fix: alinhar testes browser ao contrato de CTA home

feat: adota daisyUI 5 com tema amare

.github/workflows/ci.yml

@@ -205,15 +205,12 @@ jobs:
       - run: npm run build
       - run: npx playwright install chromium --with-deps
       - run: php artisan migrate --force
-      - run: php artisan db:seed --class=VisualContentSeeder --force
       - run: php artisan storage:link
 
       - name: Build application image
         run: docker build -t amare-app:ci .
 
       - name: Run browser tests against FrankenPHP container
-        env:
-          APP_FROZEN_NOW: "2026-03-15T12:00:00-03:00"
         run: |
           docker run -d --name amare-web \
             -e APP_ENV=testing \
@@ -222,7 +219,6 @@ jobs:
             -e APP_LOCALE=pt_BR \
             -e APP_FALLBACK_LOCALE=pt_BR \
             -e APP_TIMEZONE=America/Sao_Paulo \
-            -e APP_FROZEN_NOW="${APP_FROZEN_NOW}" \
             -e DB_CONNECTION=pgsql \
             -e DB_HOST=host.docker.internal \
             -e DB_PORT=5432 \
@@ -253,8 +249,6 @@ jobs:
           mkdir -p artifacts/browser
           docker logs amare-web > artifacts/browser/container.log 2>&1 || true
           cp -R storage/logs artifacts/browser/app-logs 2>/dev/null || true
-          cp -R tests/Browser/Screenshots artifacts/browser/screenshots 2>/dev/null || true
-          cp -R tests/.pest artifacts/browser/pest 2>/dev/null || true
 
       - name: Upload browser failure artifacts
         if: failure()

.gitignore

@@ -18,7 +18,6 @@
 /public/fonts-manifest.dev.json
 /public/hot
 /public/storage
-/tests/Browser/Screenshots
 /storage/*.key
 /storage/pail
 /vendor
@@ -27,3 +26,6 @@ Homestead.json
 Homestead.yaml
 Thumbs.db
 .worktrees/
+
+# Pest Browser visual diffs (local/CI artifacts)
+/tests/Browser/Screenshots/

AGENTS.md

@@ -31,9 +31,13 @@ Hooks live in `.husky/` and auto-install on any plain `npm install` via the `pre
 
 Follow PSR-4 and Laravel conventions: PascalCase classes, camelCase methods, and snake_case database columns. Use four spaces (two in YAML, except four in Compose files), LF endings, and UTF-8 as defined by `.editorconfig`. Every project-owned PHP file must place `declare(strict_types=1);` immediately after `<?php`. Keep domain code independent of Filament and Livewire. Run `composer pint` to format and `composer phpstan` before review.
 
+## Design Principles: DRY & YAGNI
+
+Write for the problem at hand, not an imagined future. **DRY**: extract and reuse a piece of logic as soon as it is genuinely duplicated in more than one place — but not before. **YAGNI**: do not add abstraction, configurability, or layers speculatively; add them only when a concrete requirement demands it. Prefer the simplest thing that solves the current requirement. Duplication that appears once is not yet a reason to abstract — wait for a second real occurrence before generalizing. This repo already encodes YAGNI in `openspec/config.yaml` (no generic repositories / `BaseService`); keep that spirit in new code. Avoid over-engineering and avoid premature extraction.
+
 ## Testing Guidelines
 
-Tests use Pest 4; browser coverage uses Pest Browser/Playwright. Name files by behavior, ending in `Test.php`, and add tests in the suite matching the changed layer. Feature tests use `RefreshDatabase`. Add architecture coverage for dependency-boundary changes. No numeric coverage threshold is enforced, but changed behavior must have regression coverage.
+Tests use Pest 4; browser coverage uses Pest Browser/Playwright. Tests are verification, not a design driver — write them to cover behavior you've already implemented, matching the layer you changed. Name files by behavior, ending in `Test.php`, and add tests in the suite matching the changed layer. Feature tests use `RefreshDatabase`. Add architecture coverage for dependency-boundary changes. No numeric coverage threshold is enforced; add regression tests where a bug was fixed or behavior is non-obvious, without making tests a front-loaded design ceremony.
 
 ## Commit & Pull Request Guidelines
 

CLAUDE.md

@@ -14,6 +14,10 @@ If the import above did not load, read `AGENTS.md` at the repo root now — it i
 - Every project-owned PHP file starts with `declare(strict_types=1);` immediately after `<?php`.
 - Browser tests are CI-only (they run against a FrankenPHP container built by `docker build`, not `artisan serve`).
 
+## Design principles: DRY & YAGNI (not TDD)
+
+Write for the problem at hand, not an imagined future. **DRY**: extract and reuse only once logic is genuinely duplicated in more than one place. **YAGNI**: no speculative abstraction, configurability, or layers — add them only when a concrete requirement demands it. Prefer the simplest thing that solves the current requirement; avoid over-engineering and premature extraction. Tests are verification, not a design driver: write them to cover behavior already implemented, not as a front-loaded TDD ceremony.
+
 ## Environment note
 
 PHP and Composer are **not on PATH** in this environment, and `vendor/` and `node_modules/` are absent. Every `composer …` / `php artisan …` command in `AGENTS.md` and `README.md` assumes a PHP 8.4+ runtime with Composer 2 installed. Verify the toolchain before promising a command ran.
@@ -53,18 +57,9 @@ Site-wide content is a singleton row reached via `SiteSetting::instance()`. Publ
 
 `App\Application` is **not** covered by that rule. `app/Domain/` currently holds a single placeholder (`DomainModule.php`); business reads live in `app/Application/Queries`. Extend the arch test when you add a boundary.
 
-## Visual regression — read before touching baselines
+## Deterministic test support
 
-- Baselines are committed `.snap` files under `tests/.pest/snapshots/Browser/VisualRegressionTest/`.
+`APP_FROZEN_NOW` configures `CarbonImmutable::setTestNow()` through `AppServiceProvider::freezeClockWhenConfigured()` outside production. `VisualContentSeeder` provides deterministic image/content fixtures for tests that explicitly need them. Neither setting is a browser-CI global default.
-- `tests/Browser/Screenshots/` is gitignored — it only holds diff output.
-- `composer visual:update` is the sanctioned command, but on macOS it writes baselines CI rejects. Use `scripts/test/visual-update-ci.sh`, which runs it inside the Linux runner built from `docker/ci-runner.Dockerfile`.
-- **Baselines are Linux-parity artifacts.** Pest Browser does not use FrankenPHP or `artisan serve` — it serves the Laravel kernel from an in-process Amp server (`vendor/pestphp/pest-plugin-browser/src/Drivers/LaravelHttpServer.php`), so the FrankenPHP container the `browser` job starts is only a health check. What makes a baseline reproducible is the machine that renders it: Ubuntu 24.04, Playwright's Chromium, and Playwright's font packages (`StableScreenshot` forces `Arial`, which fontconfig resolves to Liberation Sans on Linux). Commit `4578457` exists because macOS renders text differently.
-
-Determinism relies on three cooperating pieces:
-
-- `APP_FROZEN_NOW` → `CarbonImmutable::setTestNow()` in `AppServiceProvider::freezeClockWhenConfigured()` (no-op in production).
-- `Database\Seeders\VisualContentSeeder::FROZEN_NOW` — the value the browser tests and the CI job both pin to.
-- `Tests\Support\StableScreenshot` — forces Arial, disables transitions/animations, scrolls the page to settle lazy images, and avoids the flaky `networkidle` wait.
 
 ## Other things that bite
 

DESIGN.md

@@ -73,7 +73,7 @@ Estrutura base usa grade central de 12 colunas no desktop e 4 no mobile, com lar
 
 Composições editoriais alternam colunas assimétricas, imagens em diferentes proporções e blocos de leitura curtos. Formulários, listas e navegação mantêm alinhamento estrito. Ritmo estrutural usa múltiplos de `8px`; ajustes tipográficos usam `4px`.
 
-Desktop aceita spreads, conteúdo deslocado e relações 5/7 ou 4/5. Mobile lineariza ordem sem esconder conteúdo essencial, mantém CTA acessível e troca spreads por sequências verticais. Fotografia pode ocupar viewport amplo, desde que texto e ação permaneçam legíveis.
+Desktop aceita spreads, conteúdo deslocado e relações 5/7 ou 4/5. Nas aberturas narrativas com fotografia, o spread padrão reserva 5/12 para o texto e 7/12 para a mídia; a coluna de leitura não passa de 470px, e o título mantém quebra normal. Mobile lineariza a ordem para texto seguido da fotografia sem esconder conteúdo essencial e mantém CTA acessível. Fotografia pode ocupar viewport amplo, desde que texto e ação permaneçam legíveis.
 
 **The Editorial Rhythm Rule.** Seções alternam imagem, texto, densidade e silêncio; repetição de grades idênticas por toda página é proibida.
 

PRODUCT.md

@@ -14,36 +14,42 @@ web
 
 ## Product Purpose
 
-A Amare Assessoria usa uma única plataforma para apresentar sua marca, converter visitantes em oportunidades e conduzir a operação dos eventos. O produto deve reduzir planilhas e informações dispersas, preservar o fluxo de trabalho da equipe e deixar claro o que exige atenção.
+No recorte de lançamento, a Amare Assessoria usa o site institucional e seu CMS para apresentar a marca, publicar conteúdo e converter visitantes em pedidos de proposta por e-mail. O produto futuro continua planejado como uma única plataforma para conduzir leads e a operação dos eventos, mas essa evolução não faz parte do lançamento de 31/08/2026.
 
-Sucesso significa:
+Sucesso no lançamento significa:
 
 - visitantes qualificados concluírem o briefing;
+- a assessora atualizar os conteúdos essenciais sem depender de desenvolvimento;
+- o site equilibrar eventos sociais e corporativos com conteúdo real e autorizado;
+- acessibilidade, desempenho, jornadas críticas e deploy serem verificados antes da publicação.
+
+Nas fases futuras, sucesso também significará:
+
 - leads avançarem pelo pipeline sem depender de planilhas externas;
 - leads conquistados virarem eventos sem redigitação;
 - pendências reais do dia aparecerem com clareza;
-- tarefas, fornecedores, orçamento, pagamentos manuais e documentos permanecerem organizados por evento;
+- tarefas, fornecedores, orçamento, pagamentos manuais e documentos permanecerem organizados por evento.
-- jornadas críticas, acessibilidade e qualidade visual serem verificadas antes de cada deploy.
 
 ## Positioning
 
-Site público premium e operação interna formam um fluxo único. A mesma plataforma que transmite profissionalismo e capta a demanda transforma o lead em evento e orienta a equipe pelas pendências e exceções que precisam de ação, sem exigir troca radical de processo.
+No lançamento, o site público premium e o CMS interno formam a superfície entregue: a mesma aplicação transmite profissionalismo, capta a demanda por e-mail e permite manter o conteúdo essencial. A operação interna completa permanece como direção futura para transformar leads em eventos e orientar a equipe pelas pendências e exceções que precisam de ação, sem exigir troca radical de processo.
 
 ## Operating Context
 
 - Atuação em São Paulo, capital.
 - Serviços: casamentos, eventos corporativos e celebrações.
 - Operação realizada por assessora principal e equipe pequena.
-- Jornada prevista: descoberta no site, briefing, qualificação do lead, pipeline comercial, conversão em evento, checklist, fornecedores, orçamento, pagamentos manuais e documentos.
+- Jornada de lançamento: descoberta no site, briefing por e-mail e contato comercial fora da plataforma.
+- Jornada futura prevista: qualificação do lead, pipeline comercial, conversão em evento, checklist, fornecedores, orçamento, pagamentos manuais e documentos.
 - Interface pública em português do Brasil; dados financeiros em reais.
 - Área interna acessível por administradora e assistentes com papéis simples.
 
 ## Capabilities and Constraints
 
 - Produto single-tenant para a operação da Amare; não é SaaS para várias assessorias.
-- Duas superfícies integradas: site público responsivo com CMS e área interna operacional em Filament.
+- O lançamento inclui site público responsivo, CMS em Filament, briefing enviado por e-mail sem persistência de Lead, usuários internos simples, SEO básico, acessibilidade automatizada e deploy em contêiner.
-- MVP inclui briefing, CRM de leads, conversão em evento, tarefas, fornecedores, orçamento, pagamentos manuais, documentos, dashboard orientado a exceções, notificações, auditoria, SEO básico e deploy automatizado.
+- CRM de leads, conversão em evento, tarefas, fornecedores, orçamento, pagamentos manuais, documentos, dashboard orientado a exceções, notificações e auditoria permanecem especificados para as Fases 2 a 5, adiadas sem data pela ADR-016.
-- Implementação atual cobre fundação, site público e CMS; módulos operacionais posteriores ainda fazem parte do escopo planejado.
+- O produto futuro mantém duas superfícies integradas: site público responsivo com CMS e área interna operacional em Filament; no lançamento, a área interna cobre apenas CMS, configurações e usuários.
 - Não inclui portal ou login para cliente final, aplicativo nativo, pagamentos online, RSVP, gestão de convidados, assinatura eletrônica, integração oficial com WhatsApp, multi-tenancy ou PWA offline avançada.
 - Contas internas usam os papéis `admin` e `assistant`; permissões granulares ficam fora do MVP.
 - Fatos ainda em aberto: processo real de qualificação comercial, política de retenção LGPD para leads perdidos, canais oficiais, domínio e infraestrutura de produção.
@@ -58,7 +64,7 @@ Site público premium e operação interna formam um fluxo único. A mesma plata
 ## Evidence on Hand
 
 - `SPEC.md` define escopo, personas, jornadas, métricas, requisitos e decisões do MVP.
-- Código atual contém site público, CMS, estrutura de acessibilidade, testes visuais e conteúdo demonstrativo.
+- Código atual contém site público, CMS, estrutura de acessibilidade, testes browser e conteúdo demonstrativo.
 - Textos, fotografias, portfólio, depoimentos, contatos e perfis sociais presentes nos seeders são dados fictícios de desenvolvimento e não constituem prova comercial.
 - Ainda não há logo, fotografia proprietária, depoimentos autorizados, cases reais, imprensa, credenciais, CNPJ ou texto jurídico definitivo confirmados no repositório. Trabalho futuro não deve inventá-los.
 
@@ -68,7 +74,7 @@ Site público premium e operação interna formam um fluxo único. A mesma plata
 2. **Uma informação, um fluxo:** conduzir o dado do briefing ao evento sem redigitação ou planilhas paralelas.
 3. **Adoção sem ruptura:** organizar o trabalho existente da equipe sem impor processo desnecessariamente complexo.
 4. **Confiança sustentada por fatos:** usar somente conteúdo, resultados e provas reais e autorizados.
-5. **Qualidade verificável:** tratar acessibilidade, desempenho, testes visuais e jornadas críticas como critérios de entrega.
+5. **Qualidade verificável:** tratar acessibilidade, desempenho, motion e jornadas críticas como critérios de entrega.
 
 ## Accessibility & Inclusion
 

SPEC.md

@@ -23,7 +23,7 @@
 | Área pública | Blade + JS vanilla progressivo (Livewire é dependência do Filament, não usada no site público — ver ADR-015) |
 | Servidor de aplicação | FrankenPHP em modo regular |
 | Banco de dados | PostgreSQL |
-| Testes | Pest, Pest Browser/Playwright e testes visuais |
+| Testes | Pest e Pest Browser/Playwright |
 
 ### 0.1 Vocabulário normativo
 
@@ -80,7 +80,6 @@ O agente:
 - NÃO DEVE colocar regras financeiras diretamente em views, Resources, Models observers ou callbacks de formulário.
 - NÃO DEVE usar `float` para dinheiro.
 - NÃO DEVE persistir status derivados que possam ser calculados corretamente a partir dos dados fonte.
-- NÃO DEVE atualizar snapshots visuais apenas para fazer o CI passar sem revisar o diff.
 
 ### 1.2 Entrega incremental
 
@@ -135,7 +134,6 @@ Uma assessora adotará o sistema quando ele:
 | Operação | Tarefas vencidas sem responsável | `0` |
 | Financeiro | Itens de orçamento sem valor ou status | Menos de 5% por evento ativo |
 | Qualidade | Jornadas E2E críticas passando | 100% antes de deploy |
-| Visual | Snapshots aprovados | 100% |
 | Confiabilidade | Erros não tratados | Alerta imediato e tendência decrescente |
 
 ---
@@ -207,7 +205,7 @@ No recorte do lançamento (Fases 0–1):
 - formulário de briefing;
 - usuários internos e papéis simples;
 - SEO básico;
-- acessibilidade e testes visuais;
+- acessibilidade automatizada;
 - CI/CD e deploy em contêiner com FrankenPHP.
 
 Adiados para depois do lançamento (Fases 2–5, ver ADR-016):
@@ -1901,7 +1899,7 @@ A pirâmide deve possuir:
 1. muitos testes unitários rápidos;
 2. testes feature/integration suficientes para Laravel, PostgreSQL, Livewire e Filament;
 3. poucos testes E2E cobrindo jornadas críticas;
-4. testes visuais determinísticos nas telas mais importantes.
+4. testes E2E, de acessibilidade, motion e smoke nas jornadas públicas mais importantes.
 
 A distribuição é por intenção, não por percentual rígido.
 
@@ -1983,40 +1981,7 @@ Em falha, CI deve publicar:
 - logs do browser;
 - HTML report quando disponível.
 
-### 13.5 Regressão visual
+### 13.5 Testes de arquitetura
-
-Usar `assertScreenshotMatches()` ou API equivalente do Pest Browser.
-
-Snapshots obrigatórios:
-
-| Tela | Desktop | Mobile |
-|---|---:|---:|
-| Home | 1440×1000 | 390×844 |
-| Serviços | 1440×1000 | 390×844 |
-| Portfólio | 1440×1000 | 390×844 |
-| Detalhe do portfólio | 1440×1000 | 390×844 |
-| Briefing vazio | 1280×900 | 390×844 |
-| Briefing com erros | 1280×900 | 390×844 |
-| Briefing sucesso | 1280×900 | 390×844 |
-| Login | 1280×900 | Opcional |
-| Dashboard | 1440×1000 | Não obrigatório |
-| Detalhe do evento | 1440×1000 | Não obrigatório |
-
-Determinismo obrigatório:
-
-- Chromium e imagem Linux fixos;
-- viewport fixo;
-- timezone `America/Sao_Paulo`;
-- locale `pt-BR`;
-- fontes instaladas na imagem;
-- relógio congelado;
-- seed determinístico;
-- animações e transições desabilitadas;
-- dados dinâmicos mascarados quando necessário.
-
-Atualização de baseline deve usar comando explícito e revisão humana do diff.
-
-### 13.6 Testes de arquitetura
 
 Criar regras Pest Architecture:
 
@@ -2033,14 +1998,14 @@ arch()
 
 Adicionar regras conforme a estrutura real, sem tornar a suíte excessivamente frágil.
 
-### 13.7 Cobertura
+### 13.6 Cobertura
 
 - meta de 80% para `Domain` e `Application`;
 - não medir views, migrations, código gerado e framework;
 - cobertura não substitui critérios de aceite;
 - queda de cobertura em módulo crítico deve bloquear merge.
 
-### 13.8 Acessibilidade automatizada
+### 13.7 Acessibilidade automatizada
 
 Smoke/browser tests devem verificar:
 
@@ -2058,7 +2023,7 @@ Revisão manual mínima antes do lançamento:
 - zoom a 200%;
 - leitor de tela nos fluxos de briefing e login.
 
-### 13.9 Comandos padronizados
+### 13.8 Comandos padronizados
 
 O projeto deve expor scripts equivalentes:
 
@@ -2068,7 +2033,6 @@ composer test:feature
 composer test:browser
 composer test
 composer quality
-composer visual:update
 ```
 
 Composição esperada:
@@ -2076,7 +2040,7 @@ Composição esperada:
 ```text
 test:unit      → Unit + Architecture
 test:feature   → Feature + Livewire + Filament
-test:browser   → E2E + visual + acessibilidade + smoke
+test:browser   → E2E + acessibilidade + motion + smoke
 quality        → Pint check + PHPStan/Larastan + audits + testes
 ```
 
@@ -2091,7 +2055,7 @@ quality        → Pint check + PHPStan/Larastan + audits + testes
 | `static` | Pint, PHPStan/Larastan, Composer validate, Composer e npm audit | Sim |
 | `unit` | Unitários, arquitetura e cobertura | Sim |
 | `feature` | PostgreSQL, migrations, Livewire, Filament e integração | Sim |
-| `browser` | Vite, FrankenPHP, E2E, smoke, acessibilidade e visual | Sim |
+| `browser` | Vite, FrankenPHP, E2E, smoke, acessibilidade e motion | Sim |
 | `container` | Build da imagem final e healthcheck | Sim |
 
 ### 14.2 Regras do pipeline
@@ -2125,7 +2089,6 @@ Uma história só está concluída quando:
 - PHPStan/Larastan está verde;
 - unit e feature tests cobrem regras relevantes;
 - E2E foi criado ou atualizado para fluxo crítico;
-- snapshot foi criado ou revisado para UI coberta;
 - acessibilidade automatizada não possui issues críticas/sérias;
 - migration foi testada;
 - autorização foi verificada;
@@ -2383,10 +2346,9 @@ O agente deve implementar na sequência, salvo instrução explícita.
 - [x] privacidade;
 - [x] SEO;
 - [x] mídia otimizada;
-- [x] snapshots desktop/mobile;
 - [x] testes de acessibilidade.
 
-**Critério de saída:** conteúdo gerenciável no Filament e site público aprovado visualmente (baselines em `tests/.pest/snapshots/`; aprovação humana do diff visual no PR).
+**Critério de saída:** conteúdo gerenciável no Filament, testes browser funcionais, de acessibilidade e motion aprovados, e revisão humana do site público no PR.
 
 ### Fase 2 — Leads — ADIADA (ADR-016)
 
@@ -2497,8 +2459,7 @@ Toda operação financeira deve:
 | Risco | Mitigação obrigatória |
 |---|---|
 | Filament concentrar domínio | Resources finos, Actions e Queries testáveis |
-| Site parecer genérico | design tokens, conteúdo real, fotografia e visual tests |
+| Site parecer genérico | design tokens, conteúdo real, fotografia e revisão humana |
-| Snapshots instáveis | contêiner fixo, relógio/dados/fontes determinísticos |
 | Escopo crescer | lista de não objetivos e mudança somente com hipótese real |
 | Financeiro virar contabilidade | limitar a orçamento e pagamentos manuais |
 | Worker mode vazar estado | manter modo regular até benchmark e ADR |
@@ -2517,7 +2478,7 @@ Toda operação financeira deve:
 | ADR-002 | Filament para área interna (Livewire é dependência interna do Filament); site público em Blade — ver ADR-015 | Aceita |
 | ADR-003 | PostgreSQL como único banco transacional | Aceita |
 | ADR-004 | Pagamentos somente manuais | Aceita |
-| ADR-005 | Pest unifica unit, feature, browser e visual | Aceita |
+| ADR-005 | Pest unifica unit, feature e browser | Aceita |
 | ADR-006 | FrankenPHP regular mode; worker mode adiado | Aceita |
 | ADR-007 | Single-tenant; SaaS e portal do cliente adiados | Aceita |
 | ADR-008 | Database queue; Redis adiado | Aceita |
@@ -2563,7 +2524,7 @@ O lançamento está concluído somente quando:
 - assessora edita os conteúdos essenciais sem desenvolvedor;
 - briefing envia o pedido de proposta de forma segura, com proteção contra abuso e aceite de privacidade registrado;
 - usuários e Policies estão corretos;
-- testes unit, feature, visuais e arquitetura estão verdes;
+- testes unit, feature, browser funcionais e arquitetura estão verdes;
 - CI bloqueia regressões;
 - imagem FrankenPHP é reproduzível;
 - staging e produção usam a mesma imagem promovida;

app/Application/Data/HomeContent.php

@@ -8,6 +8,7 @@ use App\Models\PortfolioCase;
 use App\Models\Service;
 use App\Models\SiteSetting;
 use App\Models\Testimonial;
+use App\Models\WeddingPackage;
 use Illuminate\Database\Eloquent\Collection;
 
 final readonly class HomeContent
@@ -16,11 +17,13 @@ final readonly class HomeContent
      * @param  Collection<int, Service>  $featuredServices
      * @param  Collection<int, PortfolioCase>  $featuredCases
      * @param  Collection<int, Testimonial>  $testimonials
+     * @param  Collection<int, WeddingPackage>  $packages
      */
     public function __construct(
         public SiteSetting $settings,
         public Collection $featuredServices,
         public Collection $featuredCases,
         public Collection $testimonials,
+        public Collection $packages,
     ) {}
 }

