Rename Forte to LunarFront, generalize for any small business

Rebrand from Forte (music-store-specific) to LunarFront (any small business):
- Package namespace @forte/* → @lunarfront/*
- Database forte/forte_test → lunarfront/lunarfront_test
- Docker containers, volumes, connection strings
- UI branding, localStorage keys, test emails
- All documentation and planning docs

Generalize music-specific terminology:
- instrumentDescription → itemDescription
- instrumentCount → itemCount
- instrumentType → itemCategory (on service templates)
- New migration 0027_generalize_terminology for column renames
- Seed data updated with generic examples
- RBAC descriptions updated

packages/admin/src/wiki/index.ts

@@ -16,17 +16,17 @@ const pages: WikiPage[] = [
     title: 'Getting Started',
     category: 'General',
     content: `
-# Getting Started with Forte
+# Getting Started with LunarFront
 
-Welcome to Forte — your music store management platform.
+Welcome to LunarFront — your small business management platform.
 
 ## Signing In
 
-1. Open Forte in your browser
+1. Open LunarFront in your browser
 2. Enter your email and password
 3. Click **Sign in**
 
-If you don't have an account, ask your store manager to create one for you.
+If you don't have an account, ask your admin to create one for you.
 
 ## Navigation
 
@@ -34,13 +34,13 @@ Use the sidebar on the left to navigate between sections:
 
 - **Accounts** — manage customer accounts and their members
 - **Members** — find and manage individual people across all accounts
-- **Repairs** — track instrument repair tickets
+- **Repairs** — track repair tickets
 - **Repair Batches** — manage bulk school repair jobs
 - **Help** — you're here!
 
 ## Need Help?
 
-If you can't find what you're looking for, contact your store manager or system administrator.
+If you can't find what you're looking for, contact your admin or system administrator.
     `.trim(),
   },
   {
@@ -89,7 +89,7 @@ Every account gets a unique 6-digit number automatically. This number appears in
     content: `
 # Members
 
-A **member** is an individual person associated with an account. This could be a parent, a child, a student, a band director — anyone who takes lessons, rents instruments, or needs to be tracked.
+A **member** is an individual person associated with an account. This could be a parent, a child, a student, a staff member — anyone who takes lessons, uses services, or needs to be tracked.
 
 ## Adding a Member
 
@@ -136,7 +136,7 @@ Payment methods are cards on file for an account. These are used for recurring b
 5. Optionally enter card brand, last four digits, and expiration
 6. Click **Add Payment Method**
 
-**Note:** Card details are stored securely with the payment processor — Forte only keeps a reference and display info (last 4 digits, brand).
+**Note:** Card details are stored securely with the payment processor — LunarFront only keeps a reference and display info (last 4 digits, brand).
 
 ## Default Payment Method
 
@@ -154,7 +154,7 @@ If a payment method was migrated from an old system, it may show a "Needs Update
     content: `
 # Tax Exemptions
 
-Schools, churches, and resellers may be exempt from sales tax. Forte tracks tax exemption certificates per account.
+Schools, churches, and resellers may be exempt from sales tax. LunarFront tracks tax exemption certificates per account.
 
 ## Adding a Tax Exemption
 
@@ -191,7 +191,7 @@ All approvals and revocations are logged with who did it and when.
     content: `
 # Identity Documents
 
-You can store identity documents (driver's license, passport, school ID) for any member. This is useful for verifying identity during instrument pickups, rentals, or trade-ins.
+You can store identity documents (driver's license, passport, school ID) for any member. This is useful for verifying identity during pickups, rentals, or trade-ins.
 
 ## Adding an ID
 
@@ -225,7 +225,7 @@ If a member has multiple IDs, mark one as **Primary** — this is the one shown
     content: `
 # Users & Roles
 
-Forte uses a permission-based access control system. **Permissions** are specific actions (like "view accounts" or "edit inventory"). **Roles** are named groups of permissions that you assign to users.
+LunarFront uses a permission-based access control system. **Permissions** are specific actions (like "view accounts" or "edit inventory"). **Roles** are named groups of permissions that you assign to users.
 
 ## Managing Users
 
@@ -306,16 +306,16 @@ Your preferences are saved in your browser and persist across sessions.
     content: `
 # Repairs
 
-The Repairs module tracks instrument repair tickets from intake through completion. It supports walk-in customers, account-linked repairs, and bulk school batch jobs.
+The Repairs module tracks repair tickets from intake through completion. It supports walk-in customers, account-linked repairs, and bulk school batch jobs.
 
 ## Creating a Repair Ticket
 
 1. Go to **Repairs** in the sidebar
 2. Click **New Repair**
 3. Search for an existing account or enter customer details manually for walk-ins
-4. Describe the instrument and the problem
+4. Describe the item and the problem
 5. Optionally add line items for the estimate (use templates for common services)
-6. Add intake photos to document the instrument's condition
+6. Add intake photos to document the item's condition
 7. Click **Create Ticket**
 
 ## Ticket Status Flow
@@ -323,16 +323,16 @@ The Repairs module tracks instrument repair tickets from intake through completi
 Each ticket moves through these stages:
 
 - **New** — ticket just created, not yet examined
-- **In Transit** — instrument being transported to the shop (for school pickups or shipped instruments)
-- **Intake** — instrument received, condition documented
-- **Diagnosing** — technician examining the instrument
+- **In Transit** — item being transported to the shop (for pickups or shipped items)
+- **Intake** — item received, condition documented
+- **Diagnosing** — technician examining the item
 - **Pending Approval** — estimate provided, waiting for customer OK
 - **Approved** — customer authorized the work
 - **In Progress** — actively being repaired
 - **Pending Parts** — waiting on parts order
 - **Ready** — repair complete, awaiting pickup
-- **Picked Up** — customer collected the instrument
-- **Delivered** — instrument returned via delivery (for school batches)
+- **Picked Up** — customer collected the item
+- **Delivered** — item returned via delivery (for school batches)
 
 Click the status buttons on the ticket detail page to advance through the workflow. You can also click steps on the progress bar.
 
@@ -340,7 +340,7 @@ Click the status buttons on the ticket detail page to advance through the workfl
 
 The ticket detail has four tabs:
 
-- **Details** — customer info, instrument, condition, costs. Click **Edit** to modify.
+- **Details** — customer info, item, condition, costs. Click **Edit** to modify.
 - **Line Items** — labor, parts, flat-rate services, and misc charges. Use the template picker for common repairs.
 - **Notes** — running journal of notes. Choose **Internal** (staff only) or **Customer Visible**. You can attach photos to notes.
 - **Photos & Docs** — photos organized by repair phase (intake, in progress, completed) plus a documents section for signed approvals, quotes, and receipts.
@@ -372,7 +372,7 @@ Templates are pre-defined common repairs (e.g. "Bow Rehair — Violin — 4/4")
 2. Click **New Template**
 3. Fill in:
    - **Name** — e.g. "Bow Rehair", "String Change", "Valve Overhaul"
-   - **Instrument Type** — e.g. "Violin", "Guitar", "Trumpet"
+   - **Item Category** — e.g. "Violin", "Guitar", "Trumpet"
    - **Size** — e.g. "4/4", "3/4", "Full"
    - **Type** — Labor, Part, Flat Rate, or Misc
    - **Default Price** — the customer-facing price
@@ -400,19 +400,19 @@ When creating a ticket or adding line items, type in the **Quick Add from Templa
     content: `
 # Repair Batches
 
-Batches group multiple repair tickets under one job — typically for schools bringing in many instruments at once.
+Batches group multiple repair tickets under one job — typically for schools bringing in many items at once.
 
 ## Creating a Batch
 
 1. Go to **Repair Batches** in the sidebar
 2. Click **New Batch**
 3. Select the school's account
-4. Enter contact info, instrument count, and any notes
+4. Enter contact info, item count, and any notes
 5. Click **Create Batch**
 
 ## Adding Tickets to a Batch
 
-When creating new repair tickets, select the batch in the form. Each instrument gets its own ticket linked to the batch.
+When creating new repair tickets, select the batch in the form. Each item gets its own ticket linked to the batch.
 
 ## Batch Approval
 
@@ -426,10 +426,10 @@ Only admins can approve or reject batches.
 
 ## Batch Status
 
-- **Intake** — receiving instruments
+- **Intake** — receiving items
 - **In Progress** — work underway
 - **Completed** — all repairs done
-- **Delivered** — instruments returned to school
+- **Delivered** — items returned to customer
 
 ## Filtering
 
@@ -468,7 +468,7 @@ Photos appear inline in the note entry. Click to view full size.
 
 The Photos & Docs tab organizes photos into categories:
 
-- **Intake Photos** — document instrument condition when received
+- **Intake Photos** — document item condition when received
 - **Work in Progress** — during the repair
 - **Completed** — final result after repair
 - **Documents** — signed approvals, quotes, receipts (accepts PDFs)