Rebrand from Casera/MyCrib to honeyDue

Total rebrand across Web project:
- Package name: casera-web -> honeydue-web
- Cookie: casera-token -> honeydue-token
- Theme store: casera-theme -> honeydue-theme
- File sharing: .casera -> .honeydue, component/function renames
- casera-file-handler.tsx -> honeydue-file-handler.tsx
- All UI text, metadata, OG tags updated
- Domains: casera.treytartt.com -> honeyDue.treytartt.com
- Demo data emails updated
- All documentation updated

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/03-advanced-features.md

@@ -4,8 +4,8 @@ Build sharing, subscriptions, notifications, profile, onboarding, and summary me
 
 ## Checklist
 
-- [ ] Residence sharing: generate/display share code, join residence, manage users, .casera file export/import
-- [ ] Contractor sharing: .casera file export/import
+- [ ] Residence sharing: generate/display share code, join residence, manage users, .honeydue file export/import
+- [ ] Contractor sharing: .honeydue file export/import
 - [ ] Subscription: status display, feature comparison, upgrade prompt, usage tracking
 - [ ] Notification preferences: toggle + time picker per notification type
 - [ ] Profile: edit name/email, change password, delete account
@@ -22,7 +22,7 @@ Build sharing, subscriptions, notifications, profile, onboarding, and summary me
 | Route | Screen | Description |
 |-------|--------|-------------|
 | `/app/residences/[id]/share` | Share Residence | Generate/display share code, manage users |
-| `/app/residences/join` | Join Residence | Enter share code or import .casera file |
+| `/app/residences/join` | Join Residence | Enter share code or import .honeydue file |
 
 ### Share Code Flow
 
@@ -35,15 +35,15 @@ Owner opens Share screen
 
 Invitee opens Join screen
   → Enter share code manually, OR
-  → Upload .casera file (drag-and-drop zone)
+  → Upload .honeydue file (drag-and-drop zone)
   → POST /api/residences/join/ { code: "ABC123" }
   → On success: redirect to residence detail
 ```
 
-### .casera File Handling
+### .honeydue File Handling
 
 **Export** (owner):
-- Button on residence detail: "Export as .casera"
+- Button on residence detail: "Export as .honeydue"
 - Generates JSON file with `{ type: "residence", code: "ABC123", ... }`
 - Browser downloads the file
 
@@ -73,7 +73,7 @@ Invitee opens Join screen
 
 ## 2. Contractor Sharing
 
-### .casera File Export/Import
+### .honeydue File Export/Import
 
 **Export**:
 - Button on contractor detail: "Share Contractor"
@@ -82,7 +82,7 @@ Invitee opens Join screen
 
 **Import**:
 - Button on contractor list: "Import Contractor"
-- File picker or drag-and-drop for .casera file
+- File picker or drag-and-drop for .honeydue file
 - Read JSON, show confirmation dialog, create contractor
 - `POST /api/contractors/import/`
 
@@ -123,7 +123,7 @@ Check tier limits before allowing creation:
 ### Upgrade Path (Phase 1)
 
 Web users are directed to the mobile app for purchases:
-- "Download Casera on the App Store to upgrade"
+- "Download honeyDue on the App Store to upgrade"
 - Link to App Store listing
 
 ### Upgrade Path (Future — Phase 2)
@@ -215,7 +215,7 @@ Add Stripe Checkout for web-only subscription purchases. Requires backend work t
 
 ```
 Step 1: Welcome
-  → "Welcome to Casera! Let's set up your first property."
+  → "Welcome to honeyDue! Let's set up your first property."
 
 Step 2: Choose Path
   → "Create a new residence" OR "Join an existing residence"
@@ -300,7 +300,7 @@ Data sources:
 
 At the end of Phase 3, you should have:
 1. Residence sharing with code generation, join flow, and user management
-2. Contractor sharing via .casera files
+2. Contractor sharing via .honeydue files
 3. Subscription status with tier limits and upgrade prompts
 4. Notification preferences with toggles
 5. Profile editing (name, email, password, delete account)