app/Application/Queries/Marketing/GetHomeContent.php

@@ -9,6 +9,7 @@ use App\Models\PortfolioCase;
 use App\Models\Service;
 use App\Models\SiteSetting;
 use App\Models\Testimonial;
+use App\Models\WeddingPackage;
 
 final class GetHomeContent
 {
@@ -31,6 +32,10 @@ final class GetHomeContent
                 ->published()
                 ->orderBy('sort_order')
                 ->get(),
+            packages: WeddingPackage::query()
+                ->published()
+                ->orderBy('sort_order')
+                ->get(),
         );
     }
 }

app/Console/Commands/MediaGenerateVariantsCommand.php

@@ -29,6 +29,7 @@ final class MediaGenerateVariantsCommand extends Command
 
         foreach ($paths as $path) {
             if (! Storage::disk($disk)->exists($path)) {
+                ResponsiveImage::forgetMetadata($path, $disk);
                 $this->warn("Missing file: {$path}");
                 $skipped++;
 
@@ -56,9 +57,21 @@ final class MediaGenerateVariantsCommand extends Command
         if ($settings && filled($settings->default_og_image_path)) {
             $paths[] = (string) $settings->default_og_image_path;
         }
+        if ($settings && filled($settings->hero_image_path)) {
+            $paths[] = (string) $settings->hero_image_path;
+        }
         if ($settings && filled($settings->about_image_path)) {
             $paths[] = (string) $settings->about_image_path;
         }
+        if ($settings && filled($settings->hero_image_path)) {
+            $paths[] = (string) $settings->hero_image_path;
+        }
+        if ($settings && filled($settings->services_hero_image_path)) {
+            $paths[] = (string) $settings->services_hero_image_path;
+        }
+        if ($settings && filled($settings->portfolio_hero_image_path)) {
+            $paths[] = (string) $settings->portfolio_hero_image_path;
+        }
 
         foreach (Service::query()->whereNotNull('cover_image_path')->pluck('cover_image_path') as $path) {
             $paths[] = (string) $path;

app/Filament/Pages/ManageSiteSettings.php

@@ -160,11 +160,24 @@ class ManageSiteSettings extends Page
                         Textarea::make('hero_note')
                             ->label('Nota do hero')
                             ->rows(2),
+                        PublicImageUploadRules::fileUpload('hero_image_path', 'Imagem do hero', 'content/home'),
+                        PublicImageUploadRules::altTextField('hero_image_alt', 'hero_image_path'),
                         Textarea::make('about_summary')
                             ->label('Resumo institucional')
                             ->rows(3),
                     ])
                     ->columns(2),
+                Section::make('Imagens das aberturas')
+                    ->description('Fotos reais e autorizadas para as primeiras dobras. Sem imagem, cada rota mantém a abertura tonal.')
+                    ->schema([
+                        PublicImageUploadRules::fileUpload('hero_image_path', 'Imagem da home', 'content/heroes'),
+                        PublicImageUploadRules::altTextField('hero_image_alt', 'hero_image_path'),
+                        PublicImageUploadRules::fileUpload('services_hero_image_path', 'Imagem de Serviços', 'content/heroes'),
+                        PublicImageUploadRules::altTextField('services_hero_image_alt', 'services_hero_image_path'),
+                        PublicImageUploadRules::fileUpload('portfolio_hero_image_path', 'Imagem de Portfólio', 'content/heroes'),
+                        PublicImageUploadRules::altTextField('portfolio_hero_image_alt', 'portfolio_hero_image_path'),
+                    ])
+                    ->columns(2),
                 Section::make('Manifesto editorial')
                     ->schema([
                         TextInput::make('manifesto_title')
@@ -199,6 +212,26 @@ class ManageSiteSettings extends Page
                             ->reorderable()
                             ->columnSpanFull(),
                     ]),
+                Section::make('Corporate')
+                    ->description('Etapas apresentadas na frente Amare Corporate da home.')
+                    ->schema([
+                        Repeater::make('corporate_steps')
+                            ->label('Etapas do serviço corporativo')
+                            ->schema([
+                                TextInput::make('title')
+                                    ->label('Título')
+                                    ->required()
+                                    ->maxLength(255),
+                                Textarea::make('body')
+                                    ->label('Descrição')
+                                    ->required()
+                                    ->rows(2),
+                            ])
+                            ->defaultItems(3)
+                            ->maxItems(6)
+                            ->reorderable()
+                            ->columnSpanFull(),
+                    ]),
                 Section::make('Princípios')
                     ->schema([
                         TagsInput::make('principles')
@@ -218,6 +251,11 @@ class ManageSiteSettings extends Page
                             ->label('Telefone')
                             ->required()
                             ->maxLength(255),
+                        TextInput::make('whatsapp_number')
+                            ->label('WhatsApp oficial para as modalidades')
+                            ->tel()
+                            ->maxLength(40)
+                            ->helperText('Use o número com DDD. Sem um número válido, as CTAs levam ao briefing.'),
                         TextInput::make('city')
                             ->label('Cidade')
                             ->maxLength(255),

app/Filament/Resources/WeddingPackages/Pages/CreateWeddingPackage.php

@@ -0,0 +1,13 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Filament\Resources\WeddingPackages\Pages;
+
+use App\Filament\Resources\WeddingPackages\WeddingPackageResource;
+use Filament\Resources\Pages\CreateRecord;
+
+class CreateWeddingPackage extends CreateRecord
+{
+    protected static string $resource = WeddingPackageResource::class;
+}

app/Filament/Resources/WeddingPackages/Pages/EditWeddingPackage.php

@@ -0,0 +1,13 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Filament\Resources\WeddingPackages\Pages;
+
+use App\Filament\Resources\WeddingPackages\WeddingPackageResource;
+use Filament\Resources\Pages\EditRecord;
+
+class EditWeddingPackage extends EditRecord
+{
+    protected static string $resource = WeddingPackageResource::class;
+}

app/Filament/Resources/WeddingPackages/Pages/ListWeddingPackages.php

@@ -0,0 +1,21 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Filament\Resources\WeddingPackages\Pages;
+
+use App\Filament\Resources\WeddingPackages\WeddingPackageResource;
+use Filament\Actions\CreateAction;
+use Filament\Resources\Pages\ListRecords;
+
+class ListWeddingPackages extends ListRecords
+{
+    protected static string $resource = WeddingPackageResource::class;
+
+    protected function getHeaderActions(): array
+    {
+        return [
+            CreateAction::make(),
+        ];
+    }
+}

app/Filament/Resources/WeddingPackages/Schemas/WeddingPackageForm.php

@@ -0,0 +1,57 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Filament\Resources\WeddingPackages\Schemas;
+
+use Filament\Forms\Components\DateTimePicker;
+use Filament\Forms\Components\Repeater;
+use Filament\Forms\Components\Textarea;
+use Filament\Forms\Components\TextInput;
+use Filament\Schemas\Schema;
+
+class WeddingPackageForm
+{
+    public static function configure(Schema $schema): Schema
+    {
+        return $schema
+            ->components([
+                TextInput::make('name')
+                    ->label('Nome da modalidade')
+                    ->required()
+                    ->maxLength(255),
+                TextInput::make('level')
+                    ->label('Número / tipo (ex.: 01 / COMPLETA)')
+                    ->required()
+                    ->maxLength(255),
+                Textarea::make('summary')
+                    ->label('Resumo')
+                    ->required()
+                    ->rows(4),
+                Repeater::make('scope_items')
+                    ->label('O que está incluído')
+                    ->schema([
+                        TextInput::make('item')
+                            ->label('Item')
+                            ->required()
+                            ->maxLength(255),
+                    ])
+                    ->defaultItems(4)
+                    ->minItems(1)
+                    ->addActionLabel('Adicionar item')
+                    ->required(),
+                TextInput::make('cta_label')
+                    ->label('Texto do botão')
+                    ->required()
+                    ->maxLength(255),
+                TextInput::make('sort_order')
+                    ->label('Ordem')
+                    ->numeric()
+                    ->default(0)
+                    ->required(),
+                DateTimePicker::make('published_at')
+                    ->label('Publicado em')
+                    ->seconds(false),
+            ]);
+    }
+}

app/Filament/Resources/WeddingPackages/Tables/WeddingPackagesTable.php

@@ -0,0 +1,50 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Filament\Resources\WeddingPackages\Tables;
+
+use Filament\Actions\BulkActionGroup;
+use Filament\Actions\DeleteAction;
+use Filament\Actions\DeleteBulkAction;
+use Filament\Actions\EditAction;
+use Filament\Tables\Columns\TextColumn;
+use Filament\Tables\Table;
+
+class WeddingPackagesTable
+{
+    public static function configure(Table $table): Table
+    {
+        return $table
+            ->columns([
+                TextColumn::make('name')
+                    ->label('Nome')
+                    ->searchable()
+                    ->sortable(),
+                TextColumn::make('level')
+                    ->label('Número / tipo')
+                    ->searchable(),
+                TextColumn::make('published_at')
+                    ->label('Publicado em')
+                    ->dateTime()
+                    ->sortable(),
+                TextColumn::make('sort_order')
+                    ->label('Ordem')
+                    ->sortable(),
+            ])
+            ->defaultSort('sort_order')
+            ->filters([
+                //
+            ])
+            ->recordActions([
+                EditAction::make(),
+                DeleteAction::make()
+                    ->requiresConfirmation(),
+            ])
+            ->toolbarActions([
+                BulkActionGroup::make([
+                    DeleteBulkAction::make(),
+                ]),
+            ]);
+    }
+}

app/Filament/Resources/WeddingPackages/WeddingPackageResource.php

@@ -0,0 +1,62 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Filament\Resources\WeddingPackages;
+
+use App\Filament\Resources\WeddingPackages\Pages\CreateWeddingPackage;
+use App\Filament\Resources\WeddingPackages\Pages\EditWeddingPackage;
+use App\Filament\Resources\WeddingPackages\Pages\ListWeddingPackages;
+use App\Filament\Resources\WeddingPackages\Schemas\WeddingPackageForm;
+use App\Filament\Resources\WeddingPackages\Tables\WeddingPackagesTable;
+use App\Models\WeddingPackage;
+use App\Policies\WeddingPackagePolicy;
+use BackedEnum;
+use Filament\Resources\Resource;
+use Filament\Schemas\Schema;
+use Filament\Support\Icons\Heroicon;
+use Filament\Tables\Table;
+use UnitEnum;
+
+class WeddingPackageResource extends Resource
+{
+    protected static ?string $model = WeddingPackage::class;
+
+    protected static ?string $policy = WeddingPackagePolicy::class;
+
+    protected static string|BackedEnum|null $navigationIcon = Heroicon::OutlinedRectangleStack;
+
+    protected static ?string $navigationLabel = 'Modalidades';
+
+    protected static ?string $modelLabel = 'modalidade';
+
+    protected static ?string $pluralModelLabel = 'modalidades';
+
+    protected static string|UnitEnum|null $navigationGroup = 'Conteúdo do site';
+
+    protected static ?int $navigationSort = 3;
+
+    public static function form(Schema $schema): Schema
+    {
+        return WeddingPackageForm::configure($schema);
+    }
+
+    public static function table(Table $table): Table
+    {
+        return WeddingPackagesTable::configure($table);
+    }
+
+    public static function getRelations(): array
+    {
+        return [];
+    }
+
+    public static function getPages(): array
+    {
+        return [
+            'index' => ListWeddingPackages::route('/'),
+            'create' => CreateWeddingPackage::route('/create'),
+            'edit' => EditWeddingPackage::route('/{record}/edit'),
+        ];
+    }
+}

app/Http/Controllers/PublicSite/ContactController.php

@@ -135,6 +135,6 @@ final class ContactController extends Controller
 
     private function success(): RedirectResponse
     {
-        return redirect()->route('contact')->with('status', 'briefing-sent');
+        return redirect()->route('briefing')->with('status', 'briefing-sent');
     }
 }

app/Http/Controllers/PublicSite/PageController.php

@@ -45,7 +45,7 @@ final class PageController extends Controller
     {
         $settings = SiteSetting::instance();
 
-        return view('pages.contact', [
+        return view('pages.partners', [
             'siteSettings' => $settings,
             'pageMeta' => PageMeta::forPage(
                 canonical: route('contact'),
@@ -55,4 +55,14 @@ final class PageController extends Controller
             ),
         ]);
     }
+
+    public function briefing(): View
+    {
+        $settings = SiteSetting::instance();
+
+        return view('pages.contact', [
+            'siteSettings' => $settings,
+            'pageMeta' => PageMeta::forPage(canonical: route('briefing'), settings: $settings, title: PageMeta::withBrandSuffix('Briefing', $settings), description: 'Solicite uma proposta à '.$settings->brand_name.'.'),
+        ]);
+    }
 }

app/Http/Controllers/PublicSite/PartnerInquiryController.php

@@ -0,0 +1,66 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Http\Controllers\PublicSite;
+
+use App\Http\Controllers\Controller;
+use App\Http\Requests\PublicSite\PartnerInquiryRequest;
+use App\Mail\PartnerInquiry;
+use App\Models\SiteSetting;
+use Illuminate\Http\RedirectResponse;
+use Illuminate\Support\Facades\Log;
+use Illuminate\Support\Facades\Mail;
+use Throwable;
+
+final class PartnerInquiryController extends Controller
+{
+    private const string DUPLICATE_SESSION_KEY = 'partner_inquiry_hash';
+
+    public function store(PartnerInquiryRequest $request): RedirectResponse
+    {
+        if (filled($request->input('website'))) {
+            return $this->success();
+        }
+
+        $validated = $request->validated();
+
+        if (session()->get(self::DUPLICATE_SESSION_KEY) === $this->hash($validated)) {
+            return $this->success();
+        }
+
+        session()->put(self::DUPLICATE_SESSION_KEY, $this->hash($validated));
+
+        try {
+            $settings = SiteSetting::instance();
+
+            if (filled($settings->email)) {
+                Mail::to($settings->email)->send(new PartnerInquiry([
+                    'Nome' => $validated['nome'],
+                    'Nome profissional ou empresa' => $validated['empresa'] ?? null,
+                    'E-mail' => $validated['email'],
+                    'Atuação ou serviço' => $validated['atuacao'],
+                    'Área de atendimento' => $validated['area_atendimento'],
+                    'Mensagem' => $validated['mensagem'],
+                    'Portfólio ou redes' => $validated['portfolio_redes'] ?? null,
+                    'Telefone' => $validated['telefone'] ?? null,
+                ]));
+            }
+        } catch (Throwable $exception) {
+            Log::error('Falha ao enviar consulta de parceiro', ['exception' => $exception::class]);
+        }
+
+        return $this->success();
+    }
+
+    /** @param array<string, mixed> $validated */
+    private function hash(array $validated): string
+    {
+        return hash('sha256', serialize($validated));
+    }
+
+    private function success(): RedirectResponse
+    {
+        return redirect()->route('contact')->with('status', 'partner-inquiry-sent');
+    }
+}

app/Http/Controllers/PublicSite/ServiceController.php

@@ -8,6 +8,7 @@ use App\Application\Data\PageMeta;
 use App\Application\Queries\Marketing\GetPublishedServices;
 use App\Http\Controllers\Controller;
 use App\Models\SiteSetting;
+use App\Models\WeddingPackage;
 use Illuminate\Contracts\View\View;
 
 final class ServiceController extends Controller
@@ -19,6 +20,7 @@ final class ServiceController extends Controller
 
         return view('pages.services.index', [
             'services' => $services,
+            'weddingPackages' => WeddingPackage::query()->published()->orderBy('sort_order')->get(),
             'siteSettings' => $settings,
             'pageMeta' => PageMeta::forPage(
                 canonical: route('services.index'),

app/Http/Requests/PublicSite/PartnerInquiryRequest.php

@@ -0,0 +1,32 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Http\Requests\PublicSite;
+
+use Illuminate\Foundation\Http\FormRequest;
+
+final class PartnerInquiryRequest extends FormRequest
+{
+    protected function prepareForValidation(): void
+    {
+        $email = $this->input('email');
+
+        $this->merge(['email' => is_string($email) ? mb_strtolower(trim($email)) : $email]);
+    }
+
+    /** @return array<string, array<int, string>> */
+    public function rules(): array
+    {
+        return [
+            'nome' => ['required', 'string', 'max:120'],
+            'empresa' => ['nullable', 'string', 'max:160'],
+            'email' => ['required', 'email', 'max:254'],
+            'atuacao' => ['required', 'string', 'max:120'],
+            'area_atendimento' => ['required', 'string', 'max:160'],
+            'mensagem' => ['required', 'string', 'max:3000'],
+            'portfolio_redes' => ['nullable', 'string', 'max:500'],
+            'telefone' => ['nullable', 'string', 'max:40'],
+        ];
+    }
+}

app/Mail/PartnerInquiry.php

@@ -0,0 +1,31 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Mail;
+
+use Illuminate\Bus\Queueable;
+use Illuminate\Contracts\Queue\ShouldQueue;
+use Illuminate\Mail\Mailable;
+use Illuminate\Mail\Mailables\Content;
+use Illuminate\Mail\Mailables\Envelope;
+use Illuminate\Queue\SerializesModels;
+
+final class PartnerInquiry extends Mailable implements ShouldQueue
+{
+    use Queueable;
+    use SerializesModels;
+
+    /** @param array<string, mixed> $fields */
+    public function __construct(public readonly array $fields) {}
+
+    public function envelope(): Envelope
+    {
+        return new Envelope(subject: 'Nova consulta de fornecedor ou parceria — Amare Assessoria');
+    }
+
+    public function content(): Content
+    {
+        return new Content(html: 'emails.partner-inquiry', text: 'emails.partner-inquiry-text');
+    }
+}

app/Models/SiteSetting.php

@@ -12,12 +12,19 @@ use Illuminate\Database\Eloquent\Model;
 /**
  * @property array<string, string|null> $social_links
  * @property list<array{title?: string, body?: string}>|null $method_steps
+ * @property list<array{title?: string, body?: string}>|null $corporate_steps
  * @property list<string>|null $principles
  * @property bool $analytics_enabled
  * @property string|null $default_og_image_path
  * @property string|null $default_og_image_alt
  * @property string|null $about_image_path
  * @property string|null $about_image_alt
+ * @property string|null $hero_image_path
+ * @property string|null $hero_image_alt
+ * @property string|null $services_hero_image_path
+ * @property string|null $services_hero_image_alt
+ * @property string|null $portfolio_hero_image_path
+ * @property string|null $portfolio_hero_image_alt
  * @property string|null $logo_path
  * @property string|null $logo_alt
  */
@@ -31,6 +38,12 @@ use Illuminate\Database\Eloquent\Model;
     'hero_cta_label',
     'hero_secondary_cta_label',
     'hero_note',
+    'hero_image_path',
+    'hero_image_alt',
+    'services_hero_image_path',
+    'services_hero_image_alt',
+    'portfolio_hero_image_path',
+    'portfolio_hero_image_alt',
     'about_summary',
     'about_image_path',
     'about_image_alt',
@@ -39,9 +52,11 @@ use Illuminate\Database\Eloquent\Model;
     'manifesto_body',
     'method_intro',
     'method_steps',
+    'corporate_steps',
     'principles',
     'email',
     'phone',
+    'whatsapp_number',
     'city',
     'social_links',
     'default_meta_title',
@@ -70,9 +85,11 @@ class SiteSetting extends Model
             'manifesto_body' => 'A Amare combina sensibilidade e precisão para criar encontros coerentes com cada cliente, marca e ocasião — sem fórmulas prontas, excessos ou ruído.',
             'method_intro' => 'Clareza em cada etapa. Tranquilidade durante todo o processo.',
             'method_steps' => self::defaultMethodSteps(),
+            'corporate_steps' => self::defaultCorporateSteps(),
             'principles' => self::defaultPrinciples(),
             'email' => 'amareassessoriaeventos@gmail.com',
             'phone' => '(11) 99999-9999',
+            'whatsapp_number' => null,
             'city' => 'São Paulo - SP',
             'social_links' => [],
             'default_meta_title' => 'Amare Assessoria de Eventos',
@@ -106,6 +123,27 @@ class SiteSetting extends Model
         ];
     }
 
+    /**
+     * @return list<array{title: string, body: string}>
+     */
+    public static function defaultCorporateSteps(): array
+    {
+        return [
+            [
+                'title' => 'Planejamento',
+                'body' => 'Estruturação de escopo, cronograma e prioridades.',
+            ],
+            [
+                'title' => 'Produção',
+                'body' => 'Coordenação dos elementos necessários para colocar o evento de pé.',
+            ],
+            [
+                'title' => 'Execução',
+                'body' => 'Condução e acompanhamento do evento conforme o projeto aprovado.',
+            ],
+        ];
+    }
+
     /**
      * @return list<string>
      */
@@ -127,6 +165,7 @@ class SiteSetting extends Model
         return [
             'social_links' => 'array',
             'method_steps' => 'array',
+            'corporate_steps' => 'array',
             'principles' => 'array',
             'analytics_enabled' => 'boolean',
         ];

app/Models/WeddingPackage.php

@@ -0,0 +1,39 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Models;
+
+use App\Models\Concerns\HasPublication;
+use App\Policies\WeddingPackagePolicy;
+use Database\Factories\WeddingPackageFactory;
+use Illuminate\Database\Eloquent\Attributes\Fillable;
+use Illuminate\Database\Eloquent\Attributes\UsePolicy;
+use Illuminate\Database\Eloquent\Factories\HasFactory;
+use Illuminate\Database\Eloquent\Model;
+use Illuminate\Support\Carbon;
+
+/**
+ * @property string $name
+ * @property string $level
+ * @property string $summary
+ * @property list<string> $scope_items
+ * @property string $cta_label
+ * @property int $sort_order
+ * @property Carbon|null $published_at
+ */
+#[Fillable(['name', 'level', 'summary', 'scope_items', 'cta_label', 'sort_order', 'published_at'])]
+#[UsePolicy(WeddingPackagePolicy::class)]
+class WeddingPackage extends Model
+{
+    /** @use HasFactory<WeddingPackageFactory> */
+    use HasFactory;
+
+    use HasPublication;
+
+    /** @return array<string, string|class-string> */
+    protected function casts(): array
+    {
+        return ['scope_items' => 'array', 'sort_order' => 'integer', 'published_at' => 'datetime'];
+    }
+}

app/Policies/WeddingPackagePolicy.php

@@ -0,0 +1,36 @@
+<?php
+
+declare(strict_types=1);
+
+namespace App\Policies;
+
+use App\Models\User;
+use App\Models\WeddingPackage;
+
+class WeddingPackagePolicy
+{
+    public function viewAny(User $user): bool
+    {
+        return $user->isAdmin();
+    }
+
+    public function view(User $user, WeddingPackage $package): bool
+    {
+        return $user->isAdmin();
+    }
+
+    public function create(User $user): bool
+    {
+        return $user->isAdmin();
+    }
+
+    public function update(User $user, WeddingPackage $package): bool
+    {
+        return $user->isAdmin();
+    }
+
+    public function delete(User $user, WeddingPackage $package): bool
+    {
+        return $user->isAdmin();
+    }
+}

app/Providers/AppServiceProvider.php

@@ -72,6 +72,10 @@ class AppServiceProvider extends ServiceProvider
         RateLimiter::for('contact-briefing', function (Request $request): Limit {
             return Limit::perMinute(5)->by($request->ip().'|contact-briefing');
         });
+
+        RateLimiter::for('partner-inquiry', function (Request $request): Limit {
+            return Limit::perMinute(5)->by($request->ip().'|partner-inquiry');
+        });
     }
 
     private function freezeClockWhenConfigured(): void

app/Support/ResponsiveImage.php

@@ -5,6 +5,7 @@ declare(strict_types=1);
 namespace App\Support;
 
 use Illuminate\Contracts\Filesystem\Filesystem;
+use Illuminate\Support\Facades\Cache;
 use Illuminate\Support\Facades\Storage;
 use Intervention\Image\Drivers\Gd\Driver;
 use Intervention\Image\ImageManager;
@@ -25,90 +26,117 @@ final class ResponsiveImage
 
     public static function generate(string $path, ?string $disk = null): void
     {
+        self::forgetMetadata($path, $disk);
         $filesystem = self::filesystem($disk);
 
-        if (! $filesystem->exists($path)) {
+        try {
-            return;
+            if (! $filesystem->exists($path)) {
-        }
+                return;
-
-        $manager = new ImageManager(new Driver);
-        $contents = $filesystem->get($path);
-
-        if ($contents === null) {
-            return;
-        }
-
-        $extension = strtolower(pathinfo($path, PATHINFO_EXTENSION));
-
-        foreach (self::WIDTHS as $width) {
-            $variantPath = self::variantPath($path, $width);
-            $variant = $manager->read($contents);
-
-            if ($variant->width() > $width) {
-                $variant->scale(width: $width);
             }
 
-            $encoded = match ($extension) {
+            $manager = new ImageManager(new Driver);
-                'png' => $variant->toPng(),
+            $contents = $filesystem->get($path);
-                'webp' => $variant->toWebp(quality: 82),
-                default => $variant->toJpeg(quality: 82),
-            };
 
-            $filesystem->put($variantPath, (string) $encoded);
+            if ($contents === null) {
-
+                return;
-            // A webp sibling for every variant. The MAN-109 audit measured the
-            // hero as the LCP element on every mobile page, at 143 KiB for a
-            // 960 px jpeg — webp carries the same picture for roughly a third of
-            // that. `x-media.image` offers these through a <source> so a browser
-            // that cannot decode webp still gets the original format.
-            if ($extension === 'webp') {
-                continue;
             }
 
-            $webp = $manager->read($contents);
+            $extension = strtolower(pathinfo($path, PATHINFO_EXTENSION));
 
-            if ($webp->width() > $width) {
+            foreach (self::WIDTHS as $width) {
-                $webp->scale(width: $width);
+                $variantPath = self::variantPath($path, $width);
+                $variant = $manager->read($contents);
+
+                if ($variant->width() > $width) {
+                    $variant->scale(width: $width);
+                }
+
+                $encoded = match ($extension) {
+                    'png' => $variant->toPng(),
+                    'webp' => $variant->toWebp(quality: 82),
+                    default => $variant->toJpeg(quality: 82),
+                };
+
+                $filesystem->put($variantPath, (string) $encoded);
+
+                // A webp sibling for every variant. The MAN-109 audit measured the
+                // hero as the LCP element on every mobile page, at 143 KiB for a
+                // 960 px jpeg — webp carries the same picture for roughly a third of
+                // that. `x-media.image` offers these through a <source> so a browser
+                // that cannot decode webp still gets the original format.
+                if ($extension === 'webp') {
+                    continue;
+                }
+
+                $webp = $manager->read($contents);
+
+                if ($webp->width() > $width) {
+                    $webp->scale(width: $width);
+                }
+
+                $filesystem->put(
+                    self::webpVariantPath($path, $width),
+                    (string) $webp->toWebp(quality: 80)
+                );
             }
-
+        } finally {
-            $filesystem->put(
+            self::forgetMetadata($path, $disk);
-                self::webpVariantPath($path, $width),
-                (string) $webp->toWebp(quality: 80)
-            );
         }
+
+        self::metadata($path, $disk);
     }
 
     public static function deleteVariants(string $path, ?string $disk = null): void
     {
+        self::forgetMetadata($path, $disk);
         $filesystem = self::filesystem($disk);
 
-        foreach (self::WIDTHS as $width) {
+        try {
-            foreach ([self::variantPath($path, $width), self::webpVariantPath($path, $width)] as $variantPath) {
+            foreach (self::WIDTHS as $width) {
-                if ($filesystem->exists($variantPath)) {
+                foreach ([self::variantPath($path, $width), self::webpVariantPath($path, $width)] as $variantPath) {
-                    $filesystem->delete($variantPath);
+                    if ($filesystem->exists($variantPath)) {
+                        $filesystem->delete($variantPath);
+                    }
                 }
             }
+        } finally {
+            self::forgetMetadata($path, $disk);
         }
     }
 
     public static function delete(string $path, ?string $disk = null): void
     {
+        self::forgetMetadata($path, $disk);
         $filesystem = self::filesystem($disk);
 
-        self::deleteVariants($path, $disk);
+        try {
+            self::deleteVariants($path, $disk);
 
-        if ($filesystem->exists($path)) {
+            if ($filesystem->exists($path)) {
-            $filesystem->delete($path);
+                $filesystem->delete($path);
+            }
+        } finally {
+            self::forgetMetadata($path, $disk);
         }
     }
 
     public static function replace(string $previousPath, string $newPath, ?string $disk = null): void
     {
-        if ($previousPath !== '' && $previousPath !== $newPath) {
+        self::forgetMetadata($previousPath, $disk);
-            self::delete($previousPath, $disk);
+        self::forgetMetadata($newPath, $disk);
+
+        try {
+            if ($previousPath !== '' && $previousPath !== $newPath) {
+                self::delete($previousPath, $disk);
+            }
+
+            self::generate($newPath, $disk);
+        } finally {
+            self::forgetMetadata($previousPath, $disk);
+            self::forgetMetadata($newPath, $disk);
         }
 
-        self::generate($newPath, $disk);
+        self::metadata($newPath, $disk);
     }
 
     public static function variantPath(string $path, int $width): string
@@ -137,21 +165,7 @@ final class ResponsiveImage
      */
     public static function availableVariants(string $path, ?string $disk = null): array
     {
-        $filesystem = self::filesystem($disk);
+        return self::metadata($path, $disk)['variants'] ?? [];
-        $variants = [];
-
-        foreach (self::WIDTHS as $width) {
-            $variantPath = self::variantPath($path, $width);
-
-            if ($filesystem->exists($variantPath)) {
-                $variants[] = [
-                    'path' => $variantPath,
-                    'width' => $width,
-                ];
-            }
-        }
-
-        return $variants;
     }
 
     /**
@@ -163,21 +177,7 @@ final class ResponsiveImage
      */
     public static function availableWebpVariants(string $path, ?string $disk = null): array
     {
-        $filesystem = self::filesystem($disk);
+        return self::metadata($path, $disk)['webp_variants'] ?? [];
-        $variants = [];
-
-        foreach (self::WIDTHS as $width) {
-            $variantPath = self::webpVariantPath($path, $width);
-
-            if ($filesystem->exists($variantPath)) {
-                $variants[] = [
-                    'path' => $variantPath,
-                    'width' => $width,
-                ];
-            }
-        }
-
-        return $variants;
     }
 
     /**
@@ -185,13 +185,38 @@ final class ResponsiveImage
      */
     public static function dimensions(string $path, ?string $disk = null): ?array
     {
-        $filesystem = self::filesystem($disk);
+        $metadata = self::metadata($path, $disk);
 
-        if (! $filesystem->exists($path)) {
+        return $metadata === null ? null : [
-            return null;
+            'width' => $metadata['width'],
+            'height' => $metadata['height'],
+        ];
+    }
+
+    /**
+     * @return array{
+     *     width: int,
+     *     height: int,
+     *     variants: list<array{path: string, width: int}>,
+     *     webp_variants: list<array{path: string, width: int}>
+     * }|null
+     */
+    public static function metadata(string $path, ?string $disk = null): ?array
+    {
+        $key = self::metadataCacheKey($path, $disk);
+        $cached = self::cachedMetadata($key);
+
+        if (is_array($cached)) {
+            return $cached;
         }
 
         try {
+            $filesystem = self::filesystem($disk);
+
+            if (! $filesystem->exists($path)) {
+                return null;
+            }
+
             $contents = $filesystem->get($path);
 
             if ($contents === null) {
@@ -199,18 +224,88 @@ final class ResponsiveImage
             }
 
             $image = (new ImageManager(new Driver))->read($contents);
-
+            $metadata = [
-            return [
                 'width' => $image->width(),
                 'height' => $image->height(),
+                'variants' => self::existingVariants($filesystem, $path, false),
+                'webp_variants' => self::existingVariants($filesystem, $path, true),
             ];
+
+            self::storeMetadata($key, $metadata);
+
+            return $metadata;
         } catch (Throwable) {
             return null;
         }
     }
 
+    public static function forgetMetadata(string $path, ?string $disk = null): void
+    {
+        try {
+            Cache::forget(self::metadataCacheKey($path, $disk));
+        } catch (Throwable) {
+            // Cache availability must not block public media rendering or cleanup.
+        }
+    }
+
     private static function filesystem(?string $disk): Filesystem
     {
-        return Storage::disk($disk ?? PublicImageUploadRules::disk());
+        return Storage::disk(self::diskName($disk));
+    }
+
+    /**
+     * @return list<array{path: string, width: int}>
+     */
+    private static function existingVariants(Filesystem $filesystem, string $path, bool $webp): array
+    {
+        $variants = [];
+
+        foreach (self::WIDTHS as $width) {
+            $variantPath = $webp
+                ? self::webpVariantPath($path, $width)
+                : self::variantPath($path, $width);
+
+            if ($filesystem->exists($variantPath)) {
+                $variants[] = ['path' => $variantPath, 'width' => $width];
+            }
+        }
+
+        return $variants;
+    }
+
+    private static function metadataCacheKey(string $path, ?string $disk): string
+    {
+        return 'responsive-image:metadata:'.sha1(self::diskName($disk).'|'.$path);
+    }
+
+    /**
+     * @return array<string, mixed>|null
+     */
+    private static function cachedMetadata(string $key): ?array
+    {
+        try {
+            $cached = Cache::get($key);
+
+            return is_array($cached) ? $cached : null;
+        } catch (Throwable) {
+            return null;
+        }
+    }
+
+    /**
+     * @param  array<string, mixed>  $metadata
+     */
+    private static function storeMetadata(string $key, array $metadata): void
+    {
+        try {
+            Cache::forever($key, $metadata);
+        } catch (Throwable) {
+            // The uncached result remains safe to use for this request.
+        }
+    }
+
+    private static function diskName(?string $disk): string
+    {
+        return $disk ?? PublicImageUploadRules::disk();
     }
 }

composer.json

@@ -87,9 +87,6 @@
             "npm audit --omit=dev --audit-level=high",
             "@test"
         ],
-        "visual:update": [
-            "@php artisan test --testsuite=Browser --update-snapshots"
-        ],
         "post-autoload-dump": [
             "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
             "@php artisan package:discover --ansi",

config/app.php

@@ -73,7 +73,7 @@ return [
     |--------------------------------------------------------------------------
     |
     | When set outside production, the application clock is frozen for
-    | deterministic rendering (visual regression / seeded content).
+    | deterministic time-dependent tests or seeded content.
     |
     */
 

database/factories/WeddingPackageFactory.php

@@ -0,0 +1,33 @@
+<?php
+
+declare(strict_types=1);
+
+namespace Database\Factories;
+
+use App\Models\WeddingPackage;
+use Illuminate\Database\Eloquent\Factories\Factory;
+
+/** @extends Factory<WeddingPackage> */
+class WeddingPackageFactory extends Factory
+{
+    protected $model = WeddingPackage::class;
+
+    /** @return array<string, mixed> */
+    public function definition(): array
+    {
+        return [
+            'name' => fake()->unique()->words(2, true),
+            'level' => 'Assessoria',
+            'summary' => fake()->sentence(),
+            'scope_items' => [fake()->sentence()],
+            'cta_label' => 'Conversar sobre esta modalidade',
+            'sort_order' => 0,
+            'published_at' => null,
+        ];
+    }
+
+    public function published(): static
+    {
+        return $this->state(fn (): array => ['published_at' => now()]);
+    }
+}

database/migrations/2026_08_10_130000_add_immersive_hero_images_to_site_settings_table.php

@@ -0,0 +1,36 @@
+<?php
+
+declare(strict_types=1);
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    public function up(): void
+    {
+        Schema::table('site_settings', function (Blueprint $table): void {
+            $table->string('hero_image_path')->nullable()->after('hero_note');
+            $table->string('hero_image_alt')->nullable()->after('hero_image_path');
+            $table->string('services_hero_image_path')->nullable()->after('hero_image_alt');
+            $table->string('services_hero_image_alt')->nullable()->after('services_hero_image_path');
+            $table->string('portfolio_hero_image_path')->nullable()->after('services_hero_image_alt');
+            $table->string('portfolio_hero_image_alt')->nullable()->after('portfolio_hero_image_path');
+        });
+    }
+
+    public function down(): void
+    {
+        Schema::table('site_settings', function (Blueprint $table): void {
+            $table->dropColumn([
+                'hero_image_path',
+                'hero_image_alt',
+                'services_hero_image_path',
+                'services_hero_image_alt',
+                'portfolio_hero_image_path',
+                'portfolio_hero_image_alt',
+            ]);
+        });
+    }
+};

database/migrations/2026_08_11_010000_add_corporate_steps_to_site_settings_table.php

@@ -0,0 +1,24 @@
+<?php
+
+declare(strict_types=1);
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    public function up(): void
+    {
+        Schema::table('site_settings', function (Blueprint $table): void {
+            $table->jsonb('corporate_steps')->nullable()->after('method_steps');
+        });
+    }
+
+    public function down(): void
+    {
+        Schema::table('site_settings', function (Blueprint $table): void {
+            $table->dropColumn('corporate_steps');
+        });
+    }
+};

database/migrations/2026_08_11_190000_add_whatsapp_number_to_site_settings_table.php

@@ -0,0 +1,24 @@
+<?php
+
+declare(strict_types=1);
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    public function up(): void
+    {
+        Schema::table('site_settings', function (Blueprint $table): void {
+            $table->string('whatsapp_number')->nullable()->after('phone');
+        });
+    }
+
+    public function down(): void
+    {
+        Schema::table('site_settings', function (Blueprint $table): void {
+            $table->dropColumn('whatsapp_number');
+        });
+    }
+};

database/migrations/2026_08_11_190100_create_wedding_packages_table.php

@@ -0,0 +1,30 @@
+<?php
+
+declare(strict_types=1);
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    public function up(): void
+    {
+        Schema::create('wedding_packages', function (Blueprint $table): void {
+            $table->id();
+            $table->string('name');
+            $table->string('level');
+            $table->string('summary');
+            $table->jsonb('scope_items');
+            $table->string('cta_label');
+            $table->integer('sort_order')->default(0)->index();
+            $table->timestamp('published_at')->nullable()->index();
+            $table->timestamps();
+        });
+    }
+
+    public function down(): void
+    {
+        Schema::dropIfExists('wedding_packages');
+    }
+};

database/seeders/ContentSeeder.php

@@ -49,6 +49,7 @@ class ContentSeeder extends Seeder
         $this->seedServices();
         $this->seedPortfolioCases();
         $this->call(TestimonialsSeeder::class);
+        $this->call(WeddingPackagesSeeder::class);
     }
 
     private function seedSiteSettings(): void
@@ -61,6 +62,12 @@ class ContentSeeder extends Seeder
             'hero_cta_label' => 'Solicitar proposta',
             'hero_secondary_cta_label' => 'Conheça nosso olhar',
             'hero_note' => 'Planejamento cuidadoso, comunicação clara e execução segura — do primeiro encontro ao último detalhe.',
+            'hero_image_path' => $this->copyFixture('case-casamento-ana-lucas.jpg', 'content/heroes/home.jpg'),
+            'hero_image_alt' => 'Celebração ao ar livre em São Paulo',
+            'services_hero_image_path' => $this->copyFixture('service-eventos-corporativos.jpg', 'content/heroes/services.jpg'),
+            'services_hero_image_alt' => 'Mesa preparada para um evento corporativo',
+            'portfolio_hero_image_path' => $this->copyFixture('case-lancamento-verano.jpg', 'content/heroes/portfolio.jpg'),
+            'portfolio_hero_image_alt' => 'Ambientação de um evento de lançamento',
             'about_summary' => 'Assessoria boutique especializada em experiências memoráveis em São Paulo.',
             'about_image_path' => $this->copyFixture('about-image.jpg', 'content/about/about-image.jpg'),
             'about_image_alt' => 'Mesa de planejamento com caderno, café e guardanapos de pano',
@@ -69,6 +76,7 @@ class ContentSeeder extends Seeder
             'manifesto_body' => 'A Amare combina sensibilidade e precisão para criar encontros coerentes com cada cliente, marca e ocasião — sem fórmulas prontas, excessos ou ruído.',
             'method_intro' => 'Clareza em cada etapa. Tranquilidade durante todo o processo.',
             'method_steps' => SiteSetting::defaultMethodSteps(),
+            'corporate_steps' => SiteSetting::defaultCorporateSteps(),
             'principles' => SiteSetting::defaultPrinciples(),
             'email' => 'amareassessoriaeventos@gmail.com',
             'phone' => '(11) 99999-9999',

database/seeders/VisualContentSeeder.php

@@ -14,7 +14,7 @@ use Illuminate\Support\Carbon;
 use Illuminate\Support\Facades\Storage;
 
 /**
- * Deterministic content for visual regression. Keep separate from ContentSeeder demo data.
+ * Deterministic content and image fixtures. Keep separate from ContentSeeder demo data.
  */
 class VisualContentSeeder extends Seeder
 {
@@ -30,6 +30,7 @@ class VisualContentSeeder extends Seeder
         $this->seedServices();
         $this->seedPortfolioCases();
         $this->seedTestimonials();
+        $this->call(WeddingPackagesSeeder::class);
     }
 
     private function seedSiteSettings(): void
@@ -42,6 +43,12 @@ class VisualContentSeeder extends Seeder
             'hero_cta_label' => 'Solicitar proposta',
             'hero_secondary_cta_label' => 'Conheça nosso olhar',
             'hero_note' => 'Planejamento cuidadoso, comunicação clara e execução segura — do primeiro encontro ao último detalhe.',
+            'hero_image_path' => $this->writeSolidJpeg('visual/heroes/home.jpg', 1600, 1100, [218, 224, 205]),
+            'hero_image_alt' => 'Imagem editorial da home',
+            'services_hero_image_path' => $this->writeSolidJpeg('visual/heroes/services.jpg', 1600, 1100, [196, 200, 184]),
+            'services_hero_image_alt' => 'Imagem editorial de Serviços',
+            'portfolio_hero_image_path' => $this->writeSolidJpeg('visual/heroes/portfolio.jpg', 1600, 1100, [228, 226, 221]),
+            'portfolio_hero_image_alt' => 'Imagem editorial de Portfólio',
             'about_summary' => 'Assessoria boutique especializada em experiências memoráveis em São Paulo.',
             'about_image_path' => $this->writeSolidJpeg('visual/about/about-image.jpg', 1200, 900, [232, 228, 218]),
             'about_image_alt' => 'Imagem editorial da página Sobre',
@@ -50,6 +57,7 @@ class VisualContentSeeder extends Seeder
             'manifesto_body' => 'A Amare combina sensibilidade e precisão para criar encontros coerentes com cada cliente, marca e ocasião — sem fórmulas prontas, excessos ou ruído.',
             'method_intro' => 'Clareza em cada etapa. Tranquilidade durante todo o processo.',
             'method_steps' => SiteSetting::defaultMethodSteps(),
+            'corporate_steps' => SiteSetting::defaultCorporateSteps(),
             'principles' => SiteSetting::defaultPrinciples(),
             'email' => 'amareassessoriaeventos@gmail.com',
             'phone' => '(11) 99999-9999',
@@ -192,16 +200,22 @@ class VisualContentSeeder extends Seeder
      */
     private function writeSolidJpeg(string $destination, int $width, int $height, array $rgb): string
     {
+        $disk = Storage::disk('public');
+
+        if ($disk->exists($destination)) {
+            return $destination;
+        }
+
         $image = imagecreatetruecolor($width, $height);
         $color = imagecolorallocate($image, $rgb[0], $rgb[1], $rgb[2]);
         imagefilledrectangle($image, 0, 0, $width, $height, $color);
 
         ob_start();
-        imagejpeg($image, null, 90);
+        imagejpeg($image, null, 80);
         $binary = (string) ob_get_clean();
         imagedestroy($image);
 
-        Storage::disk('public')->put($destination, $binary);
+        $disk->put($destination, $binary);
 
         return $destination;
     }

database/seeders/WeddingPackagesSeeder.php

@@ -0,0 +1,71 @@
+<?php
+
+declare(strict_types=1);
+
+namespace Database\Seeders;
+
+use App\Models\WeddingPackage;
+use Illuminate\Database\Seeder;
+use Illuminate\Support\Carbon;
+
+/**
+ * Wedding package modalities shown on the home page (03 — Amare Casamentos).
+ * Copy is approved from the structural model preview (preview(1).html) and
+ * remains editable via the Filament resource.
+ */
+class WeddingPackagesSeeder extends Seeder
+{
+    private const PUBLISHED_AT = '2026-08-11 00:00:00';
+
+    public function run(): void
+    {
+        $packages = [
+            [
+                'name' => 'Essenza',
+                'level' => '01 / COMPLETA',
+                'summary' => 'Para casais que desejam contar com a Amare desde o planejamento até a realização do casamento.',
+                'scope_items' => [
+                    'Planejamento e organização',
+                    'Gestão de etapas e prioridades',
+                    'Acompanhamento de fornecedores',
+                    'Coordenação do grande dia',
+                ],
+                'cta_label' => 'Quero conhecer a Essenza',
+                'sort_order' => 1,
+            ],
+            [
+                'name' => 'Conduzione',
+                'level' => '02 / PARCIAL',
+                'summary' => 'Para quem já começou e deseja estruturar o que falta, organizar fornecedores e seguir com acompanhamento profissional.',
+                'scope_items' => [
+                    'Diagnóstico do planejamento',
+                    'Organização das pendências',
+                    'Gestão dos próximos passos',
+                    'Coordenação do grande dia',
+                ],
+                'cta_label' => 'Quero conhecer a Conduzione',
+                'sort_order' => 2,
+            ],
+            [
+                'name' => 'Grand Jour',
+                'level' => '03 / FINAL',
+                'summary' => 'Para casais que já planejaram o casamento e precisam de uma equipe para assumir alinhamentos e operação na reta final.',
+                'scope_items' => [
+                    'Imersão no planejamento existente',
+                    'Alinhamento de fornecedores',
+                    'Cronograma final',
+                    'Gestão da operação do evento',
+                ],
+                'cta_label' => 'Quero conhecer a Grand Jour',
+                'sort_order' => 3,
+            ],
+        ];
+
+        foreach ($packages as $package) {
+            WeddingPackage::query()->updateOrCreate(
+                ['name' => $package['name']],
+                [...$package, 'published_at' => Carbon::parse(self::PUBLISHED_AT)],
+            );
+        }
+    }
+}

docker/ci-runner.Dockerfile

@@ -1,61 +0,0 @@
-# Linux runner that reproduces CI's rendering environment for the visual
-# regression baselines. Not part of the application image and never deployed.
-#
-# Why this exists: the baselines are pixel artifacts of the machine that
-# rendered them. Pest Browser serves the Laravel kernel from an in-process Amp
-# server (vendor/pestphp/pest-plugin-browser/src/Drivers/LaravelHttpServer.php),
-# so FrankenPHP is not in the picture — what differs between a developer's Mac
-# and CI is the OS, the Chromium build and the font stack. Regenerating on
-# macOS produces baselines CI rejects, which is the whole reason commit
-# 4578457 exists. Before this file the recipe lived only as a checklist in
-# tasks.md and the image had to be reconstructed by archaeology.
-#
-# Mirrors the `browser` job in .github/workflows/ci.yml: Ubuntu 24.04,
-# PHP 8.4 with the same extension list, Node 22, and Playwright's own system
-# dependencies (which is where fonts-liberation comes from — StableScreenshot
-# forces `Arial`, and on Linux fontconfig resolves that to the
-# metric-compatible Liberation Sans).
-#
-# Driven by scripts/test/visual-update-ci.sh; see that script for usage.
-
-FROM ubuntu:24.04
-
-ENV DEBIAN_FRONTEND=noninteractive \
-    PLAYWRIGHT_BROWSERS_PATH=/opt/playwright-browsers
-
-RUN apt-get update \
-    && apt-get install -y --no-install-recommends \
-        ca-certificates \
-        curl \
-        git \
-        gnupg \
-        software-properties-common \
-        unzip \
-    && add-apt-repository -y ppa:ondrej/php \
-    && apt-get update \
-    && apt-get install -y --no-install-recommends \
-        php8.4-cli \
-        php8.4-bcmath \
-        php8.4-curl \
-        php8.4-gd \
-        php8.4-intl \
-        php8.4-mbstring \
-        php8.4-pgsql \
-        php8.4-sqlite3 \
-        php8.4-xml \
-        php8.4-zip \
-    && curl -fsSL https://deb.nodesource.com/setup_22.x | bash - \
-    && apt-get install -y --no-install-recommends nodejs \
-    && rm -rf /var/lib/apt/lists/*
-
-COPY --from=composer:2 /usr/bin/composer /usr/bin/composer
-
-# System libraries and fonts only. The browser binary itself is installed at
-# run time so its revision matches whatever playwright version package-lock
-# resolves, exactly as CI's `npx playwright install chromium --with-deps` does.
-RUN npx --yes playwright@1.62 install-deps chromium \
-    && rm -rf /root/.npm
-
-WORKDIR /app
-
-CMD ["bash"]

docs/evidence/lighthouse/README.md

@@ -101,9 +101,8 @@ páginas. Reencodados a 3× do maior render — lockup 149×144 (14 KiB) e mark
 As variantes `on-dark` foram reencodadas junto por consistência; nenhuma view as
 usa hoje.
 
-Isto absorve MAN-122: os 16 baselines visuais foram regenerados no runner Linux
+Isto absorve MAN-122: os ativos de marca foram reencodados sem alterar a forma
-(`scripts/test/visual-update-ci.sh`), e o diff é imperceptível a 2× de zoom —
+ou a cor percebida, reduzindo apenas o peso transferido.
-mesma forma, mesma cor, só menos bytes.
 
 Os arquivos versionados aqui são: `2026-08-10-local-antes.md` (commit `2e43fde`),
 `2026-08-10-local-etapa-fontes-e-marca.md` (passada intermediária) e
@@ -174,12 +173,11 @@ em ordem de custo:
 
 ## Cobertura que este trabalho não tem
 
-Os testes de regressão visual nunca exercitam `srcset` nem `<picture>`: nem
+Os testes browser não exercitam `srcset` nem `<picture>` com variantes geradas:
-`ContentSeeder` nem `VisualContentSeeder` geram variantes, e `media:generate-variants`
+nem `ContentSeeder` nem `VisualContentSeeder` geram variantes. Nesses cenários,
-não roda no runner visual. Naquele ambiente `availableVariants()` volta vazio e o
+`availableVariants()` volta vazio e o componente renderiza `<img>` puro. A
-componente renderiza `<img>` puro — foi por isso que os 16 baselines não mudaram
+cobertura do caminho com variantes fica nos testes de feature
-com a introdução do `<picture>`. A cobertura do caminho com variantes fica nos
+(`MediaImageComponentTest`).
-testes de feature (`MediaImageComponentTest`), não nos baselines.
 
 ## Staging
 

docs/superpowers/plans/2026-08-11-full-bleed-home-hero.md

@@ -0,0 +1,81 @@
+# Hero full-bleed da home Implementation Plan
+
+> **For agentic workers:** REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** Fazer a fotografia configurada do hero da home preencher toda a coluna direita abaixo do header, preservando a leitura editorial e o fallback sem foto.
+
+**Architecture:** `x-home.hero` continuará a renderizar as duas variantes. A variante com imagem usará uma grade full-width com a coluna textual ancorada à régua global e a mídia como segundo trilho sem container; a variante tonal permanece contida. Os testes de feature e browser documentam os contratos de markup, tamanho e responsividade.
+
+**Tech Stack:** Laravel Blade, Tailwind CSS 4 utilities, Pest feature/browser tests, Vite.
+
+---
+
+## Chunk 1: Layout e contratos do hero
+
+### Task 1: Cobrir o spread full-bleed
+
+**Files:**
+- Modify: `tests/Feature/PublicSite/ImmersivePhotoHeroTest.php`
+- Modify: `tests/Browser/HomeEditorialCadenceTest.php`
+
+- [ ] **Step 1: Escrever as expectativas de feature para a variante com foto**
+
+Exigir `data-split-hero`, `data-hero-content`, `data-motion="page-open"`, `data-reveal-group`, `aria-labelledby="hero-heading"`, `loading="eager"`, `fetchpriority="high"` e `sizes="(max-width: 767px) 100vw, 55vw"`. Com `hero_image_path` nulo, exigir `data-tonal-hero`, os mesmos atributos de motion/semântica, ausência de `data-split-hero` e ausência de `<img` dentro de `[data-tonal-hero]`.
+
+- [ ] **Step 2: Estender a verificação browser de geometria**
+
+No viewport 1440×1000, obter os retângulos de `.site-header`, `[data-chapter="hero"]`, `[data-hero-content]` e `[data-split-hero]`; esperar, com tolerância de 1px, que `hero.top === header.bottom`, `media.top === hero.top`, `media.bottom === hero.bottom`, `media.right === innerWidth` e `hero.height === innerHeight - header.height`. No viewport 390×844, comparar `data-split-hero` com `[data-hero-content]`; esperar que a mídia inicie depois do conteúdo, que `width / height` fique entre 0,79 e 0,81, e que não exista overflow horizontal. Antes das duas visitas de fallback, zerar `hero_image_path`; numa visita com reduced motion, esperar conteúdo visível. Em outra com `reducedMotion: no-preference` e `IntersectionObserver` desabilitado antes da navegação, esperar ausência de `data-motion` em `document.documentElement`, cada `[data-motion="page-open"]` com `.is-active`, cada `[data-reveal]` com `.is-revealed` e `aria-labelledby="hero-heading"`.
+
+- [ ] **Step 3: Executar os testes focados e confirmar a falha inicial**
+
+Run: `php artisan test tests/Feature/PublicSite/ImmersivePhotoHeroTest.php && php artisan test tests/Browser/HomeEditorialCadenceTest.php`
+
+Expected: falha nas novas expectativas de geometria/markup até a alteração do componente.
+
+### Task 2: Implementar a grade full-bleed
+
+**Files:**
+- Modify: `resources/views/components/home/hero.blade.php`
+
+- [ ] **Step 1: Separar a variante com imagem do container compartilhado**
+
+Substituir `min-h-[100dvh]` do `<section>` por `md:h-[calc(100dvh-5rem)]` quando `hero_image_path` estiver preenchido e renderizar um wrapper `grid min-h-[calc(100dvh-5rem)] md:h-full md:grid-cols-[minmax(0,0.9fr)_minmax(0,1.1fr)]`. A coluna de texto deve manter `data-reveal-group`, receber `data-hero-content`, ter `padding-left: max(var(--amare-container-padding), calc((100vw - var(--amare-container-max)) / 2 + var(--amare-container-padding)))`, padding direito fluido e centralização vertical.
+
+- [ ] **Step 2: Tornar a mídia contínua**
+
+Aplicar ao bloco `data-split-hero` `overflow-hidden`, `bg-amare-bg-deep`, `md:min-h-full`; abaixo de `md`, aplicar `aspect-[4/5]`. Manter `data-motion-beat="media"`, `data-reveal-media`, `object-cover`, path/alt CMS e mudar `sizes` para `(max-width: 767px) 100vw, 55vw`.
+
+- [ ] **Step 3: Preservar o fallback**
+
+Manter o wrapper tonal existente para hero sem imagem, com `data-tonal-hero`, `data-motion="page-open"` e `data-reveal-group`; não renderizar o bloco de mídia nessa variante.
+
+- [ ] **Step 4: Executar os testes focados e confirmar a passagem**
+
+Run: `php artisan test tests/Feature/PublicSite/ImmersivePhotoHeroTest.php && php artisan test tests/Browser/HomeEditorialCadenceTest.php`
+
+Expected: PASS.
+
+### Task 3: Verificar e registrar
+
+**Files:**
+- Modify: `resources/views/components/home/hero.blade.php`
+- Modify: `tests/Feature/PublicSite/ImmersivePhotoHeroTest.php`
+- Modify: `tests/Browser/HomeEditorialCadenceTest.php`
+
+- [ ] **Step 1: Formatar e executar as verificações proporcionais**
+
+Run: `composer pint && composer phpstan && composer test:feature && composer test:browser && npm run build`
+
+Expected: todos os comandos passam.
+
+- [ ] **Step 2: Inspecionar o diff e registrar**
+
+Run: `git diff --check && git status --short`
+
+Expected: apenas os três arquivos de implementação/testes e a documentação deste plano/especificação aparecem como escopo.
+
+- [ ] **Step 3: Commit**
+
+Run: `git add resources/views/components/home/hero.blade.php tests/Feature/PublicSite/ImmersivePhotoHeroTest.php tests/Browser/HomeEditorialCadenceTest.php docs/superpowers && git commit -m "feat(home): tornar hero fotográfico full-bleed"`
+
+Expected: commit focado, sem artefatos de build ou screenshots.

docs/superpowers/specs/2026-08-11-full-bleed-home-hero-design.md

@@ -0,0 +1,31 @@
+# Hero da home com fotografia full-bleed
+
+## Objetivo
+
+Dar à fotografia do hero da home a mesma presença contínua da referência aprovada: no desktop, ela preenche integralmente a coluna direita abaixo do header; o conteúdo editorial permanece concentrado na coluna esquerda.
+
+## Escopo
+
+- Alterar somente o componente `resources/views/components/home/hero.blade.php` e seus testes diretos.
+- Quando `hero_image_path` existir, usar uma grade externa `0.9fr / 1.1fr` a partir de `md` (768px), com altura exata `calc(100dvh - 5rem)`: o espaço restante depois do header desktop. A mídia deve chegar ao topo e à base da seção, sem padding vertical ou lateral de container.
+- Manter o texto, CTAs, imagem CMS, `alt`, carregamento eager, `fetchpriority`, responsividade de imagem e atributos de motion existentes.
+- Abaixo de `md`, manter a ordem texto seguido de imagem, sem overflow horizontal, e fixar a mídia em `aspect-ratio: 4 / 5` com `object-cover`.
+- Quando não houver imagem configurada, manter a abertura tonal, tipográfica e contida já existente, sem área vazia para mídia.
+
+## Fora de escopo
+
+- Não alterar conteúdo do CMS, imagens, Open Graph, outras rotas públicas, header, animações, tokens globais ou dependências.
+- Não criar ou publicar mídia nova.
+
+## Estrutura
+
+O componente continuará sendo a única unidade de layout do hero. A variante com foto terá um wrapper full-width em desktop. A coluna textual terá `data-hero-content`, margem esquerda `max(var(--amare-container-padding), calc((100vw - var(--amare-container-max)) / 2 + var(--amare-container-padding)))`, a mesma régua esquerda de `container-amare`, e padding direito fluido para não comprimir a leitura. O bloco de mídia ocupará os 55% da grade, receberá `data-split-hero` e `data-reveal-media`, e deixará de ficar limitado pelo container. O atributo `sizes` será `(max-width: 767px) 100vw, 55vw`. A variante sem foto permanece no wrapper atual.
+
+## Critérios de aceitação
+
+- Em desktop, `data-split-hero` inicia sob o header e mede `calc(100dvh - 5rem)`, sem margens externas de container.
+- A foto usa `object-cover`, `loading="eager"`, `fetchpriority="high"`, path/alt próprios do hero e `sizes="(max-width: 767px) 100vw, 55vw"`.
+- Em mobile, o conteúdo essencial continua acessível antes da foto, sem overflow nem texto recortado.
+- O fallback sem foto continua com `data-tonal-hero`, sem `data-split-hero` e sem mídia renderizada.
+- `data-motion="page-open"`, `data-reveal-group`, beats existentes, motion reduzido, CTAs e semântica atual continuam funcionais.
+- Testes verificam os contratos full-bleed da variante com foto, a ausência de mídia no fallback, e a continuidade de motion/semântica.

openspec/changes/2026-08-11-home-editorial-redesign/design.md

@@ -0,0 +1,36 @@
+# Design — Home editorial conforme preview
+
+Fonte de verdade visual: modelo estrutural validado (`preview(1).html`) + tokens `resources/css/tokens.css` (inalterados; assertados por `HeritageEditorialTokensTest`). Paleta do preview já mapeada para os utilitários `amare-*`.
+
+## Estrutura da home (8 capítulos)
+
+| Capítulo | Id/âncora | Componente | Conteúdo |
+|---|---|---|---|
+| Hero | — | `x-home.hero` | Eyebrow fixo, h1 fixo, lede fixo, CTAs "Conhecer a Amare" (`#sobre`) + "Enviar briefing" (`#contato`), arte `hero_image_path` ou placeholder rotulado "Fotografia hero" |
+| 01 — A Amare | `#sobre` | `x-home.manifesto` | Editorial-split 0.8fr/1.2fr; statement fixo + placeholder institucional |
+| 02 — Duas vertentes | `#vertentes` | `x-home.vertentes` | 2 cards (Casamentos/Corporate) com overlay gradiente 43%, CTAs para âncoras |
+| 03 — Amare Casamentos | `#casamentos` | `x-home.packages` | Grid 3 colunas com bordas (Eyebrow/título/descrição/items/CTA primário → `contact`), bloco de orientação accent-deep + nota de nomenclatura |
+| 04 — Amare Corporate | `#corporate` | `x-home.corporate` | Etapas `corporate_steps` (número 44px, bordas) + placeholder "Portfólio Corporate / Conteúdo em construção" |
+| 05 — Portfólio | `#portfolio` | `x-home.portfolio` | Grid 1.2fr/0.8fr/0.8fr, 1 foto alta (row-span-2, 634px) + 4; cases reais ou labels "FOTO 0X" |
+| 06 — Depoimentos | `#depoimentos` | `x-home.testimonials` | 3 cards brancos com borda; sem carrossel; placeholders até completar 3 |
+| 07 — Briefing | `#contato` | `x-home.briefing` | Formulário completo reusando `contact.store` (underline inputs, labels uppercase 12px, honeypot `#empresa`, checkbox LGPD) |
+
+## Padrões visuais
+
+- Seções: `home-chapter border-b border-amare-border bg-amare-bg`, padding `py-16 md:py-24`, `container-amare`, `data-reveal-group` + blocos `data-reveal data-reveal-from="up"`.
+- Eyebrow: `text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep`.
+- h2 `clamp(2.375rem,5vw,4rem)`, h3 `clamp(1.5625rem,2.7vw,2.125rem)`, lede `clamp(1.1875rem,2vw,1.5rem)` max-w 760px, `leading-[1.55]`.
+- Botão primário: `min-h-[48px] bg-amare-accent text-amare-accent-text uppercase text-xs font-bold tracking-[0.09em]`, hover accent-deep; contorno: `border-amare-accent text-amare-accent-deep`; em bloco escuro: `border-amare-accent-text text-amare-accent-text`.
+- Header: sticky 74px, `bg-amare-bg/95 backdrop-blur-sm`, nav 13px uppercase `tracking-[0.08em]`, botão "Conte seu evento" → `contact`.
+- Footer: `py-14 md:py-[58px]`, marca + "Assessoria & produção de eventos • São Paulo", social links do settings ou placeholder "Instagram · WhatsApp · E-mail · LinkedIn (quando confirmado)".
+
+## Acessibilidade
+
+- Âncoras `aria-labelledby` por seção; foco/ordem tab preservados; skip-link intacto.
+- `prefers-reduced-motion`: blocos globais em tokens.css (0.01ms) — nenhum motion extra adicionado.
+- Erros de validação do briefing com `role="alert"` e `aria-describedby`; honeypot oculto.
+- Contrastes: accent `#556B2F` sobre bg `#FBF9F4` ≈ 4.6:1; accent-text branco sobre accent ≈ 6.9:1; muted `#5D6155` sobre bg ≈ 5.4:1 (dentro do AA).
+
+## Fora de escopo visual
+
+Copy final institucional (placeholders), acervo fotográfico autorizado, canal de fornecedores (pós-MVP), folios ornamentais, carrossel, parallax.

openspec/changes/2026-08-11-home-editorial-redesign/proposal.md

@@ -0,0 +1,33 @@
+# Home editorial conforme preview estrutural
+
+## Why
+
+A home atual não reflete a direção editorial aprovada para o site (Dossiê Editorial do Evento). O cliente validou um modelo estrutural (`preview(1).html`) que demonstra hierarquia, jornada e diferenciação de fluxos: hero editorial, editorial-split institucional, duas vertentes (Casamentos/Corporate), modalidades de casamento com orientação humana, frente corporativa honesta sobre portfólio em construção, portfólio curado, depoimentos sem carrossel e briefing comercial único. A home também é a porta de conversão primária (briefing), então a apresentação deve construir confiança antes de pedir conversão.
+
+## What Changes
+
+- **Home em 8 seções** (componentes `x-home.*`): hero assimétrico (1.1fr/0.9fr, arte rotulada até acervo autorizado), `01 — A Amare` (editorial-split), `02 — Duas vertentes` (2 cards), `03 — Amare Casamentos` (grid de modalidades com bordas + bloco de orientação em accent-deep), `04 — Amare Corporate` (etapas + placeholder "Conteúdo em construção"), `05 — Portfólio` (1 foto alta + 4), `06 — Depoimentos` (3 cards, sem carrossel), `07 — Briefing comercial` (formulário completo reaproveitando `contact.store`).
+- **Novo modelo `WeddingPackage`** (Modalidades): migration, model com publication, factory, policy, seeder com copy exata do preview (Essenza/Conduzione/Grand Jour) e recurso Filament "Modalidades" com repeater de itens.
+- **`SiteSetting.corporate_steps`**: JSON de 3 etapas (Planejamento/Produção/Execução), editável via repeater no `ManageSiteSettings`, semeadas nos dois seeders.
+- **Header/footer globais** restilizados conforme preview (barra 74px, nav uppercase 13px, botão "Conte seu evento", footer editorial), preservando menu mobile, skip-link, logo e links legais.
+- Motion mantém convenções existentes (`data-motion="page-open"`, `data-motion-beat`, `data-reveal`), respeitando `prefers-reduced-motion` global.
+
+## Non-Goals
+
+- Copy final institucional onde o preview declara placeholder (ex.: "Aqui entra a apresentação institucional da marca e da Michele…") — permanece placeholder.
+- Fotografias autorizadas da Amare (acervo ainda em organização) — imagens permanecem rotuladas.
+- Canal/forma de fornecedores e parcerias (pós-MVP, caixa tracejada) — não misturar ao briefing comercial.
+- Carrossel de depoimentos, parallax, scroll-jacking ou folios ornamentais.
+- Alteração de tokens do design system (assertados por `HeritageEditorialTokensTest`).
+
+## Capabilities
+
+### New Capabilities
+
+- `wedding-packages`: cadastro de modalidades de casamento (Essenza/Conduzione/Grand Jour) com itens, ordenação e publicação via Filament; exibidas na home na seção `03 — Amare Casamentos`.
+
+### Modified Capabilities
+
+- `public-site-pages`: home recomposta em 8 capítulos com âncoras (`#sobre`, `#vertentes`, `#casamentos`, `#corporate`, `#portfolio`, `#depoimentos`, `#contato`); header/footer globais restilizados; briefing da home reutiliza o fluxo `contact.store` existente.
+- `content-media`: heróis continuam usando `hero_image_path` com fallback tipográfico rotulado; portfólio usa `featuredCases` reais ou labels provisórios.
+- `design-tokens`: nenhum valor alterado; novos componentes usam os tokens existentes via utilitários `amare-*`.

openspec/changes/2026-08-11-home-editorial-redesign/specs/wedding-packages/spec.md

@@ -0,0 +1,22 @@
+# Wedding Packages
+
+## Purpose
+
+Cadastro editorial das modalidades de acompanhamento de casamento oferecidas pela Amare (Essenza, Conduzione, Grand Jour). Fonte única de verdade para a seção `03 — Amare Casamentos` da home.
+
+## Functional Requirements
+
+- FR-1: Um pacote contém `eyebrow` (ex.: "01 / COMPLETA"), `title` (ex.: "Essenza"), `description`, lista ordenada de `items` (o que está incluído) e `sort_order`.
+- FR-2: Publicação via `published_at` (modelo usa `HasPublication`); pacotes rascunho nunca aparecem na home.
+- FR-3: A home renderiza pacotes publicados ordenados por `sort_order`, cada um com CTA primário "Quero conhecer a {title}" apontando para o briefing (`route('contact')`).
+- FR-4: O recurso Filament "Modalidades" (grupo "Conteúdo do site") permite criar/editar/excluir pacotes e ajustar itens via repeater; acesso restrito a admins (`WeddingPackagePolicy`).
+
+## Non-Requirements
+
+- Nenhum vínculo com checkout/pagamento nesta capacidade.
+- Nomenclaturas exibidas são provisórias até confirmação com a cliente (nota visível na home).
+
+## Data
+
+- Tabela `wedding_packages` (migration `2026_08_11_000000`): `eyebrow string`, `title string`, `description text`, `items json`, `sort_order int`, `published_at timestamp nullable`, timestamps.
+- Seed padrão (ambos os seeders): Essenza `01 / COMPLETA`, Conduzione `02 / PARCIAL`, Grand Jour `03 / FINAL`, com copy exata do preview estrutural.

openspec/changes/2026-08-11-home-editorial-redesign/tasks.md

@@ -0,0 +1,18 @@
+# Tasks — Home editorial conforme preview
+
+## Concluído
+
+- [x] **T0** Worktree `.worktrees/home-redesign` (branch `feat/home-redesign`) a partir de `main`.
+- [x] **T1** `WeddingPackage` (model + migration `2026_08_11_000000` + factory + policy + seeder + recurso Filament "Modalidades"): 3 modalidades semeadas com copy exata do preview; seeders `ContentSeeder`/`VisualContentSeeder` passam a chamar `WeddingPackagesSeeder`.
+- [x] **T2** `SiteSetting.corporate_steps` (migration `2026_08_11_010000`, `defaultCorporateSteps()`, casts/fillable/docblock, repeater em `ManageSiteSettings`, seeders atualizados).
+- [x] **T3** Header/footer globais (`layouts/public.blade.php`) restilizados conforme preview; menu mobile, skip-link, logo e links legais preservados.
+- [x] **T4** Home recomposta em 8 seções (`x-home.*`: hero, manifesto/sobre, vertentes, packages, corporate, portfolio, testimonials, briefing); `HomeContent` ganha `packages`; `GetHomeContent` busca pacotes publicados por `sort_order`.
+- [x] **T5** Motion via convenções existentes (`data-reveal`, `data-motion-beat`, `data-motion="page-open"`); `prefers-reduced-motion` global respeitado; sem carrossel/parallax.
+- [x] **T6** Testes: `HomePageContentTest` reescrito (8 seções, packages, corporate steps, briefing form, placeholders), `HomePageTest`, `GetHomeContentTest` (packages), `ImmersivePhotoHeroTest`/`MotionMarkupTest` atualizados para o novo contrato, `HomeEditorialCadenceTest` reescrito para o layout assimétrico. **178 feature + 42 unit verdes**.
+- [x] **T7** `composer pint` + `phpstan` limpos; 2 commits convencionais; PR #53 aberto.
+
+## Pendente
+
+- [ ] **T8** Proposta openspec (este change) revisada e arquivada após merge.
+- [ ] Merge do PR #53 após CI verde; limpeza do worktree (`git worktree remove`).
+- [ ] Follow-up pós-merge: confirmar nomenclaturas das modalidades com a cliente (nota na home: "Nomenclaturas exibidas conforme materiais/reunião; confirmar versão final antes da publicação.").

openspec/changes/archive/2026-08-10-remove-visual-regression/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-08-11

openspec/changes/archive/2026-08-10-remove-visual-regression/design.md

@@ -0,0 +1,37 @@
+## Context
+
+A suíte browser contém uma camada exclusiva de comparação de pixels: um teste com baselines versionados, um trait para estabilizar capturas, exportação de diffs e configuração de CI para seeds e artefatos determinísticos. O restante da cobertura browser — smoke, acessibilidade, motion e fixtures de conteúdo — não depende dessa camada.
+
+## Goals / Non-Goals
+
+**Goals:**
+
+- Remover integralmente a comparação de pixels, os baselines e a infraestrutura exclusiva de suporte.
+- Manter o job browser em FrankenPHP e suas verificações funcionais, de acessibilidade e motion.
+- Atualizar as fontes normativas e as specs ativas para que não exijam snapshots visuais.
+
+**Non-Goals:**
+
+- Não substituir a comparação de pixels por outro serviço ou ferramenta de regressão visual.
+- Não remover `VisualContentSeeder`, fixtures JPEG, `APP_FROZEN_NOW` que tenham usos fora das capturas, screenshots documentais ou testes browser não relacionados.
+- Não alterar APIs públicas, rotas, conteúdo nem comportamentos de interface.
+
+## Decisions
+
+1. **Eliminar a capability em vez de reduzir a matriz.** Todos os requisitos de `visual-regression` serão removidos, pois o produto não terá mais comparação de pixels. Alternativa rejeitada: conservar apenas algumas telas, pois ainda manteria baselines e o custo operacional indesejado.
+2. **Preservar diagnósticos gerais de browser.** O CI manterá screenshots, logs e relatórios úteis a falhas funcionais; serão removidos apenas seed global, relógio congelado e artefatos específicos de baseline/diff. Alternativa rejeitada: retirar todos os diagnósticos, pois reduziria a capacidade de investigar falhas não visuais.
+3. **Separar determinismo reutilizável da captura visual.** `VisualContentSeeder` e `APP_FROZEN_NOW` permanecem quando usados por outros testes ou pela aplicação; somente as referências exclusivas a screenshot são excluídas. Alternativa rejeitada: remover os nomes por associação, pois quebraria fixtures e cenários existentes.
+
+## Risks / Trade-offs
+
+- [Uma mudança puramente visual deixa de bloquear CI] → acessibilidade, smoke, motion e revisão humana continuam no fluxo de qualidade.
+- [Remover preparação comum do job browser afeta testes restantes] → inspecionar usos de seed/relógio e executar a suíte browser contra FrankenPHP após a alteração.
+- [Uma spec ativa ainda reintroduz snapshots] → remover as menções no delta de `enhance-public-motion` antes da validação OpenSpec.
+
+## Migration Plan
+
+Publicar a remoção junto com a atualização da documentação e do CI; não há migração de dados. O rollback é um revert do commit, restaurando os arquivos versionados e a configuração anterior.
+
+## Open Questions
+
+Nenhuma.

openspec/changes/archive/2026-08-10-remove-visual-regression/proposal.md

@@ -0,0 +1,25 @@
+## Why
+
+As comparações pixel-a-pixel e seus baselines adicionam manutenção e infraestrutura exclusiva sem serem um gate de qualidade desejado. A qualidade do site continuará protegida por jornadas browser, acessibilidade, motion, smoke e screenshots documentais, sem dependência de snapshots versionados.
+
+## What Changes
+
+- Remove a capability `visual-regression` e todos os requisitos de baselines, snapshots e diffs visuais.
+- Atualiza os quality gates para manter a cobertura browser funcional, de acessibilidade e motion sem comparações de pixels.
+- Remove a infraestrutura de testes, CI e documentação usada exclusivamente para regressão visual.
+- **BREAKING** para contribuidores: o comando `composer visual:update` deixa de existir.
+
+## Capabilities
+
+### New Capabilities
+
+Nenhuma.
+
+### Modified Capabilities
+
+- `visual-regression`: Remover os requisitos da capability descontinuada.
+- `quality-gates`: Remover a exigência de executar e publicar diagnósticos de snapshots visuais.
+
+## Impact
+
+Afeta os testes browser e seus helpers exclusivos, baselines rastreados, configuração de Composer e CI, `.gitignore`, `SPEC.md` e a documentação ativa de motion. Não altera rotas, APIs, dados de conteúdo, fixtures reutilizadas, nem a cobertura funcional, de acessibilidade ou motion.

openspec/changes/archive/2026-08-10-remove-visual-regression/specs/quality-gates/spec.md

@@ -0,0 +1,21 @@
+## MODIFIED Requirements
+
+### Requirement: Browser tests run against FrankenPHP-served application
+
+The system SHALL execute browser tests using Pest Browser/Playwright against an application served by FrankenPHP in CI. The `browser` job MUST cover the E2E journeys available in the current phase, the automated accessibility checks, motion behavior and smoke checks for public routes (SPEC §13.4, §13.7 and §14.1), without pixel comparison.
+
+#### Scenario: Browser job validates served application
+
+- **WHEN** the `browser` CI job runs
+- **THEN** tests execute against the built application artifact or equivalent production-like image
+
+#### Scenario: Browser job covers functional, accessibility and motion assertions
+
+- **WHEN** the `browser` CI job runs
+- **THEN** it MUST execute the functional browser, accessibility, motion and smoke suites
+- **AND** a failing functional assertion or a critical/serious accessibility issue MUST block merge
+
+#### Scenario: Browser failures publish diagnostics
+
+- **WHEN** a browser test fails in CI
+- **THEN** the job MUST publish screenshots, application logs and browser logs as diagnostics

openspec/changes/archive/2026-08-10-remove-visual-regression/specs/visual-regression/spec.md

@@ -0,0 +1,13 @@
+## REMOVED Requirements
+
+### Requirement: Public screens have desktop and mobile visual baselines
+**Reason**: O projeto não manterá mais comparação de pixels nem baselines versionados para telas públicas.
+**Migration**: Remover as asserções de screenshot e os arquivos baseline; manter testes browser funcionais, de acessibilidade, motion e smoke.
+
+### Requirement: Visual runs are deterministic
+**Reason**: Não haverá execução de captura para comparação visual.
+**Migration**: Preservar seeds e relógio congelado apenas onde forem necessários por outros testes.
+
+### Requirement: Baseline updates are explicit and reviewed
+**Reason**: O comando e o fluxo de atualização de baselines foram descontinuados junto com a capability.
+**Migration**: Remover `composer visual:update` e qualquer configuração de CI dedicada a regenerar, transportar ou publicar baselines e diffs.

openspec/changes/archive/2026-08-10-remove-visual-regression/tasks.md

@@ -0,0 +1,19 @@
+## 1. Contratos normativos
+
+- [x] 1.1 Remover os requisitos e critérios de regressão visual de `SPEC.md`, ADR-005 e do delta ativo `enhance-public-motion`.
+- [x] 1.2 Sincronizar os deltas da mudança para remover a capability `visual-regression` e atualizar `quality-gates`.
+
+## 2. Infraestrutura de regressão visual
+
+- [x] 2.1 Remover o teste browser, os 16 baselines, o trait de screenshot, o exportador de diffs e seu teste unitário.
+- [x] 2.2 Simplificar o `TestCase` e remover o script Composer e a regra de ignore exclusivos de baselines.
+
+## 3. Browser CI e documentação operacional
+
+- [x] 3.1 Remover seed global, relógio congelado e cópias de snapshots/diffs exclusivos de baseline do job browser, preservando diagnósticos funcionais.
+- [x] 3.2 Atualizar a documentação operacional que referencia o fluxo descontinuado sem afetar fixtures ou congelamento usados fora dele.
+
+## 4. Verificação e arquivamento
+
+- [x] 4.1 Confirmar ausência dos símbolos e comandos removidos no código ativo e executar os gates de qualidade aplicáveis.
+- [x] 4.2 Validar OpenSpec estritamente, marcar as tarefas e arquivar a mudança sincronizada.

openspec/changes/archive/2026-08-11-enhance-public-motion/design.md

@@ -10,7 +10,7 @@ O site público usa Blade/Tailwind e já contém um runtime pequeno em `resource
 - Manter texto legível durante toda entrada, animando somente `transform` e recorte de mídia.
 - Garantir enhancement progressivo: estado final imediato sem JavaScript, observer ou com movimento reduzido.
 - Preservar interação, foco, validação e ausência de overflow em desktop/mobile.
-- Cobrir marcação, comportamento real, acessibilidade, console e capturas determinísticas.
+- Cobrir marcação, comportamento real, acessibilidade e console.
 
 **Non-Goals:**
 
@@ -32,15 +32,14 @@ O site público usa Blade/Tailwind e já contém um runtime pequeno em `resource
 
 6. **Progresso com coalescência por frame.** Eventos de scroll apenas agendam uma atualização por `requestAnimationFrame`; o cálculo existente é preservado. Alternativa rejeitada: calcular em todo evento, que multiplica leituras/escritas durante scroll.
 
-7. **Testes em camadas.** Feature tests comprovam contratos Blade/CSS/JS e renderização de erros; browser tests comprovam entrada, stagger, direções, reduced motion, fallback, interação, overflow e console. Axe/snapshots passam a incluir sobre, contato, privacidade e 404; demais erros ficam em renderização feature.
+7. **Testes em camadas.** Feature tests comprovam contratos Blade/CSS/JS e renderização de erros; browser tests comprovam entrada, stagger, direções, reduced motion, fallback, interação, overflow e console. Axe e console incluem sobre, contato, privacidade e 404; demais erros ficam em renderização feature.
 
 ## Risks / Trade-offs
 
 - [Conteúdo pisca entre estado final e início do enhancement] → inicializar no primeiro módulo Vite, limitar transformações a distâncias pequenas e nunca ocultar texto.
 - [Transforms laterais causam overflow horizontal] → limitar distância por breakpoint, manter recorte no contêiner público e testar `scrollWidth` em ambos viewports.
-- [Snapshots ficam instáveis] → continuar capturando com `reducedMotion: reduce` e transições desabilitadas.
 - [Muitos observers/estilos inline] → usar um único observer, custom property de índice limitada e `unobserve` imediato.
-- [Páginas de erro não carregam o runtime em todos os contextos] → o estado final é o baseline seguro; feature tests cobrem os cinco templates.
+- [Páginas de erro não carregam o runtime em todos os contextos] → o estado final é seguro; feature tests cobrem os cinco templates.
 
 ## Migration Plan
 

openspec/changes/archive/2026-08-11-enhance-public-motion/proposal.md

@@ -9,7 +9,7 @@ O site público já possui uma abertura focal na home, mas o restante da experi
 - Alternar depoimentos entre esquerda e direita, filtrando citações vazias antes de renderizar a sequência.
 - Adicionar feedback curto e não bloqueante a links, CTAs, navegação e controles de formulário, preservando foco e mensagens de validação.
 - Garantir estado final imediato sem JavaScript, sem `IntersectionObserver` e com `prefers-reduced-motion: reduce`.
-- Limitar o progresso/índice da home a uma atualização por frame e ampliar testes de marcação, browser, acessibilidade, console e regressão visual.
+- Limitar o progresso/índice da home a uma atualização por frame e ampliar testes de marcação, browser, acessibilidade e console.
 - Não objetivos: não criar transições entre rotas, alterar conteúdo ou layout estrutural, adicionar biblioteca de animação, modificar CMS/API/banco/Filament, nem introduzir itens fora do MVP listados em SPEC.md §4.2.
 
 ## Capabilities
@@ -23,7 +23,6 @@ O site público já possui uma abertura focal na home, mas o restante da experi
 - `design-tokens`: Especificar tokens compartilhados de duração, stagger, distância e easing para motion editorial.
 - `public-site-pages`: Cobrir todas as páginas públicas visuais e templates de erro com o contrato compartilhado de abertura e reveal.
 - `testimonials`: Filtrar citações vazias e alternar explicitamente a direção de entrada dos depoimentos renderizados.
-- `visual-regression`: Ampliar a matriz visual para sobre, contato, privacidade e 404, mantendo capturas determinísticas sem animação.
 - `web-accessibility`: Ampliar axe/console e validar conteúdo imediatamente utilizável com movimento reduzido ou enhancement indisponível.
 
 ## Impact

openspec/changes/archive/2026-08-11-enhance-public-motion/tasks.md

@@ -15,10 +15,10 @@
 - [x] 3.1 Add browser tests for real opening/reveal state, 90 ms capped stagger, one-shot observation and interaction during motion
 - [x] 3.2 Add desktop/mobile tests for directional distance, reduced motion final state, no-JS/observer fallback, horizontal overflow and clean console
 - [x] 3.3 Extend axe and console route matrices to about, contact, privacy and branded 404
-- [x] 3.4 Extend deterministic desktop/mobile visual snapshots to about, contact, privacy and branded 404 and review the generated diffs
+- [x] 3.4 Extend axe and console route matrices to about, contact, privacy and branded 404
 
 ## 4. Verification and delivery
 
 - [x] 4.1 Run focused feature/browser tests, build, Pint, isolated-cache PHPStan and strict OpenSpec validation
 - [x] 4.2 Run `composer quality` and visually review desktop/mobile with normal and reduced motion
-- [ ] 4.3 Stage only scoped files, commit conventionally, open a PR with screenshots and verification evidence, watch CI to green, merge and remove the worktree
+- [x] 4.3 Stage only scoped files, commit conventionally, open a PR with screenshots and verification evidence, watch CI to green, merge and remove the worktree — delivered in PR #22 with the requested screenshots and local verification; the PR merged as `0aee15e`, the worktree/remote branch no longer exists, and the current implementation is covered by all five green CI jobs on `main` (run 31501097667). Pixel snapshots were later removed by PR #44 and are not part of the current gate.

openspec/changes/archive/2026-08-11-recompose-public-editorial/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-08-11

openspec/changes/archive/2026-08-11-recompose-public-editorial/design.md

@@ -0,0 +1,44 @@
+## Context
+
+O commit de base ja separa as imagens hero de Open Graph, oferece variantes responsivas, fallbacks tonais e preserva o formulario de briefing. As views publicas ainda usam algumas grades simetricas, especialmente nas colecoes de portfolio. A referencia aprovada define composicao e materialidade, nunca novo acervo ou copy.
+
+## Goals / Non-Goals
+
+**Goals:**
+
+- Aplicar uma cadencia de campos tonais, regras e proporcoes alternadas nas paginas narrativas.
+- Manter uma ordem DOM linear e completa em telas pequenas.
+- Reforcar os contratos existentes de acessibilidade, motion progressivo, performance de imagem e SEO.
+
+**Non-Goals:**
+
+- Alterar dados CMS, contratos de rota, controller, metadata, uploads, variantes ou o formulario.
+- Usar imagens externas, criar conteudo comercial, adicionar dependencias, atualizar snapshots ou reintroduzir regressao visual.
+
+## Decisions
+
+### Usar variacoes de `col-span` e `aspect-ratio` nas galerias existentes
+
+As imagens continuam no mesmo componente responsivo, mas a primeira imagem e os itens pares recebem encaixes editoriais no desktop. A alternativa seria uma galeria JavaScript ou masonry; foi descartada por prejudicar a ordem de leitura e adicionar comportamento sem necessidade.
+
+### Aplicar assimetria pela composicao, nao por posicionamento absoluto
+
+Grid responsivo, margens e campos tonais criam o deslocamento sem tirar conteudo do fluxo. Isso preserva foco, leitura mobile e fallback sem JavaScript. Posicionamento absoluto foi descartado por aumentar risco de sobreposicao e overflow.
+
+### Reutilizar motion de transformacao e clip ja existente
+
+As novas regioes conservam `data-reveal` e grupos existentes. Nenhum texto passa a depender de opacidade; `prefers-reduced-motion` continua exibindo o estado final imediatamente.
+
+## Risks / Trade-offs
+
+- [Ritmo visual pode parecer irregular com poucos cases] -> regras e metadados mantem uma leitura coerente mesmo com um unico item.
+- [Classes responsivas podem afetar o fluxo em mobile] -> DOM linear e classes de uma coluna continuam sendo a base abaixo de `md`.
+- [Mudar CSS pode gerar diferencas de ambiente] -> validar markup, acessibilidade funcional e build; snapshots permanecem fora do escopo.
+
+## Migration Plan
+
+Nao ha migracao de dados. A mudanca e retrocompativel: sem imagens, os fallbacks tonais existentes continuam ativos; com imagens, o mesmo `srcset` responsivo e usado. Reverter o commit restaura somente apresentacao.
+
+## Open Questions
+
+Nenhuma. Fotografia autorizada de producao permanece uma dependencia de conteudo futura.

openspec/changes/archive/2026-08-11-recompose-public-editorial/proposal.md

@@ -0,0 +1,30 @@
+## Why
+
+O site público já possui os conteúdos, fluxos e a base Heritage Editorial, mas algumas páginas ainda repetem grades regulares que enfraquecem a cadência da referência aprovada. A recomposição consolida uma leitura editorial contínua sem alterar dados CMS, SEO ou a jornada de briefing.
+
+## What Changes
+
+- Recompõe as superfícies públicas narrativas com campos tonais, regras finas, assimetria desktop e sequência vertical legível em mobile.
+- Organiza a home nos capítulos editoriais existentes, com portfólio em campo oliva e recortes de imagens em proporções alternadas.
+- Reestiliza listagens e detalhe de portfólio para que imagens e blocos de leitura não dependam de uma grade de cartões repetida.
+- Mantém contato, privacidade e erros em tratamento sóbrio; preserva menu móvel, foco, formulário, SEO, motion progressivo e conteúdo do CMS.
+- Documenta que heros fotográficos e sua administração já estão presentes na base atual, sem acoplar mídia editorial à imagem Open Graph.
+
+## Capabilities
+
+### New Capabilities
+
+- Nenhuma.
+
+### Modified Capabilities
+
+- `public-site-pages`: composição e cadência visual das rotas públicas passam a exigir ritmos editoriais assimétricos.
+- `content-media`: a apresentação de mídia de portfólio passa a suportar proporções editoriais alternadas sem mudar armazenamento ou variantes.
+
+## Impact
+
+Afeta Blade e estilos do site público, testes de estrutura/renderização e a documentação OpenSpec. Não altera rotas, controladores, dados de conteúdo, dependências ou contratos de SEO.
+
+## Non-goals
+
+Não introduz itens excluídos por SPEC.md §4.2, novos canais, prova comercial, conteúdo de produção, imagens externas, dependências de animação, snapshots visuais ou mudanças no Filament.

openspec/changes/archive/2026-08-11-recompose-public-editorial/specs/content-media/spec.md

@@ -0,0 +1,16 @@
+## MODIFIED Requirements
+
+### Requirement: Editorial image treatment remains self-hosted and deterministic
+Public photography SHALL continue to use validated self-hosted uploads and responsive variants. Editorial layouts MUST use CSS-only tonal treatment and alternating aspect ratios for portfolio media while retaining document order and the image component's `srcset`, `sizes`, dimensions and loading behavior. The system MUST NOT introduce external image CDN dependencies that compromise browser-test reliability.
+
+#### Scenario: Public pages do not depend on external stock hosts
+
+- **WHEN** the visual or browser suite loads covered public routes
+- **THEN** content images MUST resolve from the application media disk or static fixtures
+- **AND** MUST NOT require network access to third-party stock hosts
+
+#### Scenario: Editorial portfolio media retains responsive delivery
+
+- **WHEN** a portfolio listing or gallery applies an editorial image proportion
+- **THEN** the rendered image MUST still expose the responsive media component markup
+- **AND** image order and lazy-loading behavior MUST remain intact

openspec/changes/archive/2026-08-11-recompose-public-editorial/specs/public-site-pages/spec.md

@@ -0,0 +1,69 @@
+## MODIFIED Requirements
+
+### Requirement: Home renders the editorial structure from CMS content
+The home page SHALL render, in order: header/navigation, hero, manifesto, featured services summary, featured portfolio selection, working method (four steps), testimonials, Amare positioning/profile, final contact CTA, and footer with contact, social links and legal links (WEB-01). Hero copy, brand name, manifesto, method and principles MUST come from `site_settings` (with editorial defaults when optional fields are empty); services, cases and testimonials MUST come from published records. The home MUST follow the Heritage Editorial composition: asymmetric spreads and tonal fields on desktop, with portfolio images in alternating editorial proportions, and a linear complete sequence on mobile rather than rounded card grids.
+
+#### Scenario: Published content is displayed in configured order
+
+- **GIVEN** published services, cases and testimonials exist
+- **WHEN** a visitor loads the home
+- **THEN** the published content MUST be displayed following the `sort_order` and featured flags
+- **AND** the hero MUST show the values stored in `site_settings`
+- **AND** the manifesto, method and positioning sections MUST be present
+- **AND** the portfolio section MUST use an olive tonal field with editorial image proportions
+
+#### Scenario: CTA leads to the contact placeholder page
+
+- **WHEN** a visitor activates the primary or final CTA on the home
+- **THEN** the visitor MUST be taken to the `contact` route
+- **AND** no lead record MUST be created
+
+#### Scenario: Empty catalog sections are omitted
+
+- **GIVEN** no published services, cases or testimonials
+- **WHEN** a visitor loads the home
+- **THEN** the response MUST be 200
+- **AND** the services, portfolio and testimonials sections MUST be omitted instead of rendering empty containers
+- **AND** hero, manifesto, method, positioning and final CTA MUST still render
+
+#### Scenario: Home has no console errors
+
+- **WHEN** the home is loaded in a real browser at desktop and mobile viewports
+- **THEN** the browser console MUST contain no JavaScript errors
+
+### Requirement: Listing and detail pages exist for catalog content
+The system SHALL render a services listing (WEB-02) and a portfolio listing plus case detail (WEB-03) using the Heritage Editorial visual language. The case detail MUST present summary, event type, optional city/venue/date, challenge, solution, optional result, cover image and the ordered gallery. Portfolio listings and galleries MUST use alternating editorial image proportions on desktop while retaining DOM order and a single-column readable sequence on mobile.
+
+#### Scenario: Services listing shows published services
+
+- **WHEN** a visitor loads `/servicos`
+- **THEN** every published service MUST be listed with title and summary in `sort_order`
+- **AND** the listing MUST use the public editorial layout (not an unrelated visual system)
+
+#### Scenario: Gallery respects stored order
+
+- **GIVEN** a published case with multiple gallery images
+- **WHEN** a visitor loads the case detail
+- **THEN** the images MUST be rendered ordered by `sort_order`
+- **AND** desktop presentation MUST alternate editorial image proportions without changing that order
+
+#### Scenario: Listings paginate open-ended growth
+
+- **WHEN** the number of published cases exceeds the page size
+- **THEN** `/portfolio` MUST paginate instead of rendering all records
+
+### Requirement: Institutional and error pages have brand identity
+The system SHALL provide the Sobre and Política de privacidade pages and branded error pages (WEB-07) using the Heritage Editorial public layout, including the brand mark when available. Contact, privacy and error surfaces MUST remain sober tonal layouts without decorative photography. The 404 page MUST use the public layout, and the 500 page MUST NOT expose stack traces or internal details when `APP_DEBUG` is false.
+
+#### Scenario: Unknown URL renders branded 404
+
+- **WHEN** a visitor requests a non-existent public URL
+- **THEN** the response status MUST be 404
+- **AND** the page MUST use the public layout and offer navigation back to the home
+
+#### Scenario: Server error hides internals in production
+
+- **GIVEN** `APP_DEBUG` is false
+- **WHEN** an unhandled exception occurs on a public route
+- **THEN** the response MUST be a generic branded error page
+- **AND** MUST NOT contain a stack trace, file path, or environment variable

openspec/changes/archive/2026-08-11-recompose-public-editorial/tasks.md

@@ -0,0 +1,10 @@
+## 1. Editorial composition
+
+- [x] 1.1 Add regression coverage for alternating public portfolio composition and sober functional surfaces.
+- [x] 1.2 Recompose home portfolio, portfolio listing and case gallery with responsive editorial proportions while preserving order and responsive media delivery.
+- [x] 1.3 Refine public content-page rhythm with tonal fields and desktop offsets without changing routes, CMS content or briefing behavior.
+
+## 2. Verification
+
+- [x] 2.1 Run focused feature and browser checks for public routes, motion, accessibility and navigation.
+- [x] 2.2 Run formatting, static analysis, frontend build and strict OpenSpec validation without updating snapshots.

openspec/changes/complete-foundation-parity/tasks.md

@@ -36,8 +36,8 @@
 
 ## 6. Phase 0 exit evidence
 
-- [ ] 6.1 Perform first successful staging deploy of a `main` SHA and capture evidence (workflow URL, smoke output)
+- [x] 6.1 Perform first successful staging deploy of a `main` SHA and capture evidence (workflow URL, smoke output) — run 31395107465 deployed `7e68c0e` successfully; smoke recorded `/up`, `/` and `/admin/login` returning HTTP 200.
 - [ ] 6.2 Verify rollback to previous SHA works once on staging
-- [x] 6.3 Update `SPEC.md` §18 Fase 0 checkboxes only for items with evidence; note remaining deferred items if any — flipped L2338 (FrankenPHP/Compose) and the auth/npm-audit/coverage bullets to `[x]`; left the staging hello-world bullet and the phase exit-criterion line unchecked (Dokploy deploy still failing, out of scope here)
+- [x] 6.3 Update `SPEC.md` §18 Fase 0 checkboxes only for items with evidence; note remaining deferred items if any — local runtime/auth/audit/coverage evidence was recorded by PR #39, and the staging exit criterion was subsequently marked complete from successful run 31395107465.
-- [ ] 6.4 Run full `composer quality` and confirm all five CI jobs + staging deploy path green
+- [x] 6.4 Run full `composer quality` and confirm all five CI jobs + staging deploy path green — local quality evidence is recorded in task 2.4; PR #39 passed `static`, `unit`, `feature`, `browser` and `container`, then run 31395107465 deployed that exact merge SHA and passed all three smoke endpoints.
-- [ ] 6.5 Report in SPEC §24 format; archive this change only after remaining parity tasks (1–3) also complete
+- [ ] 6.5 Report in SPEC §24 format; archive this change only after remaining parity tasks are complete — blocked by tasks 3.4 and 6.2, tracked separately in MAN-125.

openspec/changes/enhance-public-motion/specs/visual-regression/spec.md

@@ -1,26 +0,0 @@
-## MODIFIED Requirements
-
-### Requirement: Public screens have desktop and mobile visual baselines
-
-The system SHALL keep versioned screenshot baselines for the public screens available in this phase (SPEC §13.5): Home, Serviços, Portfólio, Detalhe do portfólio, Sobre, Contato, Privacidade and branded 404, at 1440×1000 desktop and 390×844 mobile, under the Heritage Editorial identity. A rendering change that alters those screens MUST fail the browser suite until the diff is reviewed and baselines are explicitly updated.
-
-#### Scenario: Unintended visual change fails the suite
-
-- **GIVEN** approved baselines exist
-- **WHEN** a code change alters the rendering of a covered screen
-- **THEN** the visual assertion MUST fail and report the diff
-
-#### Scenario: Both viewports are covered
-
-- **WHEN** the visual suite runs
-- **THEN** each covered screen MUST be asserted at 1440×1000 and 390×844
-
-#### Scenario: Heritage Editorial identity is captured
-
-- **WHEN** approved baselines for the home are reviewed after this change
-- **THEN** they MUST reflect EB Garamond typography, olive/paper palette and sharp-edged editorial layout rather than the previous gold/rounded placeholder look
-
-#### Scenario: Motion does not destabilize new baselines
-
-- **WHEN** Sobre, Contato, Privacidade, or 404 is captured
-- **THEN** the browser MUST use the final reduced-motion state before asserting the screenshot

openspec/changes/hero-editorial-spread/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-08-11

openspec/changes/hero-editorial-spread/design.md

@@ -0,0 +1,48 @@
+## Context
+
+As imagens de abertura por rota, `ResponsiveImage`, texto alternativo obrigatório e fallback tonal já existem. O componente público atual, porém, põe o texto sobre a fotografia e a home mantém duas colunas iguais. A referência aprovada pede uma abertura editorial legível, reutilizável e linear sem JavaScript.
+
+## Goals / Non-Goals
+
+**Goals:**
+
+- Reunir as cinco aberturas narrativas em um único componente Blade de spread 5/7.
+- Limitar a coluna de leitura a 470 px e manter títulos com quebra normal, sem clipping ou overflow.
+- Preservar a ordem DOM texto → mídia em mobile, mídia responsiva, foco, motion progressivo e fallback tonal.
+
+**Non-Goals:**
+
+- Alterar campos CMS, uploads, dados, rotas, cópia, SEO/Open Graph, contato, privacidade, erros ou dependências.
+- Criar ou atualizar snapshots, introduzir imagens externas ou transformar a rota de protótipo em funcionalidade de produção.
+
+## Decisions
+
+### Um componente compartilhado recebe todo o conteúdo de abertura
+
+`x-public.photo-hero` passa a renderizar texto, slot opcional e mídia tanto para as páginas institucionais quanto para a home. A home delega o seu conteúdo ao componente para impedir que os contratos de proporção, fallback e carregamento se separem. Duplicar uma segunda implementação da home foi descartado por já ter produzido divergência 50/50.
+
+### Grade CSS 5/7 acima de `lg`; fluxo normal abaixo dela
+
+No desktop, uma grade de doze colunas entrega 5/12 ao campo de texto e 7/12 à mídia. No mobile e tablet, a ordem do DOM produz texto seguido pela imagem de proporção 4/5. Posicionamento absoluto e painel sobre a foto foram descartados porque reduzem a largura de leitura previsível e dificultam a contenção do texto.
+
+### Mídia de hero continua prioritária e dimensionada pela área real
+
+A única imagem de abertura mantém `loading=eager`, `fetchpriority=high`, `object-cover` e o componente responsivo existente. Seu `sizes` informa `100vw` abaixo de `lg` e aproximadamente `58vw` acima dele, em vez dos antigos `50vw`/`100vw` indiscriminados. O fallback não emite imagem quando o campo está vazio.
+
+### Motion preserva o conteúdo legível desde o HTML
+
+Os atributos existentes de `page-open` e beats de mídia/título/CTA permanecem. Nenhum texto fica escondido por opacidade; movimento reduzido e ausência de JavaScript exibem o estado final.
+
+## Risks / Trade-offs
+
+- [Uma imagem de origem estreita pode recortar conteúdo importante em 7/12] → `object-cover` preserva o contrato atual; curadoria/crop da mídia continua sendo responsabilidade editorial.
+- [Conteúdo de título excepcionalmente longo pode pressionar a coluna] → limite de leitura, quebra normal e testes de ausência de overflow evitam palavras cortadas.
+- [Breakpoint pode atualizar depois de resize em browser test] → os testes aguardam dois frames de animação antes de medir a mídia.
+
+## Migration Plan
+
+Não há migração de dados. O deploy troca apenas markup e classes; o rollback do commit restaura a abertura anterior. Rotas sem imagem continuam no fallback tonal já previsto.
+
+## Open Questions
+
+Nenhuma. Fotografias autorizadas de produção continuam uma dependência de conteúdo, não desta mudança.

openspec/changes/hero-editorial-spread/proposal.md

@@ -0,0 +1,25 @@
+## Why
+
+As aberturas fotográficas já contam com mídia própria, mas a composição atual alterna uma imagem de fundo ou uma divisão 50/50 que achata a leitura editorial. Um spread consistente de texto 5/12 e imagem 7/12 reforça a hierarquia de WEB-01, WEB-02, WEB-03 e WEB-07 sem inventar conteúdo nem ampliar o CMS.
+
+## What Changes
+
+- Define um componente único de abertura fotográfica em spread: conteúdo à esquerda em 5/12, fotografia à direita em 7/12, coluna de leitura limitada e imagem com recorte editorial.
+- Aplica o mesmo contrato às aberturas narrativas da home, serviços, portfólio, detalhe de case e Sobre; telas menores linearizam texto antes da mídia.
+- Mantém os campos de mídia existentes, carregamento prioritário apenas do hero, alternativa tonal sem imagem e a separação entre imagens editoriais e Open Graph.
+- Mantém contato, privacidade e páginas de erro como superfícies tonais sóbrias.
+
+## Capabilities
+
+### New Capabilities
+
+- Nenhuma.
+
+### Modified Capabilities
+
+- `public-site-pages`: as cinco aberturas narrativas passam a exigir o spread editorial 5/7 em desktop e uma sequência texto-para-mídia em telas menores.
+- `content-media`: imagens de abertura passam a declarar tamanhos compatíveis com 100% da largura em mobile e 7/12 do viewport em desktop.
+
+## Impact
+
+Afeta os componentes Blade de hero público e da home, a documentação de design, os testes de renderização e browser das rotas públicas e as delta specs. Não altera rotas de produção, controladores, CMS, uploads, SEO/OG, dependências ou os itens fora do MVP em SPEC.md §4.2.

openspec/changes/hero-editorial-spread/specs/content-media/spec.md

@@ -0,0 +1,14 @@
+## ADDED Requirements
+
+### Requirement: Editorial hero media declares its responsive spread width
+Configured narrative hero media SHALL load eagerly with high priority and declare responsive sizes matching the rendered spread: full viewport width below the desktop breakpoint and seven twelfths of the viewport at desktop. Each configured hero image MUST retain meaningful alternative text; a missing image MUST use the tonal fallback without emitting media markup (SPEC §6.4, §6.6).
+
+#### Scenario: A configured hero reports its responsive width
+- **WHEN** a narrative route renders configured hero media
+- **THEN** the image MUST declare `100vw` for smaller viewports and approximately `58vw` for the desktop spread
+- **AND** it MUST use eager loading and high fetch priority
+
+#### Scenario: An unconfigured hero emits no media
+- **WHEN** a narrative route has no hero image path
+- **THEN** the opening MUST not render an image element
+- **AND** it MUST retain its readable tonal content

openspec/changes/hero-editorial-spread/specs/public-site-pages/spec.md

@@ -0,0 +1,23 @@
+## ADDED Requirements
+
+### Requirement: Narrative openings use a readable editorial spread
+The home, services, portfolio listing, portfolio detail, and About routes SHALL render configured hero media as a Heritage Editorial spread: a 5/12 text field and 7/12 media field on desktop, with a text-first linear sequence on smaller viewports. The text field MUST limit reading width to 470 px, preserve normal word wrapping, and avoid horizontal overflow or clipped text. Contact, privacy, and error surfaces MUST remain sober tonal layouts (WEB-01, WEB-02, WEB-03, WEB-07).
+
+#### Scenario: A configured narrative opening renders the desktop spread
+- **WHEN** a visitor loads a narrative route with its configured hero image at a desktop viewport
+- **THEN** its text field MUST occupy five of twelve grid columns and its media field seven of twelve grid columns
+- **AND** the media MUST use an editorial `object-cover` crop
+
+#### Scenario: A configured narrative opening stacks without losing reading content
+- **WHEN** a visitor loads a narrative route with its configured hero image below the desktop breakpoint
+- **THEN** the text content MUST precede the media in DOM and visual order
+- **AND** the route MUST not horizontally overflow or clip text
+
+#### Scenario: A narrative opening has no configured image
+- **WHEN** a visitor loads a narrative route without configured hero media
+- **THEN** the route MUST render its intentional tonal fallback without an empty image request
+
+#### Scenario: Functional routes remain sober
+- **WHEN** a visitor loads contact or privacy
+- **THEN** the route MUST use its sober tonal opening
+- **AND** it MUST not render the narrative photo spread

openspec/changes/hero-editorial-spread/tasks.md

@@ -0,0 +1,14 @@
+## 1. Editorial contract
+
+- [x] 1.1 Record the approved 5/7 spread rule in the Heritage Editorial design guidance.
+- [x] 1.2 Add failing feature and browser coverage for the 5/7 desktop grid, 470 px reading column, responsive image sizes, text-first mobile order, and contained text.
+
+## 2. Shared opening implementation
+
+- [x] 2.1 Rebuild the public photo hero as the single responsive spread component, retaining fallback, accessible media, motion attributes, optional content, and no-image behavior.
+- [x] 2.2 Delegate the home opening to the shared component while retaining its CTAs, note, chapter marker, and motion hooks.
+
+## 3. Verification
+
+- [x] 3.1 Run focused feature and browser/accessibility/motion checks without creating or updating screenshots.
+- [x] 3.2 Run Pint, PHPStan, frontend build, and strict OpenSpec validation.

openspec/changes/restructure-home-weddings-corporate/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-08-11

openspec/changes/restructure-home-weddings-corporate/design.md

@@ -0,0 +1,58 @@
+## Context
+
+The public site currently sends every commercial CTA to `/contato`, where the detailed event briefing lives. Its home chapters reflect the original editorial sequence, while the CMS only has generic `Service` records. Production seed gating already distinguishes environmental content but the public portfolio needs an explicit empty-acervo state so no demonstrative case can be mistaken for proof.
+
+## Goals / Non-Goals
+
+**Goals:**
+
+- Keep the public surface server-rendered Blade with progressive vanilla JS and a single Heritage Editorial visual language.
+- Make wedding modalities typed, publishable, ordered CMS content; derive their WhatsApp CTA server-side with an explicit briefing fallback.
+- Split prospect and partner submissions at route, request, controller, mail and success-state boundaries.
+- Keep public data minimised: partner submissions are mailed, never persisted.
+
+**Non-Goals:**
+
+- No WhatsApp API/integration, CRM Lead creation, partner directory, Corporate service inventory, Corporate case, invented evidence or page builder.
+- No production migration of fixture cases into real proof; the authorized client content remains an operational prerequisite.
+
+## Decisions
+
+### Typed `WeddingPackage` content instead of a JSON setting
+
+`wedding_packages` has a dedicated model, migration, factory, policy, Filament resource and public query. This matches the existing publication/order model for Services and keeps content validation, ordering and authorization visible. A JSON array in `site_settings` would be faster initially but would weaken publication control and future editing.
+
+### WhatsApp is a deeplink, not an integration
+
+The setting stores digits-normalized `whatsapp_number`; a small value object builds `https://wa.me/<digits>?text=<encoded contextual message>`. If the setting is absent or invalid, the same CTA points to `/briefing?servico_interesse=<package>` so conversion still works. This offers the authorized official channel without violating SPEC §4.2's prohibition on an official integration.
+
+### Separate partner boundary, not a mode on briefing
+
+`PartnerInquiryRequest`, `PartnerInquiryController` and `PartnerInquiry` mailable have their own payload, honeypot key, throttle and session duplicate hash. It prevents event fields, marketing origin and confirmations from crossing into the partnership flow. A single controller with a discriminated input was rejected because it increases the chance of accidental routing or data disclosure.
+
+### Honest public availability states
+
+The home consumes `GetHomeContent`, which returns only actual published cases in production. The portfolio chapter itself remains present and shows an acervo-em-preparação note on empty data. Non-production visual fixtures continue to seed only for development/staging. Corporate remains copy plus a briefing CTA, deliberately without data-driven claims, media or a service list.
+
+### Navigation links use canonical home fragments
+
+Header/footer link to `/#amare`, `/#casamentos`, `/#corporate`, `/#portfolio` and `/#depoimentos` from other routes, and native fragments on the home. This preserves deep links and no-JS behavior; CSS scroll margin compensates for the sticky header.
+
+## Risks / Trade-offs
+
+- [Official WhatsApp number is not configured at deploy] → every package CTA has a deterministic briefing fallback and settings label calls out the operational requirement.
+- [Client proof is still unavailable] → production renders no fixture cases, a visible acervo note and no Corporate cases.
+- [New contact route changes incoming links] → `/contato` remains available for partners and header/footer continue to expose it; event CTA links move deliberately to `/briefing`.
+- [Detailed forms duplicate markup] → shared field styles and narrow controllers are preferred over generic, condition-heavy form components.
+
+## Migration Plan
+
+1. Deploy the additive table/column migrations and code together.
+2. Run the content seeder to install official wedding modalities; set the official WhatsApp number in Filament before promoting CTAs.
+3. In production, leave portfolio cases unpublished until real authorized material is loaded; verify the empty-acervo state.
+4. Rollback is code-safe because routes remain additive and the legacy setting data is untouched; if necessary, unset the new WhatsApp column and retain the package rows without public publication.
+
+## Open Questions
+
+- Corporate institutional copy and authorized proof (MAN-98/MAN-99) remain client dependencies; no placeholder claims will be added.
+- The official WhatsApp number must be supplied before the campaign links are promoted.

openspec/changes/restructure-home-weddings-corporate/proposal.md

@@ -0,0 +1,31 @@
+## Why
+
+A home atual apresenta os conteúdos do CMS, mas não conduz com clareza as duas frentes da Amare nem separa o pedido de proposta da relação com fornecedores. A estrutura de lançamento precisa tornar Casamentos e Corporate compreensíveis sem inventar prova, preservar o acervo real como requisito de publicação e abrir um canal mínimo, privado e específico para parcerias.
+
+## What Changes
+
+- Reorganizar a home em capítulos editoriais ancoráveis: apresentação, Amare, vertentes, Casamentos, Corporate, acervo, depoimentos e fechamento.
+- Adicionar modalidades de casamento publicáveis e ordenáveis no CMS, com conteúdo inicial oficial para Essenza, Conduzione e Grand Jour.
+- Adicionar número oficial de WhatsApp às configurações e tornar as CTAs das modalidades contextuais, com fallback para o briefing.
+- Mover o formulário de pedido de proposta para `/briefing`; transformar `/contato` em uma jornada independente para fornecedores e parcerias.
+- Enviar a consulta de parceiro por e-mail próprio, sem criar Lead ou persistir dados; manter CSRF, honeypot, rate limit, validação e aviso de privacidade proporcional à finalidade.
+- Manter Corporate como apresentação institucional e CTA até haver copy, fotos e cases autorizados; em produção, não publicar fixtures de portfólio e informar que o acervo está em preparação.
+
+## Capabilities
+
+### New Capabilities
+
+- `wedding-packages`: modalidades de casamento gerenciadas no CMS e CTAs contextuais de WhatsApp/briefing.
+- `partner-inquiries`: formulário público mínimo, privado e não persistente para fornecedores e parcerias.
+
+### Modified Capabilities
+
+- `public-site-pages`: nova estrutura editorial da home, âncoras e separação entre briefing e contato de parceiros.
+- `service-catalog`: aprofundamento de serviços passa a apresentar as modalidades de casamento publicadas.
+- `site-settings`: configurações tipadas passam a incluir o número oficial de WhatsApp.
+- `transactional-email`: e-mail operacional separado para consultas de parceiros.
+- `content-media`: fixtures de casos ficam limitadas a desenvolvimento e staging; produção só mostra acervo real publicado.
+
+## Impact
+
+Afeta rotas, controllers, requests, mailables, modelos/migrations/seeders, Filament, consultas de marketing, componentes Blade, navegação, estilos e testes feature/browser. A mudança atende WEB-01, WEB-02, WEB-03, WEB-05, WEB-06 e WEB-07, sem introduzir integração oficial com WhatsApp, CRM, persistência de leads, marketplace ou outros itens fora do MVP (SPEC.md §4.2).

openspec/changes/restructure-home-weddings-corporate/specs/content-media/spec.md

@@ -0,0 +1,8 @@
+## ADDED Requirements
+
+### Requirement: Production never promotes visual fixture cases as Amare proof
+The content seeder SHALL restrict visual fixture portfolio cases to non-production environments. Production public output SHALL only render cases that were explicitly loaded and published as authorized content.
+
+#### Scenario: Production seed does not create fixture cases
+- **WHEN** the content seeder runs with the production environment
+- **THEN** no fixture portfolio case or fixture portfolio image is published

openspec/changes/restructure-home-weddings-corporate/specs/partner-inquiries/spec.md

@@ -0,0 +1,16 @@
+## ADDED Requirements
+
+### Requirement: Partners have a separate, non-persistent contact journey
+The system SHALL expose `/contato` as a supplier and partnership form. It MUST collect name, optional professional/company name, e-mail, service/activity, coverage area, message, optional portfolio/social link and optional telephone. It SHALL send a dedicated internal e-mail and MUST NOT persist a Lead or partner record.
+
+#### Scenario: Valid partner inquiry is delivered separately
+- **WHEN** a visitor submits valid partner data on `/contato`
+- **THEN** the configured internal recipient receives the dedicated partner inquiry e-mail
+- **AND** no briefing confirmation or Lead is created
+
+### Requirement: Partner inquiry is protected and transparent
+The partner form SHALL enforce CSRF, server-side limits, honeypot, rate limiting and duplicate-click protection. It MUST show a purpose-specific privacy notice linking to the privacy policy.
+
+#### Scenario: Honeypot blocks automated partner form submissions
+- **WHEN** the partner honeypot is filled
+- **THEN** the system reports generic success without sending an e-mail

openspec/changes/restructure-home-weddings-corporate/specs/public-site-pages/spec.md

@@ -0,0 +1,38 @@
+## ADDED Requirements
+
+### Requirement: Home presents the weddings and corporate editorial journey
+The home SHALL expose anchored chapters for presentation, Amare, service directions, weddings, Corporate, portfolio/acervo, testimonials and final contact paths. It MUST retain the photographic hero, tonal fields, fine rules, EB Garamond and progressive/reduced-motion behavior. Corporate SHALL present only institutional copy and a briefing CTA until authorized copy and proof exist.
+
+#### Scenario: Canonical anchor journey is reachable
+- **WHEN** a visitor loads the home or follows a `/#chapter` link from another public page
+- **THEN** the relevant chapter exists with a stable id and is reachable without JavaScript
+
+#### Scenario: Corporate does not imply unauthorized proof
+- **WHEN** a visitor loads the Corporate chapter before client proof is published
+- **THEN** no Corporate service list, image, metric or case is rendered
+
+### Requirement: Production portfolio remains truthful when no cases are published
+The public portfolio chapter SHALL render a visible acervo-em-preparação note when no real published cases are available. Production seeders MUST NOT publish development fixture cases.
+
+#### Scenario: Empty production acervo is explicit
+- **GIVEN** production has no published portfolio cases
+- **WHEN** a visitor loads the home
+- **THEN** the portfolio chapter displays the acervo preparation note and no case card
+
+## MODIFIED Requirements
+
+### Requirement: Contact page presents contact data as briefing placeholder
+
+The `contact` route SHALL render the partner and supplier inquiry page using `site_settings` contact data. The detailed event proposal form SHALL be served by the `briefing` route at `/briefing`; public proposal CTAs MUST target that route. Neither public form MUST create a Lead in the launch scope.
+
+#### Scenario: Contact page shows partner journey
+
+- **WHEN** a visitor loads `/contato`
+- **THEN** partner-specific copy, fields and privacy notice MUST be displayed
+- **AND** the detailed event briefing MUST NOT be rendered
+
+#### Scenario: Briefing route remains reachable for prospects
+
+- **WHEN** a visitor loads `/briefing`
+- **THEN** the detailed event proposal form MUST be displayed
+- **AND** no Lead record MUST be created

openspec/changes/restructure-home-weddings-corporate/specs/service-catalog/spec.md

@@ -0,0 +1,9 @@
+## ADDED Requirements
+
+### Requirement: Services explain published wedding modalities
+The public services experience SHALL present published wedding modalities as the available Casamentos scope, including level, summary and ordered scope items. It MUST not treat unpublished modalities as public services.
+
+#### Scenario: Draft modality remains private
+- **GIVEN** a wedding modality with `published_at` null
+- **WHEN** a visitor loads `/servicos`
+- **THEN** that modality MUST NOT be rendered

openspec/changes/restructure-home-weddings-corporate/specs/site-settings/spec.md

@@ -0,0 +1,8 @@
+## ADDED Requirements
+
+### Requirement: Official WhatsApp number is a typed site setting
+The typed site settings singleton SHALL include an optional `whatsapp_number`. The admin form MUST validate and label it as the official number used by public modality CTAs; it MUST NOT create an external WhatsApp integration.
+
+#### Scenario: Admin stores official WhatsApp number
+- **WHEN** an admin saves a valid number in site settings
+- **THEN** public wedding modality CTAs can derive the contextual deeplink

openspec/changes/restructure-home-weddings-corporate/specs/transactional-email/spec.md

@@ -0,0 +1,9 @@
+## ADDED Requirements
+
+### Requirement: Partner inquiries use a dedicated transactional message
+The system SHALL send supplier and partnership submissions in a dedicated `PartnerInquiry` mailable to the configured internal site recipient. It MUST NOT send the visitor briefing confirmation for this form.
+
+#### Scenario: Partner email does not cross into briefing mail
+- **WHEN** a valid partner inquiry is submitted
+- **THEN** the recipient receives the partner field set
+- **AND** the visitor does not receive `ContactBriefingConfirmation`

openspec/changes/restructure-home-weddings-corporate/specs/wedding-packages/spec.md

@@ -0,0 +1,26 @@
+## ADDED Requirements
+
+### Requirement: Wedding modalities are managed as publishable ordered content
+The system SHALL let an admin manage `WeddingPackage` records with name, level, summary, ordered scope items, CTA label, sort order and `published_at`. Only published records SHALL appear in public wedding sections, in ascending `sort_order`.
+
+#### Scenario: Published modalities follow CMS order
+- **GIVEN** published and draft wedding modalities with different sort orders
+- **WHEN** a visitor loads the home or services page
+- **THEN** only published modalities appear in ascending `sort_order`
+
+#### Scenario: Official initial modalities are available
+- **WHEN** the content seeder runs
+- **THEN** Essenza, Conduzione and Grand Jour are created as the official initial modalities
+
+### Requirement: Wedding modality CTA has a contextual channel and conversion fallback
+The system SHALL build a WhatsApp deeplink containing the selected modality when `whatsapp_number` is valid. When it is missing or invalid, the CTA SHALL point to `/briefing` with the modality prefilled as `servico_interesse`.
+
+#### Scenario: Valid WhatsApp setting creates contextual link
+- **GIVEN** a valid official WhatsApp number
+- **WHEN** a visitor activates a wedding modality CTA
+- **THEN** the link targets `wa.me` with a URL-encoded message naming that modality
+
+#### Scenario: Missing WhatsApp setting preserves briefing conversion
+- **GIVEN** no valid official WhatsApp number
+- **WHEN** a visitor activates a wedding modality CTA
+- **THEN** the visitor reaches `/briefing` with `servico_interesse` prefilled

openspec/changes/restructure-home-weddings-corporate/tasks.md

@@ -0,0 +1,25 @@
+## 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.

openspec/specs/container-runtime/spec.md

@@ -57,3 +57,31 @@ The system SHALL define a container healthcheck that verifies application availa
 - **WHEN** the application inside the container fails to respond healthy on `/up`
 - **THEN** the container healthcheck MUST report unhealthy status
 
+### Requirement: Local Compose runs FrankenPHP application alongside PostgreSQL
+
+The local Docker Compose stack SHALL include a FrankenPHP application service built from the project Dockerfile, dependent on a healthy PostgreSQL service, exposing the application on port 8000 (or documented equivalent). FrankenPHP MUST run in regular mode (ADR-006).
+
+#### Scenario: Developer starts full local stack
+
+- **WHEN** a developer runs `docker compose up -d` with the application service enabled
+- **THEN** PostgreSQL and the FrankenPHP app containers MUST become healthy
+- **AND** `GET /up` on the app port MUST return HTTP 200
+
+#### Scenario: App waits for database readiness
+
+- **WHEN** the application service starts
+- **THEN** it MUST depend on the PostgreSQL healthcheck succeeding before becoming ready
+
+### Requirement: Runtime PHP version is canonically 8.4
+
+Docker, CI, and project documentation MUST treat PHP 8.4 as the canonical runtime for this MVP. Statements that require PHP 8.5+ MUST NOT remain in project docs while the runtime image uses 8.4.
+
+#### Scenario: Dockerfile pins PHP 8.4
+
+- **WHEN** the production/runtime image is built
+- **THEN** the FrankenPHP base image MUST use PHP 8.4
+
+#### Scenario: Documentation matches the runtime
+
+- **WHEN** a contributor reads the README requirements
+- **THEN** the documented PHP version MUST be 8.4 (compatible with Composer `^8.3`)

openspec/specs/content-media/spec.md

@@ -126,11 +126,16 @@ The system SHALL provide optimized Amare brand logo assets derived from the offi
 - **THEN** the uploaded logo MUST be used instead of the static fallback
 
 ### Requirement: Editorial image treatment remains self-hosted and deterministic
-
+Public photography SHALL continue to use validated self-hosted uploads and responsive variants. Editorial layouts MUST use CSS-only tonal treatment and alternating aspect ratios for portfolio media while retaining document order and the image component's `srcset`, `sizes`, dimensions and loading behavior. The system MUST NOT introduce external image CDN dependencies that compromise browser-test reliability.
-Public photography SHALL continue to use validated self-hosted uploads and responsive variants. Decorative saturation/contrast treatment for editorial mood MUST be applied via CSS on self-hosted images and MUST NOT introduce external image CDN dependencies that break deterministic visual tests.
 
 #### Scenario: Public pages do not depend on external stock hosts
 
 - **WHEN** the visual or browser suite loads covered public routes
 - **THEN** content images MUST resolve from the application media disk or static fixtures
 - **AND** MUST NOT require network access to third-party stock hosts
+
+#### Scenario: Editorial portfolio media retains responsive delivery
+
+- **WHEN** a portfolio listing or gallery applies an editorial image proportion
+- **THEN** the rendered image MUST still expose the responsive media component markup
+- **AND** image order and lazy-loading behavior MUST remain intact

openspec/specs/design-tokens/spec.md

@@ -53,3 +53,11 @@ The public site SHALL express hierarchy through tonal paper fields, 1px botanica
 - **THEN** they MUST NOT depend on `--amare-shadow-*` card elevation for hierarchy
 - **AND** separation MUST come from borders, tonal backgrounds, or whitespace
 
+### Requirement: Editorial motion tokens are centralized
+
+The system SHALL define shared public motion tokens for an approximately 500 ms entrance, short interaction feedback, exponential ease-out, 90 ms stagger capped at 270 ms, 12 px vertical distance, and 24 px desktop / 16 px mobile lateral distance. Public motion CSS MUST consume these tokens instead of duplicating arbitrary values.
+
+#### Scenario: Motion runtime uses shared values
+- **WHEN** page openings, reveals, or interaction feedback are styled
+- **THEN** duration, easing, stagger, and distance MUST be derived from centralized tokens
+

openspec/specs/health-check/spec.md

@@ -26,3 +26,17 @@ The system SHALL return a failure status when the application cannot initialize
 - **WHEN** the application fails to boot due to misconfiguration or missing dependencies
 - **THEN** the health endpoint MUST NOT return HTTP 200
 
+### Requirement: Staging health and smoke use the public /up endpoint
+
+Staging healthchecks and post-deploy smoke MUST call `GET /up` without authentication and MUST treat a non-200 response as deployment failure (SPEC §15.5, §16.2). The health response MUST NOT expose secrets.
+
+#### Scenario: Staging healthcheck probes /up
+
+- **WHEN** Dokploy or the container runtime evaluates application health after deploy
+- **THEN** it MUST request `/up`
+- **AND** MUST require HTTP 200 before marking the service healthy
+
+#### Scenario: Smoke failure on /up fails the deploy gate
+
+- **WHEN** post-deploy smoke requests `/up` and receives a non-200 response
+- **THEN** the staging promotion MUST be considered failed

openspec/specs/internal-authentication/spec.md

@@ -58,3 +58,35 @@ The system SHALL restrict user management (create, update, deactivate) to users
 - **WHEN** an authenticated assistant attempts to access user management in the panel
 - **THEN** the system MUST deny access via authorization policy
 
+### Requirement: Verified email is required for panel access
+
+Internal users MUST have a verified email address to access the Filament panel (SPEC §12.1, ADM-01). Active users with unverified email MUST be denied panel access. Development seeds MUST mark local demo users as verified.
+
+#### Scenario: Unverified active user is denied panel access
+
+- **WHEN** an active user with null `email_verified_at` authenticates
+- **THEN** the system MUST NOT grant access to the Filament panel
+
+#### Scenario: Verified active user can access the panel
+
+- **WHEN** an active user with a non-null `email_verified_at` submits valid credentials
+- **THEN** the system authenticates the user and allows Filament panel access subject to role rules
+
+#### Scenario: Local seed users are verified
+
+- **WHEN** `DatabaseSeeder` creates the local admin and assistant
+- **THEN** both users MUST have `email_verified_at` set
+
+### Requirement: Password reset flow is covered by automated tests
+
+The secure password reset flow for internal users MUST be covered by feature tests that assert a reset request for a registered email queues/sends a reset notification without revealing whether the email exists to the client (SPEC §12.1; existing password-reset requirement).
+
+#### Scenario: Reset request does not reveal account existence
+
+- **WHEN** a visitor submits a password reset for an unknown email
+- **THEN** the response MUST not disclose that the email is unregistered
+
+#### Scenario: Registered email receives reset notification
+
+- **WHEN** a visitor submits a password reset for a registered email
+- **THEN** the system MUST dispatch the password reset notification (faked in tests)

openspec/specs/public-site-motion/spec.md

@@ -0,0 +1,79 @@
+# public-site-motion Specification
+
+## Purpose
+
+Define progressive, accessible and non-blocking motion choreography for the public site, including shared timings, one-shot reveals, interaction feedback and safe fallbacks.
+
+## Requirements
+### Requirement: Public pages use shared progressive motion choreography
+
+The public site SHALL expose a declarative motion contract using `data-motion="page-open"`, `data-motion-beat`, `data-reveal-group`, `data-reveal`, and `data-reveal-from="up|left|right"`. Home, services, portfolio index/detail, about, contact, privacy, and branded 404/419/429/500/503 pages MUST use the contract without introducing route transitions.
+
+#### Scenario: Visual public route exposes motion hooks
+- **WHEN** a visitor loads any visual public route or branded error page
+- **THEN** the rendered page MUST expose a page opening hook and appropriate reveal hooks
+
+#### Scenario: Technical endpoints remain outside motion
+- **WHEN** a visitor requests `sitemap.xml` or `robots.txt`
+- **THEN** the response MUST NOT depend on the public motion runtime
+
+### Requirement: Editorial entrance timing and direction are consistent
+
+Entrances SHALL use shared tokens for an approximately 500 ms duration, 90 ms stagger capped at 270 ms, 12 px vertical distance, and 24 px desktop / 16 px mobile lateral distance. Text MUST remain fully visible; motion MUST use transforms and MAY use media clipping without opacity fades for text.
+
+#### Scenario: Reveal group computes capped stagger
+- **WHEN** more than four reveal items are rendered in one group
+- **THEN** the applied delay MUST NOT exceed 270 ms
+
+#### Scenario: Text enters without opacity fade
+- **WHEN** page opening or scroll reveal motion runs
+- **THEN** text MUST remain visible throughout the transition
+
+### Requirement: Reveals execute once without blocking interaction
+
+Each scroll reveal SHALL activate once, reach its final state, and be removed from observation. Visitors MUST be able to activate links and form controls while entrance motion is running.
+
+#### Scenario: Revealed content leaves observer
+- **WHEN** a reveal target intersects the configured viewport threshold
+- **THEN** it MUST receive the final state and be unobserved
+- **AND** scrolling away and back MUST NOT replay the reveal
+
+#### Scenario: CTA remains interactive during entrance
+- **WHEN** a visitor activates a CTA while its entrance is in progress
+- **THEN** navigation MUST proceed without waiting for animation completion
+
+### Requirement: Motion enhancement has immediate safe fallbacks
+
+Without JavaScript, without `IntersectionObserver`, or when `prefers-reduced-motion: reduce` is active, the site SHALL render every motion target immediately in its final usable state. Non-essential animation and transition MUST NOT run under reduced motion.
+
+#### Scenario: JavaScript is unavailable
+- **WHEN** a public page renders without executing JavaScript
+- **THEN** all content MUST be visible and usable in its final state
+
+#### Scenario: IntersectionObserver is unavailable
+- **WHEN** JavaScript runs but `IntersectionObserver` is not supported
+- **THEN** all reveal targets MUST remain in their final state
+
+#### Scenario: Reduced motion is preferred
+- **WHEN** the browser reports `prefers-reduced-motion: reduce`
+- **THEN** page openings, reveals, media clips, and non-essential feedback transitions MUST NOT run
+
+### Requirement: Public interaction feedback is short and accessible
+
+CTAs, links, navigation, and form controls SHALL provide short feedback using shared tokens while preserving visible `:focus-visible` indication. Alerts and validation messages MUST NOT be animated by this contract.
+
+#### Scenario: Keyboard focus remains visible
+- **WHEN** a visitor focuses an interactive element with the keyboard
+- **THEN** its focus indicator MUST remain visible and MUST NOT be displaced by motion feedback
+
+#### Scenario: Validation message appears without motion
+- **WHEN** server validation renders an error message
+- **THEN** the message MUST appear in its final position without entrance animation
+
+### Requirement: Home progress updates at most once per animation frame
+
+Scroll-driven chapter index and progress updates on the home SHALL be coalesced through `requestAnimationFrame`, with at most one pending update per frame.
+
+#### Scenario: Multiple scroll events occur in one frame
+- **WHEN** multiple scroll events fire before the next animation frame
+- **THEN** the home progress calculation MUST execute only once for that frame

openspec/specs/public-site-pages/spec.md

@@ -34,8 +34,7 @@ The system SHALL expose the public routes of SPEC §5.1: `home` (`/`), `services
 - **AND** the case MUST appear in the `/portfolio` listing
 
 ### Requirement: Home renders the editorial structure from CMS content
-
+The home page SHALL render, in order: header/navigation, hero, manifesto, featured services summary, featured portfolio selection, working method (four steps), testimonials, Amare positioning/profile, final contact CTA, and footer with contact, social links and legal links (WEB-01). Hero copy, brand name, manifesto, method and principles MUST come from `site_settings` (with editorial defaults when optional fields are empty); services, cases and testimonials MUST come from published records. The home MUST follow the Heritage Editorial composition: asymmetric spreads and tonal fields on desktop, with portfolio images in alternating editorial proportions, and a linear complete sequence on mobile rather than rounded card grids.
-The home page SHALL render, in order: header/navigation, hero, manifesto, featured services summary, featured portfolio selection, working method (four steps), testimonials, Amare positioning/profile, final contact CTA, and footer with contact, social links and legal links (WEB-01). Hero copy, brand name, manifesto, method and principles MUST come from `site_settings` (with editorial defaults when optional fields are empty); services, cases and testimonials MUST come from published records. The home MUST follow the Heritage Editorial composition (asymmetric spreads on desktop, linear sequence on mobile) rather than rounded card grids.
 
 #### Scenario: Published content is displayed in configured order
 
@@ -44,6 +43,7 @@ The home page SHALL render, in order: header/navigation, hero, manifesto, featur
 - **THEN** the published content MUST be displayed following the `sort_order` and featured flags
 - **AND** the hero MUST show the values stored in `site_settings`
 - **AND** the manifesto, method and positioning sections MUST be present
+- **AND** the portfolio section MUST use an olive tonal field with editorial image proportions
 
 #### Scenario: CTA leads to the contact placeholder page
 
@@ -65,8 +65,7 @@ The home page SHALL render, in order: header/navigation, hero, manifesto, featur
 - **THEN** the browser console MUST contain no JavaScript errors
 
 ### Requirement: Listing and detail pages exist for catalog content
-
+The system SHALL render a services listing (WEB-02) and a portfolio listing plus case detail (WEB-03) using the Heritage Editorial visual language. The case detail MUST present summary, event type, optional city/venue/date, challenge, solution, optional result, cover image and the ordered gallery. Portfolio listings and galleries MUST use alternating editorial image proportions on desktop while retaining DOM order and a single-column readable sequence on mobile.
-The system SHALL render a services listing (WEB-02) and a portfolio listing plus case detail (WEB-03) using the Heritage Editorial visual language. The case detail MUST present summary, event type, optional city/venue/date, challenge, solution, optional result, cover image and the ordered gallery.
 
 #### Scenario: Services listing shows published services
 
@@ -79,6 +78,7 @@ The system SHALL render a services listing (WEB-02) and a portfolio listing plus
 - **GIVEN** a published case with multiple gallery images
 - **WHEN** a visitor loads the case detail
 - **THEN** the images MUST be rendered ordered by `sort_order`
+- **AND** desktop presentation MUST alternate editorial image proportions without changing that order
 
 #### Scenario: Listings paginate open-ended growth
 
@@ -86,8 +86,7 @@ The system SHALL render a services listing (WEB-02) and a portfolio listing plus
 - **THEN** `/portfolio` MUST paginate instead of rendering all records
 
 ### Requirement: Institutional and error pages have brand identity
-
+The system SHALL provide the Sobre and Política de privacidade pages and branded error pages (WEB-07) using the Heritage Editorial public layout, including the brand mark when available. Contact, privacy and error surfaces MUST remain sober tonal layouts without decorative photography. The 404 page MUST use the public layout, and the 500 page MUST NOT expose stack traces or internal details when `APP_DEBUG` is false.
-The system SHALL provide the Sobre and Política de privacidade pages and branded error pages (WEB-07) using the Heritage Editorial public layout, including the brand mark when available. The 404 page MUST use the public layout, and the 500 page MUST NOT expose stack traces or internal details when `APP_DEBUG` is false.
 
 #### Scenario: Unknown URL renders branded 404
 
@@ -146,3 +145,16 @@ When public pages render illustrative/demo photography that is not an authorized
 
 - **WHEN** the home or portfolio renders placeholder photography
 - **THEN** a visible note or equivalent disclosure MUST indicate the imagery is illustrative pending authorized assets
+
+### Requirement: Visual public and error pages expose the shared motion contract
+
+The system SHALL apply the shared progressive opening and reveal contract to home, services, portfolio index/detail, about, contact, privacy, and branded 404/419/429/500/503 pages. The contract MUST NOT change page copy, content ordering, route behavior, or structural layout.
+
+#### Scenario: Institutional page uses shared opening
+- **WHEN** a visitor loads `/sobre`, `/contato`, or `/privacidade`
+- **THEN** the page MUST expose the shared page opening hook and section reveal hooks
+
+#### Scenario: Error page remains branded and progressively enhanced
+- **WHEN** Laravel renders a branded 404, 419, 429, 500, or 503 response
+- **THEN** the page MUST expose the shared opening hook
+- **AND** all error guidance and navigation MUST remain immediately usable without enhancement

openspec/specs/quality-gates/spec.md

@@ -1,7 +1,7 @@
 # quality-gates Specification
 
 ## Purpose
-Define Composer quality scripts, architecture boundaries, PostgreSQL-backed feature tests, and the five blocking CI jobs including browser visual and accessibility coverage.
+Define Composer quality scripts, architecture boundaries, PostgreSQL-backed feature tests, and the five blocking CI jobs including browser functional, accessibility and motion coverage.
 
 ## Requirements
 ### Requirement: Standardized Composer test scripts exist
@@ -53,20 +53,57 @@ The system SHALL configure `phpunit.xml` so that the Feature test suite uses Pos
 
 ### Requirement: Browser tests run against FrankenPHP-served application
 
-The system SHALL execute browser tests using Pest Browser/Playwright against an application served by FrankenPHP in CI. The `browser` job MUST cover the E2E journeys available in the current phase, the visual regression assertions and the automated accessibility checks for public routes, and MUST run in assertion mode without regenerating baselines (SPEC §13.4, §13.5, §13.8, §14.1).
+The system SHALL execute browser tests using Pest Browser/Playwright against an application served by FrankenPHP in CI. The `browser` job MUST cover the E2E journeys available in the current phase, automated accessibility checks, motion behavior and smoke checks for public routes (SPEC §13.4, §13.7 and §14.1), without pixel comparison.
 
 #### Scenario: Browser job validates served application
 
 - **WHEN** the `browser` CI job runs
 - **THEN** tests execute against the built application artifact or equivalent production-like image
 
-#### Scenario: Browser job covers visual and accessibility assertions
+#### Scenario: Browser job covers functional, accessibility and motion assertions
 
 - **WHEN** the `browser` CI job runs
-- **THEN** it MUST execute the visual regression suite and the accessibility suite
+- **THEN** it MUST execute the functional browser, accessibility, motion and smoke suites
-- **AND** a failing snapshot or a critical/serious accessibility issue MUST block merge
+- **AND** a failing functional assertion or a critical/serious accessibility issue MUST block merge
 
 #### Scenario: Browser failures publish diagnostics
 
 - **WHEN** a browser test fails in CI
-- **THEN** the job MUST publish screenshots, snapshot diffs, application logs and browser logs as artifacts
+- **THEN** the job MUST publish application logs and browser logs as diagnostics
+
+### Requirement: Quality gate includes npm dependency audit
+
+The system SHALL run an npm audit as part of the quality/static gate according to the project policy (SPEC §12.6, §13.9). Audit failure MUST block merge unless an explicit, documented exception exists.
+
+#### Scenario: Vulnerable dependency fails static gate
+
+- **WHEN** `npm audit` reports a policy-violating vulnerability in production dependencies
+- **THEN** the static/quality gate MUST fail and block merge
+
+#### Scenario: Developer runs quality locally with audit
+
+- **WHEN** a developer runs `composer quality` (or the documented npm audit step it requires)
+- **THEN** the npm audit MUST execute as part of the gate sequence
+
+### Requirement: Domain and Application maintain minimum coverage
+
+The CI unit gate SHALL measure code coverage for `App\Domain` and `App\Application` and MUST fail when either namespace falls below 80% (SPEC §13.7). Views, migrations, generated code, and framework code MUST NOT be required to meet this threshold.
+
+#### Scenario: Coverage drop below threshold blocks merge
+
+- **WHEN** Domain or Application coverage is below 80% on the unit CI job
+- **THEN** the job MUST fail
+
+#### Scenario: Coverage ignores non-domain layers
+
+- **WHEN** coverage is computed for the gate
+- **THEN** Blade views and migrations MUST NOT be counted toward the Domain/Application threshold
+
+### Requirement: Staging deploy job runs only after blocking CI jobs
+
+When deploying from `main`, the staging deploy workflow MUST require the five blocking CI jobs (`static`, `unit`, `feature`, `browser`, `container`) to succeed before building/pushing the image and triggering Dokploy (SPEC §14.1, §14.3).
+
+#### Scenario: Failed browser job prevents staging deploy
+
+- **WHEN** the `browser` CI job fails on `main`
+- **THEN** the staging deploy workflow MUST NOT promote a new image

openspec/specs/staging-deployment/spec.md

@@ -0,0 +1,83 @@
+# staging-deployment Specification
+
+## Purpose
+
+Define immutable staging and production promotion through GHCR and Dokploy Compose, including migration, health, smoke, rollback, and backup evidence.
+
+## Requirements
+
+### Requirement: Staging deploys an immutable application image by commit SHA
+
+The system SHALL deploy staging from a single FrankenPHP application image tagged with the Git commit SHA and published to GHCR (SPEC §14.3, §15.2). Web, queue worker, and scheduler processes MUST use that same image digest. Rebuilds per process on the staging host MUST NOT be the promotion path.
+
+#### Scenario: Same image serves all application processes
+
+- **WHEN** a staging deployment is promoted for commit SHA `abc123`
+- **THEN** web, queue, and scheduler MUST run from `ghcr.io/<owner>/<repo>:abc123` (or equivalent digest)
+- **AND** MUST NOT rebuild distinct images per process
+
+#### Scenario: CI publishes the image before Dokploy deploy
+
+- **WHEN** `main` passes the blocking CI jobs
+- **THEN** the deploy workflow MUST build and push the SHA-tagged image before triggering Dokploy
+
+### Requirement: Staging runs on Dokploy Compose on the operator VPS
+
+Staging SHALL be operated as a Dokploy Docker Compose deployment on the operator-managed VPS. PostgreSQL MUST be a managed private database service; application media MUST use the configured production object storage disk (`r2`) and mail MUST use the configured Resend transport when enabled.
+
+#### Scenario: Compose defines required processes
+
+- **WHEN** staging Compose is deployed
+- **THEN** it MUST include web, queue worker, scheduler, and a one-shot migrate job using the application image
+
+#### Scenario: Database is not embedded in the application image
+
+- **WHEN** staging boots
+- **THEN** PostgreSQL MUST be provided by the Dokploy/database service
+- **AND** MUST NOT live inside the application image layers
+
+### Requirement: Staging deploy migrates then proves health with smoke checks
+
+A staging promotion MUST run database migrations against the staging database, wait for `/up` to report healthy, and execute smoke HTTP checks for `/up`, the public home, and `/admin/login` (SPEC §14.3, §15.5, §16.2).
+
+#### Scenario: Unhealthy deploy is not considered successful
+
+- **WHEN** `/up` fails after a staging deploy attempt
+- **THEN** the deployment MUST be treated as failed
+- **AND** MUST NOT be recorded as a successful Phase 0 exit criterion
+
+#### Scenario: Smoke checks cover public and login surfaces
+
+- **WHEN** staging deploy health succeeds
+- **THEN** smoke checks MUST request `/`, `/up`, and `/admin/login`
+- **AND** each MUST return HTTP 200
+
+### Requirement: Staging rollback uses the previous image SHA
+
+Rollback SHALL redeploy a previously published SHA-tagged image without rebuilding from source (SPEC §14.3).
+
+#### Scenario: Operator rolls back to previous SHA
+
+- **WHEN** the operator points staging Compose at a previous SHA tag and redeploys
+- **THEN** web, queue, and scheduler MUST run that previous image
+- **AND** no source rebuild MUST be required
+
+### Requirement: Production promotion reuses the same immutable digest
+
+Production SHALL be promoted from an already-published SHA-tagged image without rebuilding from source. Promotion MUST require explicit human action (SPEC §14.3).
+
+#### Scenario: Operator promotes a staging-approved SHA to production
+
+- **WHEN** the operator confirms promotion of commit SHA `abc123`
+- **THEN** production web, queue, and scheduler MUST run the same digest previously published as `ghcr.io/<owner>/<repo>:abc123`
+- **AND** MUST NOT rebuild from source for that promotion
+
+### Requirement: Database backups exist before production cutover
+
+Staging and production PostgreSQL services SHALL have automated daily backups with retention of at least 14 days, and a documented restore procedure MUST be verified on staging before the first production promotion (SPEC §16.3).
+
+#### Scenario: Staging restore is proven before production promotion
+
+- **WHEN** the operator prepares the first production promotion
+- **THEN** a restore from a staging backup MUST have been documented and successfully tested
+- **AND** production MUST have daily backup configured with retention of at least 14 days

openspec/specs/testimonials/spec.md

@@ -6,7 +6,7 @@ Define testimonial management, publication, authorization, and featured filterin
 ## Requirements
 ### Requirement: Testimonials are managed with publication control
 
-The system SHALL allow admins to manage testimonials (SPEC WEB-04) with quote text (including multi-paragraph content), author name, optional context (event type and/or date), optional photo with alt text, sort order, featured flag, and `published_at`. Public rendering MUST preserve paragraph breaks from the stored quote. Testimonials sourced from real clients MUST NOT be published to production without authorization; development seeds MAY include the authorized-pending real quotes marked for review.
+The system SHALL allow admins to manage testimonials (SPEC WEB-04) with quote text (including multi-paragraph content), author name, optional context (event type and/or date), optional photo with alt text, sort order, featured flag, and `published_at`. Public rendering MUST preserve paragraph breaks from the stored quote, MUST omit blank/whitespace-only quotes before creating the rendered sequence, and MUST assign alternating `left`/`right` reveal directions according to the remaining rendered column order at desktop and mobile viewports. Testimonials sourced from real clients MUST NOT be published to production without authorization; development seeds MAY include the authorized-pending real quotes marked for review.
 
 #### Scenario: Unpublished testimonial is excluded
 
@@ -34,6 +34,18 @@ The system SHALL allow admins to manage testimonials (SPEC WEB-04) with quote te
 - **WHEN** the home testimonials section is rendered
 - **THEN** each paragraph MUST appear as distinct block text rather than a single collapsed line
 
+#### Scenario: Blank quotes do not affect alternation
+
+- **GIVEN** the published testimonial collection contains a blank quote between two non-blank quotes
+- **WHEN** the home testimonials section is rendered
+- **THEN** the blank testimonial MUST be omitted
+- **AND** the two rendered testimonials MUST receive alternating `left` and `right` directions based on their rendered order
+
+#### Scenario: Direction alternation remains on mobile
+
+- **WHEN** testimonials are viewed at a mobile viewport
+- **THEN** their explicit `left` and `right` directions MUST be preserved with the reduced mobile distance
+
 ### Requirement: Real wedding testimonials are seeded from authorized source copy
 
 Content and visual seeders SHALL replace fictional testimonials with the five real wedding testimonials from `depoimentos.md`, preserving author couple names, quote wording, and date/context. Until final publication authorization is confirmed, production deployments MUST keep those records unpublished or gated by explicit admin publish action.

openspec/specs/visual-regression/spec.md

@@ -1,60 +0,0 @@
-# visual-regression Specification
-
-## Purpose
-Define deterministic visual baselines for public screens and the explicit baseline update workflow.
-
-## Requirements
-### Requirement: Public screens have desktop and mobile visual baselines
-
-The system SHALL keep versioned screenshot baselines for the public screens available in this phase (SPEC §13.5): Home, Serviços, Portfólio and Detalhe do portfólio, at 1440×1000 desktop and 390×844 mobile, under the Heritage Editorial identity. A rendering change that alters those screens MUST fail the browser suite until the diff is reviewed and baselines are explicitly updated.
-
-#### Scenario: Unintended visual change fails the suite
-
-- **GIVEN** approved baselines exist
-- **WHEN** a code change alters the rendering of a covered screen
-- **THEN** the visual assertion MUST fail and report the diff
-
-#### Scenario: Both viewports are covered
-
-- **WHEN** the visual suite runs
-- **THEN** each covered screen MUST be asserted at 1440×1000 and 390×844
-
-#### Scenario: Heritage Editorial identity is captured
-
-- **WHEN** approved baselines for the home are reviewed after this change
-- **THEN** they MUST reflect EB Garamond typography, olive/paper palette and sharp-edged editorial layout rather than the previous gold/rounded placeholder look
-
-### Requirement: Visual runs are deterministic
-
-Visual runs SHALL be deterministic per SPEC §13.5: fixed Chromium and Linux image, fixed viewport, timezone `America/Sao_Paulo`, locale `pt-BR`, self-hosted fonts installed/bundled for the suite, frozen clock, deterministic seed (including real testimonial subset and São Paulo settings), animations and transitions disabled, and no dependency on external network.
-
-#### Scenario: Repeated run without code change produces no diff
-
-- **WHEN** the visual suite runs twice against the same commit and seed
-- **THEN** both runs MUST pass with no pixel diff
-
-#### Scenario: Time-dependent content does not cause drift
-
-- **GIVEN** the clock is frozen and the seed is deterministic
-- **WHEN** the suite runs on a different calendar day
-- **THEN** rendered dates MUST remain identical to the baseline
-
-#### Scenario: Motion is disabled during capture
-
-- **WHEN** a screenshot is captured
-- **THEN** CSS animations and transitions MUST be disabled
-
-### Requirement: Baseline updates are explicit and reviewed
-
-Baselines SHALL only be updated through the explicit `composer visual:update` command, and the resulting diff MUST be reviewed by a human before merge. Baselines MUST NOT be regenerated automatically to make CI pass.
-
-#### Scenario: CI does not regenerate baselines
-
-- **WHEN** the `browser` CI job runs
-- **THEN** it MUST run in assertion mode
-- **AND** MUST NOT write new baselines
-
-#### Scenario: Developer updates baselines intentionally
-
-- **WHEN** a developer runs `composer visual:update`
-- **THEN** the updated baseline files MUST be written to the versioned baseline directory for review

openspec/specs/web-accessibility/spec.md

@@ -6,7 +6,7 @@ Define automated accessibility checks, semantic structure, keyboard operability,
 ## Requirements
 ### Requirement: Public routes have no critical or serious accessibility issues
 
-The system SHALL run automated accessibility checks on the public routes covered by the browser suite (SPEC §6.5, §13.8) after the Heritage Editorial redesign. A critical or serious issue MUST fail the suite.
+The system SHALL run automated accessibility checks on the public routes covered by the browser suite (SPEC §6.5, §13.8) after the Heritage Editorial motion enhancement. A critical or serious issue MUST fail the suite.
 
 #### Scenario: Critical issue blocks the suite
 
@@ -16,7 +16,7 @@ The system SHALL run automated accessibility checks on the public routes covered
 #### Scenario: Covered routes are checked
 
 - **WHEN** the accessibility suite runs
-- **THEN** the home, services listing, portfolio listing and case detail MUST each be checked
+- **THEN** home, services listing, portfolio listing, case detail, about, contact, privacy and branded 404 MUST each be checked
 
 ### Requirement: Public pages use accessible semantic structure
 
@@ -65,19 +65,34 @@ Visitors SHALL be able to reach and activate every interactive element with the
 
 ### Requirement: Reduced motion preference is honored
 
-The system SHALL suppress non-essential animation and transition when the user agent reports `prefers-reduced-motion: reduce`, including editorial hover scales and menu transitions introduced by the redesign.
+The system SHALL suppress non-essential animation and transition when the user agent reports `prefers-reduced-motion: reduce`, including page openings, editorial reveals, image hover scales, interaction feedback and menu transitions. All affected content MUST render in its final visible and interactive state.
 
 #### Scenario: Reduced motion disables transitions
 
 - **GIVEN** the browser reports `prefers-reduced-motion: reduce`
 - **WHEN** a public page is loaded
 - **THEN** decorative transitions and animations MUST NOT run
+- **AND** every motion target MUST be in its final visible and interactive state
 
 ### Requirement: Public pages emit no console errors
 
-Covered public routes SHALL load without JavaScript console errors in a real browser (SPEC §13.8, §19), including pages that load the mobile navigation script.
+Covered public routes SHALL load without JavaScript console errors in a real browser (SPEC §13.8, §19), including home, services listing, portfolio listing, case detail, about, contact, privacy, branded 404, and pages that load the mobile navigation or motion runtime.
 
 #### Scenario: Console stays clean on covered routes
 
 - **WHEN** a covered public route is loaded in the browser suite
 - **THEN** the console MUST contain no error-level messages
+
+### Requirement: Motion enhancement failure does not hide or disable content
+
+The public site SHALL remain readable, keyboard-operable, and interactive when JavaScript is disabled or `IntersectionObserver` is unavailable. Motion targets MUST default to their final state without relying on timeout recovery.
+
+#### Scenario: JavaScript disabled keeps public page usable
+
+- **WHEN** a visitor loads a public page with JavaScript disabled
+- **THEN** headings, copy, navigation, CTAs, and form controls MUST be visible and operable
+
+#### Scenario: Observer unavailable keeps reveals final
+
+- **WHEN** the motion runtime executes without `IntersectionObserver`
+- **THEN** reveal targets MUST remain in the final state

package-lock.json

@@ -1,5 +1,5 @@
 {
-    "name": "site-amare",
+    "name": "daisyui",
     "lockfileVersion": 3,
     "requires": true,
     "packages": {
@@ -7,6 +7,7 @@
             "devDependencies": {
                 "@tailwindcss/vite": "^4.0.0",
                 "concurrently": "^9.0.1",
+                "daisyui": "^5.7.16",
                 "husky": "^9.1.7",
                 "laravel-vite-plugin": "^3.1",
                 "playwright": "^1.62.0",
@@ -790,6 +791,16 @@
                 "url": "https://github.com/open-cli-tools/concurrently?sponsor=1"
             }
         },
+        "node_modules/daisyui": {
+            "version": "5.7.16",
+            "resolved": "https://registry.npmjs.org/daisyui/-/daisyui-5.7.16.tgz",
+            "integrity": "sha512-V9CJxvrWIXTDuP/0tpijjWaKaKJNYo2IrULJfTWs3/DjW9rPqswk1n8NCLQRLrTutmlG2Ech7nkJDpCnF+6Dzw==",
+            "dev": true,
+            "license": "MIT",
+            "funding": {
+                "url": "https://github.com/saadeghi/daisyui?sponsor=1"
+            }
+        },
         "node_modules/detect-libc": {
             "version": "2.1.2",
             "resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-2.1.2.tgz",

package.json

@@ -10,6 +10,7 @@
     "devDependencies": {
         "@tailwindcss/vite": "^4.0.0",
         "concurrently": "^9.0.1",
+        "daisyui": "^5.7.16",
         "husky": "^9.1.7",
         "laravel-vite-plugin": "^3.1",
         "playwright": "^1.62.0",