## 1. CMS and public content model

- [x] 1.1 Add the typed official WhatsApp setting with migration, model/form validation and regression coverage.
- [x] 1.2 Add the publishable, ordered WeddingPackage model, migration, factory, policy and Filament resource with failing-first coverage.
- [x] 1.3 Add official Essenza, Conduzione and Grand Jour seed content and production-safe visual fixture gating.
- [x] 1.4 Extend the public marketing query/data object to load wedding modalities and truthful acervo state.

## 2. Proposal and partner boundaries

- [x] 2.1 Move the existing event proposal request/form/mail route to `/briefing`, including prefilled modality interest.
- [x] 2.2 Add the isolated partner inquiry request, controller, rate limit, honeypot, duplicate guard and dedicated mailable.
- [x] 2.3 Cover each public form's validation, delivery, privacy copy, anti-spam path and absence of cross-flow mail/persistence.

## 3. Editorial public journey

- [x] 3.1 Recompose home chapters and stable anchors for Amare, directions, weddings, Corporate, acervo and testimonials.
- [x] 3.2 Render published wedding modalities with contextual WhatsApp/fallback CTAs and keep Corporate proof-free.
- [x] 3.3 Update navigation, footer and deep-route `/#chapter` links; preserve the services, portfolio, about and privacy deep dives.
- [x] 3.4 Update `/servicos`, `/briefing` and `/contato` with the approved factual copy and Heritage Editorial form/layout treatment.

## 4. Verification and handoff

- [x] 4.1 Run the focused feature suite and static/formatting gates; fix all scoped regressions.
- [x] 4.2 Run browser coverage at desktop and mobile, keyboard/axe and reduced-motion checks without visual snapshots.
- [x] 4.3 Validate the OpenSpec change and update every completed task only with recorded verification evidence.