Tenant Service & Form Exploration

Context

Current booking system allows tenants to manage Services, Rentals, and Add-ons.
Admin pages show a list of services, with visibility, price kind, and scheduling tied in.
Comparison with Wix highlights opportunities for polish and clarity in service listings.

Form builder: Needed so tenants can attach intake forms to bookings.
- Open question: Should forms be tenant-wide defaults, service-level, or variation-level?
- Recommendation: Hybrid inheritance — Tenant ⟶ Service ⟶ Variation.
- Ensures flexibility while keeping a consistent, auditable intake snapshot.
Services Page:
- Current: Simple table with name, base price, visibility.
- Desired: Elevated UX, placeholders for images, empty state when no services, and more contextual info (like Wix).

Tenant empowerment: Tenants can add their own forms without dev help.
Consistency: All bookings carry a snapshot of required intake data.
UI polish: Cleaner, more scannable service lists with empty/near-empty states.

Implement form builder spec (drafted as GitHub issue).
Create service page revamp issue (Wix-inspired polish).
Capture acceptance criteria for booking flow integration:
- Resolve forms per tenant/service/variation.
- Ensure snapshotting on booking confirmation.
- Validate required fields before payment.