feat(home): preencher hero fotográfico

.github/workflows/ci.yml

@@ -6,7 +6,7 @@ on:
   pull_request:
 
 concurrency:
-  group: ci-${{ gitea.workflow }}-${{ gitea.ref }}
+  group: ci-${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true
 
 env:
@@ -18,9 +18,7 @@ env:
   BCRYPT_ROUNDS: 4
   CACHE_STORE: database
   DB_CONNECTION: pgsql
-  # Service hostname on the per-job network (act_runner with empty
-  # container.network). Do not publish host :5432/:8000 — parallel jobs collide.
-  DB_HOST: postgres
+  DB_HOST: 127.0.0.1
   DB_PORT: 5432
   DB_DATABASE: amare_test
   DB_USERNAME: amare
@@ -42,6 +40,12 @@ jobs:
           extensions: dom, curl, libxml, mbstring, zip, pcntl, pdo, pdo_pgsql, bcmath, intl, sodium, gd
           coverage: none
 
+      - uses: actions/cache@v5
+        with:
+          path: ~/.composer/cache/files
+          key: composer-${{ runner.os }}-${{ hashFiles('**/composer.lock') }}
+          restore-keys: composer-${{ runner.os }}-
+
       - run: composer validate --strict
       - run: composer install --no-interaction --prefer-dist
       - run: composer pint:check
@@ -70,6 +74,8 @@ jobs:
           POSTGRES_DB: amare_test
           POSTGRES_USER: amare
           POSTGRES_PASSWORD: secret
+        ports:
+          - 5432:5432
         options: >-
           --health-cmd "pg_isready -U amare -d amare_test"
           --health-interval 5s
@@ -85,6 +91,18 @@ jobs:
           extensions: dom, curl, libxml, mbstring, zip, pcntl, pdo, pdo_pgsql, bcmath, intl, sodium, gd
           coverage: pcov
 
+      - uses: actions/cache@v5
+        with:
+          path: ~/.composer/cache/files
+          key: composer-${{ runner.os }}-${{ hashFiles('**/composer.lock') }}
+          restore-keys: composer-${{ runner.os }}-
+
+      - uses: actions/cache@v5
+        with:
+          path: ~/.npm
+          key: npm-${{ runner.os }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: npm-${{ runner.os }}-
+
       - run: composer install --no-interaction --prefer-dist
       - run: npm ci
       - run: npm run build
@@ -108,6 +126,8 @@ jobs:
           POSTGRES_DB: amare_test
           POSTGRES_USER: amare
           POSTGRES_PASSWORD: secret
+        ports:
+          - 5432:5432
         options: >-
           --health-cmd "pg_isready -U amare -d amare_test"
           --health-interval 5s
@@ -123,6 +143,18 @@ jobs:
           extensions: dom, curl, libxml, mbstring, zip, pcntl, pdo, pdo_pgsql, bcmath, intl, sodium, gd
           coverage: none
 
+      - uses: actions/cache@v5
+        with:
+          path: ~/.composer/cache/files
+          key: composer-${{ runner.os }}-${{ hashFiles('**/composer.lock') }}
+          restore-keys: composer-${{ runner.os }}-
+
+      - uses: actions/cache@v5
+        with:
+          path: ~/.npm
+          key: npm-${{ runner.os }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: npm-${{ runner.os }}-
+
       - run: composer install --no-interaction --prefer-dist
       - run: npm ci
       - run: npm run build
@@ -139,6 +171,8 @@ jobs:
           POSTGRES_DB: amare_test
           POSTGRES_USER: amare
           POSTGRES_PASSWORD: secret
+        ports:
+          - 5432:5432
         options: >-
           --health-cmd "pg_isready -U amare -d amare_test"
           --health-interval 5s
@@ -154,6 +188,18 @@ jobs:
           extensions: dom, curl, libxml, mbstring, zip, pcntl, pdo, pdo_pgsql, bcmath, intl, sodium, gd
           coverage: none
 
+      - uses: actions/cache@v5
+        with:
+          path: ~/.composer/cache/files
+          key: composer-${{ runner.os }}-${{ hashFiles('**/composer.lock') }}
+          restore-keys: composer-${{ runner.os }}-
+
+      - uses: actions/cache@v5
+        with:
+          path: ~/.npm
+          key: npm-${{ runner.os }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: npm-${{ runner.os }}-
+
       - run: composer install --no-interaction --prefer-dist
       - run: npm ci
       - run: npm run build
@@ -166,28 +212,15 @@ jobs:
 
       - name: Run browser tests against FrankenPHP container
         run: |
-          # Join the per-job network (act_runner creates one when
-          # container.network is empty). No host -p: parallel jobs would
-          # collide on :8000/:5432; DNS names work on the job network.
-          # Container --name is global on the shared docker.sock host —
-          # include run id or leftovers from cancelled jobs Conflict.
-          JOB_CID="$(hostname)"
-          JOB_NET="$(docker inspect -f '{{range $k, $_ := .NetworkSettings.Networks}}{{println $k}}{{end}}' "$JOB_CID" | head -n1)"
-          test -n "$JOB_NET"
-          WEB_NAME="amare-web-${GITHUB_RUN_ID:-$$}"
-          docker rm -f "$WEB_NAME" 2>/dev/null || true
-
-          docker run -d --name "$WEB_NAME" \
-            --network "$JOB_NET" \
-            --network-alias amare-web \
+          docker run -d --name amare-web \
             -e APP_ENV=testing \
             -e APP_KEY="${APP_KEY}" \
-            -e APP_URL=http://amare-web:8000 \
+            -e APP_URL=http://127.0.0.1:8000 \
             -e APP_LOCALE=pt_BR \
             -e APP_FALLBACK_LOCALE=pt_BR \
             -e APP_TIMEZONE=America/Sao_Paulo \
             -e DB_CONNECTION=pgsql \
-            -e DB_HOST=postgres \
+            -e DB_HOST=host.docker.internal \
             -e DB_PORT=5432 \
             -e DB_DATABASE=amare_test \
             -e DB_USERNAME=amare \
@@ -195,28 +228,26 @@ jobs:
             -e SESSION_DRIVER=database \
             -e CACHE_STORE=database \
             -e QUEUE_CONNECTION=database \
+            --add-host=host.docker.internal:host-gateway \
             -v "${GITHUB_WORKSPACE}/storage/app/public:/app/storage/app/public" \
+            -p 8000:8000 \
             amare-app:ci
 
-          cleanup() { docker rm -f "$WEB_NAME" >/dev/null 2>&1 || true; }
-          trap cleanup EXIT
-
           for i in $(seq 1 30); do
-            if curl -fsS http://amare-web:8000/up; then
+            if curl -fsS http://127.0.0.1:8000/up; then
               break
             fi
             sleep 2
           done
 
-          curl -fsS http://amare-web:8000/up
-          APP_URL=http://amare-web:8000 ./vendor/bin/pest --testsuite=Browser
+          curl -fsS http://127.0.0.1:8000/up
+          ./vendor/bin/pest --testsuite=Browser
 
       - name: Collect failure diagnostics
         if: failure()
         run: |
           mkdir -p artifacts/browser
-          WEB_NAME="amare-web-${GITHUB_RUN_ID:-$$}"
-          docker logs "$WEB_NAME" > artifacts/browser/container.log 2>&1 || true
+          docker logs amare-web > artifacts/browser/container.log 2>&1 || true
           cp -R storage/logs artifacts/browser/app-logs 2>/dev/null || true
 
       - name: Upload browser failure artifacts
@@ -238,21 +269,10 @@ jobs:
 
       - name: Verify container healthcheck and storage link
         run: |
-          # Same per-job network as the step container — no host :8000
-          # publish (collides when capacity > 1). Unique --name: docker.sock
-          # is shared across jobs; leftovers from cancelled runs Conflict.
-          JOB_CID="$(hostname)"
-          JOB_NET="$(docker inspect -f '{{range $k, $_ := .NetworkSettings.Networks}}{{println $k}}{{end}}' "$JOB_CID" | head -n1)"
-          test -n "$JOB_NET"
-          HEALTH_NAME="amare-health-${GITHUB_RUN_ID:-$$}"
-          docker rm -f "$HEALTH_NAME" 2>/dev/null || true
-
-          docker run -d --name "$HEALTH_NAME" \
-            --network "$JOB_NET" \
-            --network-alias amare-health \
+          docker run -d --name amare-health \
             -e APP_ENV=production \
             -e APP_KEY="${{ env.APP_KEY }}" \
-            -e APP_URL=http://amare-health:8000 \
+            -e APP_URL=http://127.0.0.1:8000 \
             -e APP_DEBUG=false \
             -e DB_CONNECTION=pgsql \
             -e DB_HOST=127.0.0.1 \
@@ -260,18 +280,16 @@ jobs:
             -e DB_DATABASE=amare \
             -e DB_USERNAME=amare \
             -e DB_PASSWORD=secret \
+            -p 8000:8000 \
             amare-app:ci
 
-          cleanup() { docker rm -f "$HEALTH_NAME" >/dev/null 2>&1 || true; }
-          trap cleanup EXIT
-
           for i in $(seq 1 30); do
-            if curl -fsS http://amare-health:8000/up; then
-              docker exec "$HEALTH_NAME" test -L /app/public/storage
+            if curl -fsS http://127.0.0.1:8000/up; then
+              docker exec amare-health test -L /app/public/storage
               exit 0
             fi
             sleep 2
           done
 
-          docker logs "$HEALTH_NAME"
+          docker logs amare-health
           exit 1

.github/workflows/deploy-staging.yml

@@ -1,16 +1,10 @@
 name: Deploy staging
 
-# Requires Gitea >= 1.25 for workflow_run (1.24.x has no trigger match).
 on:
   workflow_run:
-    workflows:
-      - CI
-      - ci.yml
-    types:
-      - completed
-    branches:
-      - main
-  workflow_dispatch:
+    workflows: [CI]
+    types: [completed]
+    branches: [main]
 
 permissions:
   contents: read
@@ -21,28 +15,27 @@ concurrency:
   cancel-in-progress: false
 
 env:
-  REGISTRY: git.hellomanoel.com
-  IMAGE_NAME: ${{ gitea.repository }}
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
 
 jobs:
   deploy:
     name: publish-and-deploy-staging
     if: >-
-      gitea.event_name == 'workflow_dispatch' ||
-      (gitea.event.workflow_run.conclusion == 'success' &&
-       gitea.event.workflow_run.event == 'push' &&
-       gitea.event.workflow_run.head_branch == 'main')
+      github.event.workflow_run.conclusion == 'success' &&
+      github.event.workflow_run.event == 'push' &&
+      github.event.workflow_run.head_branch == 'main'
     runs-on: ubuntu-latest
     steps:
       - name: Checkout deployed SHA
         uses: actions/checkout@v4
         with:
-          ref: ${{ gitea.event.workflow_run.head_sha || gitea.sha }}
+          ref: ${{ github.event.workflow_run.head_sha }}
 
       - name: Set image metadata
         id: meta
         run: |
-          SHA="${{ gitea.event.workflow_run.head_sha || gitea.sha }}"
+          SHA="${{ github.event.workflow_run.head_sha }}"
           SHORT_SHA="${SHA:0:7}"
           IMAGE="${REGISTRY}/${IMAGE_NAME}"
           IMAGE="$(echo "$IMAGE" | tr '[:upper:]' '[:lower:]')"
@@ -50,14 +43,12 @@ jobs:
           echo "short_sha=${SHORT_SHA}" >> "$GITHUB_OUTPUT"
           echo "image=${IMAGE}" >> "$GITHUB_OUTPUT"
 
-      - name: Log in to Gitea registry
+      - name: Log in to GHCR
         uses: docker/login-action@v3
         with:
           registry: ${{ env.REGISTRY }}
-          # Gitea's GITEA_TOKEN cannot push OCI packages (gitea#23642); a PAT
-          # with read:package/write:package scopes is required instead.
-          username: ${{ secrets.REGISTRY_USER }}
-          password: ${{ secrets.REGISTRY_PAT }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
@@ -70,6 +61,8 @@ jobs:
           tags: |
             ${{ steps.meta.outputs.image }}:${{ steps.meta.outputs.sha }}
             ${{ steps.meta.outputs.image }}:staging
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
 
       - name: Deploy staging on Dokploy
         env:

.github/workflows/promote-production.yml

@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
     inputs:
       sha:
-        description: Full git SHA already published to the Gitea registry (same digest used by staging)
+        description: Full git SHA already published to GHCR (same digest used by staging)
         required: true
         type: string
       confirm:
@@ -21,8 +21,8 @@ concurrency:
   cancel-in-progress: false
 
 env:
-  REGISTRY: git.hellomanoel.com
-  IMAGE_NAME: ${{ gitea.repository }}
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
 
 jobs:
   promote:
@@ -50,14 +50,12 @@ jobs:
           echo "short_sha=${SHORT_SHA}" >> "$GITHUB_OUTPUT"
           echo "image=${IMAGE}" >> "$GITHUB_OUTPUT"
 
-      - name: Log in to Gitea registry
+      - name: Log in to GHCR
         uses: docker/login-action@v3
         with:
           registry: ${{ env.REGISTRY }}
-          # Gitea's GITEA_TOKEN cannot push OCI packages (gitea#23642); a PAT
-          # with read:package/write:package scopes is required instead.
-          username: ${{ secrets.REGISTRY_USER }}
-          password: ${{ secrets.REGISTRY_PAT }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3

.gitignore

@@ -26,6 +26,3 @@ Homestead.json
 Homestead.yaml
 Thumbs.db
 .worktrees/
-
-# Pest Browser visual diffs (local/CI artifacts)
-/tests/Browser/Screenshots/

AGENTS.md

@@ -31,13 +31,9 @@ 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. 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.
+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.
 
 ## Commit & Pull Request Guidelines
 

CLAUDE.md

@@ -14,22 +14,17 @@ 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.
 
-## Git remotes — Gitea origin, GitHub legacy
+## Git remote auth — two GitHub accounts
 
-`origin` is `git@git.hellomanoel.com:manoel-freitas/amare.git` (self-hosted Gitea). CI/CD and the container registry live there (`git.hellomanoel.com`). Verify SSH with `ssh -T git@git.hellomanoel.com` → should greet `Hi there, manoel-freitas!`.
+`origin` is `git@github.com:manoel-freitas/amore-site.git`, owned by the **`manoel-freitas`** account. The machine's default SSH identity is a different account (`manoel-freitas-neto`) that cannot see this repo, so pushes fail with `ERROR: Repository not found.` — an access error that reads like a missing repo.
 
-The remote named `github` is the legacy mirror `git@github.com:manoel-freitas/amore-site.git`. Push there only when intentionally syncing the backup. That GitHub account still needs `~/.ssh/id_github_pessoal` (or an equivalent key) when the machine's default identity is a different GitHub user (`manoel-freitas-neto`) that cannot see the repo.
-
-- Prefer plain `git push` / `git push origin <branch>` against Gitea.
-- **`gh`** talks to GitHub only. Use the Gitea web UI or API for PRs on `amare`. If you still need `gh` against the legacy remote, confirm `gh auth status` shows `manoel-freitas`.
+- Correct key: `~/.ssh/id_github_pessoal`. Verify with `ssh -i ~/.ssh/id_github_pessoal -o IdentitiesOnly=yes -T git@github.com` → should greet `Hi manoel-freitas!`.
+- The repo has `core.sshCommand = ssh -i ~/.ssh/id_github_pessoal -o IdentitiesOnly=yes` set locally, so plain `git push` works. If that config is lost, restore it instead of editing the remote URL.
+- **`gh` authenticates separately**, by token rather than SSH key. As of 2026-08-10 it is logged in as `manoel-freitas`, so `gh pr create` / `gh repo view` work. Confirm with `gh auth status` before assuming: if it reports `manoel-freitas-neto`, that account cannot see this repo and every `gh` call fails on it. Recovering needs an interactive `gh auth login` (or `gh auth switch` with both accounts added), so ask the user to run it.
 
 ## Request spine for the public site
 

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. 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.
+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.
 
 **The Editorial Rhythm Rule.** Seções alternam imagem, texto, densidade e silêncio; repetição de grades idênticas por toda página é proibida.
 
@@ -109,4 +109,4 @@ Círculos ficam reservados para retratos ou indicadores que exigem forma circula
 - **Don't** misturar famílias tipográficas sem redefinição explícita da identidade.
 - **Don't** transformar oliva em pequenos acentos sobre uma página dominada por branco puro.
 - **Don't** inventar cases, números, credenciais, clientes ou prova corporativa.
-- **Don't** usar decoração de casamento genérica como corações, flores desenhadas ou dourado ornamental.
+- **Don't** usar decoração de casamento genérica como corações, flores desenhadas ou dourado ornamental.

PRODUCT.md

@@ -14,42 +14,36 @@ web
 
 ## Product Purpose
 
-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.
+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.
 
-Sucesso no lançamento significa:
+Sucesso 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
 
-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.
+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.
 
 ## 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 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.
+- Jornada prevista: descoberta no site, briefing, 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.
-- 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.
-- 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.
-- 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.
+- Duas superfícies integradas: site público responsivo com CMS e área interna operacional em Filament.
+- 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.
+- Implementação atual cobre fundação, site público e CMS; módulos operacionais posteriores ainda fazem parte do escopo planejado.
 - 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.

README.md

@@ -138,10 +138,10 @@ Após `php artisan db:seed`:
 - [docs/adr/](docs/adr/) — ADRs aceitas
 - [docs/conventions/php-strict-types.md](docs/conventions/php-strict-types.md) — convenção de strict types
 - [docs/operations/atualizacao-de-conteudo.md](docs/operations/atualizacao-de-conteudo.md) — runbook de atualização de conteúdo do site pelo painel admin
-- [docs/deployment/dokploy.md](docs/deployment/dokploy.md) — deploy staging/produção no Dokploy + registry Gitea
+- [docs/deployment/dokploy.md](docs/deployment/dokploy.md) — deploy staging/produção no Dokploy + GHCR
 
 ## Deploy (Dokploy)
 
-Staging publica automaticamente após CI verde em `main` (imagem no registry Gitea por SHA + alias `:staging`). Produção promove a **mesma digest** com workflow manual `Promote production` (sem rebuild).
+Staging publica automaticamente após CI verde em `main` (imagem GHCR por SHA + alias `:staging`). Produção promove a **mesma digest** com workflow manual `Promote production` (sem rebuild).
 
 Ver runbook completo: [docs/deployment/dokploy.md](docs/deployment/dokploy.md).

SPEC.md

@@ -2073,7 +2073,7 @@ quality        → Pint check + PHPStan/Larastan + audits + testes
 ### 14.3 Branches e ambientes
 
 - PR: testes e preview opcional;
-- `main`: build imutável por SHA publicado no registry Gitea (`git.hellomanoel.com`) e deploy automático em staging via Dokploy;
+- `main`: build imutável por SHA publicado no GHCR e deploy automático em staging via Dokploy;
 - staging: Dokploy Compose executa migração, healthcheck `/up` e smoke pós-deploy (`/up`, `/`, `/admin/login`);
 - produção: promoção da mesma imagem aprovada, sem rebuild (retag do digest em `:production`);
 - produção requer aprovação humana explícita no MVP (`workflow_dispatch` com confirmação);
@@ -2487,7 +2487,7 @@ Toda operação financeira deve:
 | ADR-011 | Cloudflare R2 (S3-compatible) como storage de objetos em produção | Aceita |
 | ADR-012 | E-mail transacional via Resend (mailer nativo Laravel) | Aceita |
 | ADR-013 | Design system Heritage Editorial para o site público | Aceita |
-| ADR-014 | Deploy via Dokploy Compose com imagem imutável por SHA no registry Gitea | Aceita |
+| ADR-014 | Deploy via Dokploy Compose com imagem imutável por SHA no GHCR | Aceita |
 | ADR-015 | Site público permanece Blade + JS vanilla; Livewire e Alpine ficam restritos ao Filament até o gatilho de §22. Emenda o texto da ADR-002 | Aceita |
 | ADR-016 | Lançamento de 31/08/2026 entrega apenas o site institucional (Fases 0–1); Fases 2–5 seguem especificadas e adiadas, sem data | Aceita |
 
@@ -2524,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, browser funcionais e arquitetura estão verdes;
+- testes unit, feature, visuais 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/AboutContent.php

@@ -1,20 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace App\Application\Data;
-
-use App\Models\PortfolioCase;
-use App\Models\SiteSetting;
-use Illuminate\Database\Eloquent\Collection;
-
-final readonly class AboutContent
-{
-    /**
-     * @param  Collection<int, PortfolioCase>  $featuredCases
-     */
-    public function __construct(
-        public SiteSetting $settings,
-        public Collection $featuredCases,
-    ) {}
-}

app/Application/Data/HomeContent.php

@@ -8,7 +8,6 @@ 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
@@ -17,13 +16,11 @@ 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/Data/PageMeta.php

@@ -6,7 +6,6 @@ namespace App\Application\Data;
 
 use App\Models\PortfolioCase;
 use App\Models\SiteSetting;
-use App\Models\WeddingPackage;
 use Illuminate\Support\Facades\Storage;
 
 final readonly class PageMeta
@@ -85,43 +84,6 @@ final readonly class PageMeta
         );
     }
 
-    /**
-     * @param  array<string, mixed>|null  $jsonLd
-     */
-    public static function forPackage(
-        WeddingPackage $package,
-        string $canonical,
-        SiteSetting $settings,
-        ?array $jsonLd = null,
-    ): self {
-        $title = filled($package->meta_title)
-            ? (string) $package->meta_title
-            : (filled($package->title_line) ? (string) $package->title_line : (string) $package->name);
-
-        $description = filled($package->meta_description)
-            ? (string) $package->meta_description
-            : (filled($package->summary) ? (string) $package->summary : self::defaultDescription($settings));
-
-        $ogImageUrl = filled($package->hero_image_path)
-            ? url(Storage::disk('public')->url((string) $package->hero_image_path))
-            : self::defaultOgImageUrl($settings);
-
-        $ogImageAlt = filled($package->hero_image_alt)
-            ? (string) $package->hero_image_alt
-            : $settings->default_og_image_alt;
-
-        return new self(
-            title: $title,
-            description: $description,
-            canonical: $canonical,
-            ogType: 'article',
-            ogImageUrl: $ogImageUrl,
-            ogImageAlt: $ogImageAlt,
-            jsonLd: $jsonLd,
-            siteName: (string) $settings->brand_name,
-        );
-    }
-
     /**
      * Build the metadata for branded error pages.
      *

app/Application/Queries/Marketing/FindPublishedWeddingPackageBySlug.php

@@ -1,18 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace App\Application\Queries\Marketing;
-
-use App\Models\WeddingPackage;
-
-final class FindPublishedWeddingPackageBySlug
-{
-    public function __invoke(string $slug): ?WeddingPackage
-    {
-        return WeddingPackage::query()
-            ->published()
-            ->where('slug', $slug)
-            ->first();
-    }
-}

app/Application/Queries/Marketing/GetAboutContent.php

@@ -1,25 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace App\Application\Queries\Marketing;
-
-use App\Application\Data\AboutContent;
-use App\Models\PortfolioCase;
-use App\Models\SiteSetting;
-
-final class GetAboutContent
-{
-    public function __invoke(): AboutContent
-    {
-        return new AboutContent(
-            settings: SiteSetting::instance(),
-            featuredCases: PortfolioCase::query()
-                ->published()
-                ->where('is_featured', true)
-                ->orderBy('sort_order')
-                ->limit(6)
-                ->get(),
-        );
-    }
-}

app/Application/Queries/Marketing/GetHomeContent.php

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

app/Application/Queries/Marketing/GetSitemapEntries.php

@@ -5,7 +5,6 @@ declare(strict_types=1);
 namespace App\Application\Queries\Marketing;
 
 use App\Models\PortfolioCase;
-use App\Models\WeddingPackage;
 use Illuminate\Support\Carbon;
 
 final class GetSitemapEntries
@@ -39,21 +38,6 @@ final class GetSitemapEntries
             ];
         }
 
-        $packages = WeddingPackage::query()
-            ->published()
-            ->orderBy('sort_order')
-            ->get(['slug', 'updated_at']);
-
-        foreach ($packages as $package) {
-            /** @var Carbon|null $updatedAt */
-            $updatedAt = $package->updated_at;
-
-            $entries[] = [
-                'loc' => route('packages.show', $package->slug),
-                'lastmod' => $updatedAt?->toAtomString(),
-            ];
-        }
-
         return $entries;
     }
 }

app/Console/Commands/MediaGenerateVariantsCommand.php

@@ -63,9 +63,6 @@ final class MediaGenerateVariantsCommand extends Command
         if ($settings && filled($settings->about_image_path)) {
             $paths[] = (string) $settings->about_image_path;
         }
-        if ($settings && filled($settings->founder_image_path)) {
-            $paths[] = (string) $settings->founder_image_path;
-        }
         if ($settings && filled($settings->hero_image_path)) {
             $paths[] = (string) $settings->hero_image_path;
         }

app/Domain/Marketing/PackageIconCatalog.php

@@ -1,49 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace App\Domain\Marketing;
-
-/**
- * Closed catalog of icon keys available for wedding modality detail
- * sections (benefits strip and included items).
- *
- * Keys are stable kebab-case identifiers rendered as inline SVGs by the
- * public Blade components. Admin selection is constrained to this catalog
- * so arbitrary SVG markup can never reach the public page.
- */
-final class PackageIconCatalog
-{
-    /**
-     * @return array<string, string> map of icon_key => pt-BR label
-     */
-    public static function labels(): array
-    {
-        return [
-            'calendar' => 'Calendário',
-            'checklist' => 'Checklist',
-            'users' => 'Casais',
-            'map' => 'Mapa e fornecedores',
-            'heart' => 'Cuidado',
-            'spark' => 'Detalhes',
-        ];
-    }
-
-    /**
-     * @return list<string>
-     */
-    public static function keys(): array
-    {
-        return array_keys(self::labels());
-    }
-
-    public static function isValid(string $iconKey): bool
-    {
-        return isset(self::labels()[$iconKey]);
-    }
-
-    public static function labelFor(string $iconKey): ?string
-    {
-        return self::labels()[$iconKey] ?? null;
-    }
-}

app/Filament/Pages/ManageSiteSettings.php

@@ -212,26 +212,6 @@ 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')
@@ -251,11 +231,6 @@ 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),
@@ -268,10 +243,8 @@ class ManageSiteSettings extends Page
                     ->columns(2),
                 Section::make('Página Sobre')
                     ->schema([
-                        PublicImageUploadRules::fileUpload('about_image_path', 'Imagem do hero / Sobre', 'content/about'),
+                        PublicImageUploadRules::fileUpload('about_image_path', 'Imagem da página Sobre', 'content/about'),
                         PublicImageUploadRules::altTextField('about_image_alt', 'about_image_path'),
-                        PublicImageUploadRules::fileUpload('founder_image_path', 'Foto da Michele', 'content/about/founder'),
-                        PublicImageUploadRules::altTextField('founder_image_alt', 'founder_image_path'),
                     ])
                     ->columns(2),
                 Section::make('SEO padrão')

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

@@ -1,13 +0,0 @@
-<?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

@@ -1,13 +0,0 @@
-<?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

@@ -1,21 +0,0 @@
-<?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

@@ -1,193 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace App\Filament\Resources\WeddingPackages\Schemas;
-
-use App\Domain\Marketing\PackageIconCatalog;
-use App\Support\PublicImageUploadRules;
-use Filament\Forms\Components\DateTimePicker;
-use Filament\Forms\Components\Repeater;
-use Filament\Forms\Components\Select;
-use Filament\Forms\Components\Textarea;
-use Filament\Forms\Components\TextInput;
-use Filament\Schemas\Components\Section;
-use Filament\Schemas\Schema;
-
-class WeddingPackageForm
-{
-    public static function configure(Schema $schema): Schema
-    {
-        return $schema
-            ->components([
-                Section::make('Identificação')
-                    ->schema([
-                        TextInput::make('name')
-                            ->label('Nome da modalidade')
-                            ->required()
-                            ->maxLength(255)
-                            ->live(onBlur: true)
-                            ->afterStateUpdated(function (?string $state, callable $set, callable $get): void {
-                                if (blank($get('slug'))) {
-                                    $set('slug', str($state)->slug()->toString());
-                                }
-                            }),
-                        TextInput::make('slug')
-                            ->label('Slug')
-                            ->required()
-                            ->maxLength(255)
-                            ->unique(ignoreRecord: true),
-                        TextInput::make('level')
-                            ->label('Número / tipo (ex.: 01 / COMPLETA)')
-                            ->required()
-                            ->maxLength(255),
-                        TextInput::make('tag')
-                            ->label('Etiqueta curta (ex.: Assessoria completa)')
-                            ->maxLength(255),
-                        TextInput::make('subtitle')
-                            ->label('Frase de apoio')
-                            ->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('compare_heading')
-                            ->label('Comparação — título (leitura rápida)')
-                            ->maxLength(255),
-                        TextInput::make('compare_summary')
-                            ->label('Comparação — resumo (leitura rápida)')
-                            ->maxLength(255),
-                        TextInput::make('sort_order')
-                            ->label('Ordem')
-                            ->numeric()
-                            ->default(0)
-                            ->required(),
-                        DateTimePicker::make('published_at')
-                            ->label('Publicado em')
-                            ->seconds(false),
-                    ])
-                    ->columns(2),
-                Section::make('Hero da página')
-                    ->description('Dados de abertura da página da modalidade.')
-                    ->schema([
-                        TextInput::make('eyebrow')
-                            ->label('Eyebrow (ex.: Assessoria)')
-                            ->maxLength(255),
-                        TextInput::make('title_line')
-                            ->label('Título (linha principal)')
-                            ->maxLength(255),
-                        TextInput::make('title_emphasis')
-                            ->label('Título (ênfase em itálico)')
-                            ->maxLength(255),
-                        Textarea::make('hero_lead')
-                            ->label('Texto de abertura')
-                            ->rows(3),
-                        PublicImageUploadRules::fileUpload('hero_image_path', 'Imagem do hero'),
-                        PublicImageUploadRules::altTextField('hero_image_alt', 'hero_image_path'),
-                    ])
-                    ->columns(2),
-                Section::make('Diferenciais')
-                    ->description('Faixa escura com os valores da modalidade.')
-                    ->schema([
-                        Repeater::make('benefits')
-                            ->label('Diferenciais')
-                            ->schema([
-                                Select::make('icon_key')
-                                    ->label('Ícone')
-                                    ->options(PackageIconCatalog::labels())
-                                    ->required(),
-                                TextInput::make('label')
-                                    ->label('Rótulo')
-                                    ->required()
-                                    ->maxLength(255),
-                            ])
-                            ->defaultItems(4)
-                            ->minItems(1)
-                            ->addActionLabel('Adicionar diferencial'),
-                    ])
-                    ->columns(1),
-                Section::make('O que está incluso')
-                    ->schema([
-                        Repeater::make('included_items')
-                            ->label('Itens inclusos')
-                            ->schema([
-                                Select::make('icon_key')
-                                    ->label('Ícone')
-                                    ->options(PackageIconCatalog::labels())
-                                    ->required(),
-                                TextInput::make('title')
-                                    ->label('Título')
-                                    ->required()
-                                    ->maxLength(255),
-                                Textarea::make('description')
-                                    ->label('Descrição')
-                                    ->rows(2)
-                                    ->maxLength(500),
-                            ])
-                            ->defaultItems(6)
-                            ->minItems(1)
-                            ->addActionLabel('Adicionar item'),
-                    ])
-                    ->columns(1),
-                Section::make('Para quem é este pacote')
-                    ->schema([
-                        TextInput::make('audience_heading')
-                            ->label('Título da seção')
-                            ->maxLength(255),
-                        Textarea::make('audience_intro')
-                            ->label('Texto de introdução')
-                            ->rows(3),
-                        Repeater::make('audience_points')
-                            ->label('Público')
-                            ->schema([
-                                TextInput::make('point')
-                                    ->label('Ponto')
-                                    ->required()
-                                    ->maxLength(255),
-                            ])
-                            ->defaultItems(4)
-                            ->minItems(1)
-                            ->addActionLabel('Adicionar ponto'),
-                        PublicImageUploadRules::fileUpload('audience_image_path', 'Imagem da seção'),
-                        PublicImageUploadRules::altTextField('audience_image_alt', 'audience_image_path'),
-                    ])
-                    ->columns(2),
-                Section::make('CTA final')
-                    ->schema([
-                        TextInput::make('final_cta_heading')
-                            ->label('Título do CTA final')
-                            ->maxLength(255),
-                        Textarea::make('final_cta_body')
-                            ->label('Texto do CTA final')
-                            ->rows(3),
-                    ])
-                    ->columns(2),
-                Section::make('SEO')
-                    ->schema([
-                        TextInput::make('meta_title')
-                            ->label('Meta title')
-                            ->maxLength(255),
-                        Textarea::make('meta_description')
-                            ->label('Meta description')
-                            ->rows(3),
-                    ])
-                    ->columns(2),
-            ]);
-    }
-}

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

@@ -1,53 +0,0 @@
-<?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('slug')
-                    ->label('Slug')
-                    ->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

@@ -1,62 +0,0 @@
-<?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('briefing')->with('status', 'briefing-sent');
+        return redirect()->route('contact')->with('status', 'briefing-sent');
     }
 }

app/Http/Controllers/PublicSite/PackageController.php

@@ -1,46 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace App\Http\Controllers\PublicSite;
-
-use App\Application\Data\PageMeta;
-use App\Application\Queries\Marketing\FindPublishedWeddingPackageBySlug;
-use App\Http\Controllers\Controller;
-use App\Models\SiteSetting;
-use Illuminate\Contracts\View\View;
-use Illuminate\Http\Response;
-
-final class PackageController extends Controller
-{
-    public function show(string $slug, FindPublishedWeddingPackageBySlug $findPublishedWeddingPackageBySlug): View|Response
-    {
-        $package = $findPublishedWeddingPackageBySlug($slug);
-
-        if ($package === null) {
-            abort(404);
-        }
-
-        $settings = SiteSetting::instance();
-        $canonical = route('packages.show', $package->slug);
-
-        return view('pages.packages.show', [
-            'package' => $package,
-            'siteSettings' => $settings,
-            'pageMeta' => PageMeta::forPackage(
-                package: $package,
-                canonical: $canonical,
-                settings: $settings,
-                jsonLd: [
-                    '@context' => 'https://schema.org',
-                    '@type' => 'Article',
-                    'headline' => $package->name,
-                    'description' => $package->summary,
-                    'url' => $canonical,
-                    'datePublished' => $package->published_at?->toAtomString(),
-                    'dateModified' => $package->updated_at?->toAtomString(),
-                ],
-            ),
-        ]);
-    }
-}

app/Http/Controllers/PublicSite/PageController.php

@@ -5,20 +5,17 @@ declare(strict_types=1);
 namespace App\Http\Controllers\PublicSite;
 
 use App\Application\Data\PageMeta;
-use App\Application\Queries\Marketing\GetAboutContent;
 use App\Http\Controllers\Controller;
 use App\Models\SiteSetting;
 use Illuminate\Contracts\View\View;
 
 final class PageController extends Controller
 {
-    public function about(GetAboutContent $getAboutContent): View
+    public function about(): View
     {
-        $content = $getAboutContent();
-        $settings = $content->settings;
+        $settings = SiteSetting::instance();
 
         return view('pages.about', [
-            'content' => $content,
             'siteSettings' => $settings,
             'pageMeta' => PageMeta::forPage(
                 canonical: route('about'),
@@ -48,7 +45,7 @@ final class PageController extends Controller
     {
         $settings = SiteSetting::instance();
 
-        return view('pages.partners', [
+        return view('pages.contact', [
             'siteSettings' => $settings,
             'pageMeta' => PageMeta::forPage(
                 canonical: route('contact'),
@@ -58,14 +55,4 @@ 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

@@ -1,66 +0,0 @@
-<?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,7 +8,6 @@ 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
@@ -20,7 +19,6 @@ 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

@@ -1,32 +0,0 @@
-<?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

@@ -1,31 +0,0 @@
-<?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,15 +12,12 @@ 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 $founder_image_path
- * @property string|null $founder_image_alt
  * @property string|null $hero_image_path
  * @property string|null $hero_image_alt
  * @property string|null $services_hero_image_path
@@ -49,18 +46,14 @@ use Illuminate\Database\Eloquent\Model;
     'about_summary',
     'about_image_path',
     'about_image_alt',
-    'founder_image_path',
-    'founder_image_alt',
     'manifesto_title',
     'manifesto_lead',
     'manifesto_body',
     'method_intro',
     'method_steps',
-    'corporate_steps',
     'principles',
     'email',
     'phone',
-    'whatsapp_number',
     'city',
     'social_links',
     'default_meta_title',
@@ -89,11 +82,9 @@ 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',
@@ -127,27 +118,6 @@ 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>
      */
@@ -169,7 +139,6 @@ class SiteSetting extends Model
         return [
             'social_links' => 'array',
             'method_steps' => 'array',
-            'corporate_steps' => 'array',
             'principles' => 'array',
             'analytics_enabled' => 'boolean',
         ];

app/Models/WeddingPackage.php

@@ -1,108 +0,0 @@
-<?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;
-use Illuminate\Support\Str;
-
-/**
- * @property string $name
- * @property string|null $slug
- * @property string $level
- * @property string|null $tag
- * @property string|null $subtitle
- * @property string $summary
- * @property list<string> $scope_items
- * @property string $cta_label
- * @property string|null $compare_heading
- * @property string|null $compare_summary
- * @property string|null $eyebrow
- * @property string|null $title_line
- * @property string|null $title_emphasis
- * @property string|null $hero_lead
- * @property string|null $hero_image_path
- * @property string|null $hero_image_alt
- * @property list<array{icon_key: string, label: string}>|null $benefits
- * @property list<array{icon_key: string, title: string, description: string}>|null $included_items
- * @property string|null $audience_heading
- * @property string|null $audience_intro
- * @property list<string>|null $audience_points
- * @property string|null $audience_image_path
- * @property string|null $audience_image_alt
- * @property string|null $final_cta_heading
- * @property string|null $final_cta_body
- * @property string|null $meta_title
- * @property string|null $meta_description
- * @property int $sort_order
- * @property Carbon|null $published_at
- */
-#[Fillable([
-    'name',
-    'slug',
-    'level',
-    'tag',
-    'subtitle',
-    'summary',
-    'scope_items',
-    'cta_label',
-    'compare_heading',
-    'compare_summary',
-    'sort_order',
-    'published_at',
-    'eyebrow',
-    'title_line',
-    'title_emphasis',
-    'hero_lead',
-    'hero_image_path',
-    'hero_image_alt',
-    'benefits',
-    'included_items',
-    'audience_heading',
-    'audience_intro',
-    'audience_points',
-    'audience_image_path',
-    'audience_image_alt',
-    'final_cta_heading',
-    'final_cta_body',
-    'meta_title',
-    'meta_description',
-])]
-#[UsePolicy(WeddingPackagePolicy::class)]
-class WeddingPackage extends Model
-{
-    /** @use HasFactory<WeddingPackageFactory> */
-    use HasFactory;
-
-    use HasPublication;
-
-    protected static function booted(): void
-    {
-        static::saving(function (WeddingPackage $weddingPackage): void {
-            if (blank($weddingPackage->slug) && filled($weddingPackage->name)) {
-                $weddingPackage->slug = Str::slug($weddingPackage->name);
-            }
-        });
-    }
-
-    /** @return array<string, string|class-string> */
-    protected function casts(): array
-    {
-        return [
-            'scope_items' => 'array',
-            'benefits' => 'array',
-            'included_items' => 'array',
-            'audience_points' => 'array',
-            'sort_order' => 'integer',
-            'published_at' => 'datetime',
-        ];
-    }
-}

app/Policies/WeddingPackagePolicy.php

@@ -1,36 +0,0 @@
-<?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,10 +72,6 @@ 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/PackageContactLink.php

@@ -1,28 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace App\Support;
-
-use App\Models\SiteSetting;
-
-final class PackageContactLink
-{
-    /**
-     * Resolve the contextual contact link for a wedding package modality.
-     *
-     * @return array{href: string, isWhatsapp: bool}
-     */
-    public static function for(SiteSetting $settings, string $packageName): array
-    {
-        $digits = preg_replace('/\D/', '', (string) $settings->whatsapp_number);
-        $isWhatsapp = strlen($digits) >= 10;
-
-        return [
-            'href' => $isWhatsapp
-                ? 'https://wa.me/'.$digits.'?text='.rawurlencode('Olá, gostaria de conversar sobre a modalidade '.$packageName.' para meu casamento.')
-                : route('briefing', ['servico_interesse' => $packageName]),
-            'isWhatsapp' => $isWhatsapp,
-        ];
-    }
-}

database/factories/WeddingPackageFactory.php

@@ -1,56 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-namespace Database\Factories;
-
-use App\Models\WeddingPackage;
-use Illuminate\Database\Eloquent\Factories\Factory;
-use Illuminate\Support\Str;
-
-/** @extends Factory<WeddingPackage> */
-class WeddingPackageFactory extends Factory
-{
-    protected $model = WeddingPackage::class;
-
-    /** @return array<string, mixed> */
-    public function definition(): array
-    {
-        $name = fake()->unique()->words(2, true);
-
-        return [
-            'name' => $name,
-            'slug' => Str::slug($name),
-            'level' => 'Assessoria',
-            'tag' => fake()->words(2, true),
-            'subtitle' => fake()->sentence(),
-            'summary' => fake()->sentence(),
-            'scope_items' => [fake()->sentence()],
-            'cta_label' => 'Conversar sobre esta modalidade',
-            'compare_heading' => fake()->words(3, true),
-            'compare_summary' => fake()->sentence(),
-            'sort_order' => 0,
-            'published_at' => null,
-            'eyebrow' => 'Assessoria',
-            'title_line' => fake()->words(2, true),
-            'title_emphasis' => fake()->word(),
-            'hero_lead' => fake()->paragraph(),
-            'benefits' => [
-                ['icon_key' => 'checklist', 'label' => fake()->word()],
-            ],
-            'included_items' => [
-                ['icon_key' => 'checklist', 'title' => fake()->word(), 'description' => fake()->sentence()],
-            ],
-            'audience_heading' => 'Para quem é este pacote',
-            'audience_intro' => fake()->paragraph(),
-            'audience_points' => [fake()->sentence()],
-            'final_cta_heading' => 'Vamos conversar?',
-            'final_cta_body' => fake()->paragraph(),
-        ];
-    }
-
-    public function published(): static
-    {
-        return $this->state(fn (): array => ['published_at' => now()]);
-    }
-}

database/migrations/2026_08_11_010000_add_corporate_steps_to_site_settings_table.php

@@ -1,24 +0,0 @@
-<?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

@@ -1,24 +0,0 @@
-<?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

@@ -1,30 +0,0 @@
-<?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/migrations/2026_08_12_000000_add_founder_image_to_site_settings_table.php

@@ -1,25 +0,0 @@
-<?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('founder_image_path')->nullable()->after('about_image_alt');
-            $table->string('founder_image_alt')->nullable()->after('founder_image_path');
-        });
-    }
-
-    public function down(): void
-    {
-        Schema::table('site_settings', function (Blueprint $table): void {
-            $table->dropColumn(['founder_image_path', 'founder_image_alt']);
-        });
-    }
-};

database/migrations/2026_08_12_100000_add_preview_fields_to_wedding_packages_table.php

@@ -1,27 +0,0 @@
-<?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('wedding_packages', function (Blueprint $table): void {
-            $table->string('tag')->nullable();
-            $table->string('subtitle')->nullable();
-            $table->string('compare_heading')->nullable();
-            $table->string('compare_summary')->nullable();
-        });
-    }
-
-    public function down(): void
-    {
-        Schema::table('wedding_packages', function (Blueprint $table): void {
-            $table->dropColumn(['tag', 'subtitle', 'compare_heading', 'compare_summary']);
-        });
-    }
-};

database/migrations/2026_08_12_120000_extend_wedding_packages_for_detail_pages.php

@@ -1,83 +0,0 @@
-<?php
-
-declare(strict_types=1);
-
-use Illuminate\Database\Migrations\Migration;
-use Illuminate\Database\Schema\Blueprint;
-use Illuminate\Support\Facades\DB;
-use Illuminate\Support\Facades\Schema;
-use Illuminate\Support\Str;
-
-return new class extends Migration
-{
-    public function up(): void
-    {
-        Schema::table('wedding_packages', function (Blueprint $table): void {
-            $table->string('slug')->nullable()->unique()->after('name');
-            $table->string('eyebrow')->nullable()->after('level');
-            $table->string('title_line')->nullable()->after('eyebrow');
-            $table->string('title_emphasis')->nullable()->after('title_line');
-            $table->text('hero_lead')->nullable()->after('title_emphasis');
-            $table->string('hero_image_path')->nullable()->after('hero_lead');
-            $table->string('hero_image_alt')->nullable()->after('hero_image_path');
-            $table->jsonb('benefits')->nullable()->after('hero_image_alt');
-            $table->jsonb('included_items')->nullable()->after('benefits');
-            $table->string('audience_heading')->nullable()->after('included_items');
-            $table->text('audience_intro')->nullable()->after('audience_heading');
-            $table->jsonb('audience_points')->nullable()->after('audience_intro');
-            $table->string('audience_image_path')->nullable()->after('audience_points');
-            $table->string('audience_image_alt')->nullable()->after('audience_image_path');
-            $table->string('final_cta_heading')->nullable()->after('audience_image_alt');
-            $table->text('final_cta_body')->nullable()->after('final_cta_heading');
-            $table->string('meta_title')->nullable()->after('final_cta_body');
-            $table->text('meta_description')->nullable()->after('meta_title');
-        });
-
-        $this->backfillSlugs();
-    }
-
-    public function down(): void
-    {
-        Schema::table('wedding_packages', function (Blueprint $table): void {
-            $table->dropUnique(['slug']);
-            $table->dropColumn([
-                'slug',
-                'eyebrow',
-                'title_line',
-                'title_emphasis',
-                'hero_lead',
-                'hero_image_path',
-                'hero_image_alt',
-                'benefits',
-                'included_items',
-                'audience_heading',
-                'audience_intro',
-                'audience_points',
-                'audience_image_path',
-                'audience_image_alt',
-                'final_cta_heading',
-                'final_cta_body',
-                'meta_title',
-                'meta_description',
-            ]);
-        });
-    }
-
-    private function backfillSlugs(): void
-    {
-        $rows = DB::table('wedding_packages')->whereNull('slug')->get(['id', 'name']);
-
-        foreach ($rows as $row) {
-            $slug = Str::slug($row->name);
-            $candidate = $slug;
-            $suffix = 2;
-
-            while (DB::table('wedding_packages')->where('slug', $candidate)->exists()) {
-                $candidate = "{$slug}-{$suffix}";
-                $suffix++;
-            }
-
-            DB::table('wedding_packages')->where('id', $row->id)->update(['slug' => $candidate]);
-        }
-    }
-};

database/seeders/ContentSeeder.php

@@ -49,7 +49,6 @@ class ContentSeeder extends Seeder
         $this->seedServices();
         $this->seedPortfolioCases();
         $this->call(TestimonialsSeeder::class);
-        $this->call(WeddingPackagesSeeder::class);
     }
 
     private function seedSiteSettings(): void
@@ -71,14 +70,11 @@ class ContentSeeder extends Seeder
             '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',
-            'founder_image_path' => $this->copyFixture('about-image.jpg', 'content/about/founder/michele.jpg'),
-            'founder_image_alt' => 'Michele, da Amare',
             'manifesto_title' => 'Sofisticação que também se traduz em organização.',
             'manifesto_lead' => 'Um evento memorável não nasce apenas de uma boa estética. Ele depende de decisões bem conduzidas, fornecedores alinhados e atenção constante ao que realmente importa.',
             '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

@@ -30,7 +30,6 @@ class VisualContentSeeder extends Seeder
         $this->seedServices();
         $this->seedPortfolioCases();
         $this->seedTestimonials();
-        $this->call(WeddingPackagesSeeder::class);
     }
 
     private function seedSiteSettings(): void
@@ -52,14 +51,11 @@ class VisualContentSeeder extends Seeder
             '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',
-            'founder_image_path' => $this->writeSolidJpeg('visual/about/founder-michele.jpg', 900, 1200, [210, 205, 192]),
-            'founder_image_alt' => 'Michele, da Amare',
             'manifesto_title' => 'Sofisticação que também se traduz em organização.',
             'manifesto_lead' => 'Um evento memorável não nasce apenas de uma boa estética. Ele depende de decisões bem conduzidas, fornecedores alinhados e atenção constante ao que realmente importa.',
             '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',
@@ -202,22 +198,16 @@ 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, 80);
+        imagejpeg($image, null, 90);
         $binary = (string) ob_get_clean();
         imagedestroy($image);
 
-        $disk->put($destination, $binary);
+        Storage::disk('public')->put($destination, $binary);
 
         return $destination;
     }

database/seeders/WeddingPackagesSeeder.php

@@ -1,175 +0,0 @@
-<?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)
- * and the services page. Copy is approved from the structural model preview
- * (preview(2).html) and remains editable via the Filament resource. Detail
- * copy follows the complete-assessoria preview
- * (amare-assessoria-completa.html) adapted to each modality.
- */
-class WeddingPackagesSeeder extends Seeder
-{
-    private const PUBLISHED_AT = '2026-08-11 00:00:00';
-
-    public function run(): void
-    {
-        $packages = [
-            [
-                'name' => 'Essenza',
-                'slug' => 'essenza',
-                'level' => '01 / COMPLETA',
-                'tag' => 'Assessoria completa',
-                'subtitle' => 'Do planejamento ao grande dia.',
-                'summary' => 'Para casais que desejam contar com a Amare desde o início ou ainda estão estruturando etapas importantes.',
-                'scope_items' => [
-                    'Estruturação do planejamento',
-                    'Cronogramas, prazos e prioridades',
-                    'Orientação e gestão de fornecedores',
-                    'Alinhamento entre os envolvidos',
-                    'Coordenação da execução',
-                ],
-                'cta_label' => 'Quero conhecer a Essenza',
-                'compare_heading' => 'Começar com a Amare',
-                'compare_summary' => 'Acompanhamento mais amplo ao longo do planejamento.',
-                'sort_order' => 1,
-                'eyebrow' => 'Assessoria',
-                'title_line' => 'Assessoria',
-                'title_emphasis' => 'Completa',
-                'hero_lead' => 'Do planejamento ao grande dia, com calma, precisão e cuidado.',
-                'benefits' => [
-                    ['icon_key' => 'calendar', 'label' => 'Organização integral'],
-                    ['icon_key' => 'checklist', 'label' => 'Planejamento personalizado'],
-                    ['icon_key' => 'users', 'label' => 'Fornecedores selecionados'],
-                    ['icon_key' => 'heart', 'label' => 'Experiência leve e inesquecível'],
-                ],
-                'included_items' => [
-                    ['icon_key' => 'heart', 'title' => 'Escuta e briefing', 'description' => 'Cada casal é único; começamos por ouvir.'],
-                    ['icon_key' => 'checklist', 'title' => 'Planejamento completo', 'description' => 'Cada etapa mapeada com clareza.'],
-                    ['icon_key' => 'map', 'title' => 'Gestão de fornecedores', 'description' => 'Contatos e prazos sob cuidado.'],
-                    ['icon_key' => 'calendar', 'title' => 'Acompanhamento contínuo', 'description' => 'Perto do casal em cada decisão.'],
-                    ['icon_key' => 'spark', 'title' => 'Produção e logística', 'description' => 'Dia a dia do evento organizado nos detalhes.'],
-                    ['icon_key' => 'users', 'title' => 'Dia do evento', 'description' => 'Coordenação total para o casal viver o momento.'],
-                ],
-                'audience_heading' => 'Para quem é este pacote',
-                'audience_intro' => 'Para quem quer uma assessoria completa, do início ao fim.',
-                'audience_points' => [
-                    'Casamentos',
-                    'Aniversários',
-                    'Eventos sociais e celebrações',
-                    'Eventos corporativos',
-                ],
-                'final_cta_heading' => 'Pronta para começar?',
-                'final_cta_body' => 'Conte seu evento para a Amare e receba uma proposta.',
-            ],
-            [
-                'name' => 'Conduzione',
-                'slug' => 'conduzione',
-                'level' => '02 / PARCIAL',
-                'tag' => 'Assessoria parcial',
-                'subtitle' => 'Para quem já começou e quer seguir acompanhado.',
-                'summary' => 'Para casais que já tomaram decisões e contrataram parte dos fornecedores, mas precisam estruturar o que falta.',
-                'scope_items' => [
-                    'Diagnóstico do planejamento existente',
-                    'Organização das pendências',
-                    'Gestão dos fornecedores contratados',
-                    'Orientação para próximas decisões',
-                    'Coordenação da execução',
-                ],
-                'cta_label' => 'Quero conhecer a Conduzione',
-                'compare_heading' => 'Trazer a Amare para o caminho',
-                'compare_summary' => 'O planejamento existe, mas ainda há decisões e gestão pela frente.',
-                'sort_order' => 2,
-                'eyebrow' => 'Assessoria',
-                'title_line' => 'Assessoria',
-                'title_emphasis' => 'Parcial',
-                'hero_lead' => 'Para retomar o planejamento, organizar o que falta e seguir com acompanhamento profissional.',
-                'benefits' => [
-                    ['icon_key' => 'checklist', 'label' => 'Diagnóstico completo'],
-                    ['icon_key' => 'calendar', 'label' => 'Organização integral'],
-                    ['icon_key' => 'users', 'label' => 'Fornecedores selecionados'],
-                    ['icon_key' => 'heart', 'label' => 'Experiência leve e inesquecível'],
-                ],
-                'included_items' => [
-                    ['icon_key' => 'checklist', 'title' => 'Diagnóstico do planejamento', 'description' => 'Um olhar profissional sobre o que já existe.'],
-                    ['icon_key' => 'calendar', 'title' => 'Organização das pendências', 'description' => 'Prioridades claras, etapa a etapa.'],
-                    ['icon_key' => 'map', 'title' => 'Gestão de fornecedores', 'description' => 'Contatos e prazos sob cuidado.'],
-                    ['icon_key' => 'spark', 'title' => 'Gestão dos próximos passos', 'description' => 'Um plano para chegar tranquilo ao grande dia.'],
-                    ['icon_key' => 'users', 'title' => 'Acompanhamento contínuo', 'description' => 'Perto do casal em cada decisão.'],
-                    ['icon_key' => 'heart', 'title' => 'Dia do evento', 'description' => 'Coordenação total para o casal viver o momento.'],
-                ],
-                'audience_heading' => 'Para quem é este pacote',
-                'audience_intro' => 'Para quem já começou a planejar e quer retomar as rédeas com acompanhamento profissional.',
-                'audience_points' => [
-                    'Casamentos em andamento',
-                    'Casais com pouco tempo disponível',
-                    'Quem precisa priorizar pendências',
-                    'Quem busca fornecedores confiáveis',
-                ],
-                'final_cta_heading' => 'Pronta para retomar?',
-                'final_cta_body' => 'Conte onde seu planejamento está e receba uma proposta.',
-            ],
-            [
-                'name' => 'Grand Jour',
-                'slug' => 'grand-jour',
-                'level' => '03 / FINAL',
-                'tag' => 'Assessoria final',
-                'subtitle' => 'O planejamento está pronto. Agora é hora de viver.',
-                'summary' => 'Para casais na reta final que precisam de uma equipe para assumir alinhamentos, cronograma e operação.',
-                'scope_items' => [
-                    'Imersão no planejamento existente',
-                    'Conferência das informações',
-                    'Alinhamento dos fornecedores',
-                    'Organização do cronograma final',
-                    'Gestão da operação do evento',
-                ],
-                'cta_label' => 'Quero conhecer a Grand Jour',
-                'compare_heading' => 'Entregar a operação para a Amare',
-                'compare_summary' => 'O projeto está pronto e o foco passa a ser alinhamento e execução.',
-                'sort_order' => 3,
-                'eyebrow' => 'Assessoria',
-                'title_line' => 'Assessoria',
-                'title_emphasis' => 'Final',
-                'hero_lead' => 'Para assumir os alinhamentos e a operação quando o grande dia está próximo.',
-                'benefits' => [
-                    ['icon_key' => 'checklist', 'label' => 'Imersão no que já existe'],
-                    ['icon_key' => 'users', 'label' => 'Alinhamento de fornecedores'],
-                    ['icon_key' => 'calendar', 'label' => 'Cronograma final'],
-                    ['icon_key' => 'heart', 'label' => 'Operação com leveza'],
-                ],
-                'included_items' => [
-                    ['icon_key' => 'checklist', 'title' => 'Imersão no planejamento', 'description' => 'Entendemos cada decisão já tomada.'],
-                    ['icon_key' => 'map', 'title' => 'Alinhamento de fornecedores', 'description' => 'Contatos e prazos sob cuidado.'],
-                    ['icon_key' => 'calendar', 'title' => 'Cronograma final', 'description' => 'Cada etapa posicionada na reta final.'],
-                    ['icon_key' => 'spark', 'title' => 'Ensaios e detalhes', 'description' => 'Produção e logística nos detalhes.'],
-                    ['icon_key' => 'users', 'title' => 'Operação do evento', 'description' => 'Gestão da equipe e do dia a dia.'],
-                    ['icon_key' => 'heart', 'title' => 'Dia do evento', 'description' => 'Coordenação total para o casal viver o momento.'],
-                ],
-                'audience_heading' => 'Para quem é este pacote',
-                'audience_intro' => 'Para casais já planejados que querem chegar ao grande dia com equipe e operação no lugar.',
-                'audience_points' => [
-                    'Casamentos já planejados',
-                    'Casais na reta final',
-                    'Quem precisa de operação no dia',
-                    'Quem quer viver o momento com leveza',
-                ],
-                'final_cta_heading' => 'Pronta para o grande dia?',
-                'final_cta_body' => 'Conte a data do seu evento e receba uma proposta.',
-            ],
-        ];
-
-        foreach ($packages as $package) {
-            WeddingPackage::query()->updateOrCreate(
-                ['name' => $package['name']],
-                [...$package, 'published_at' => Carbon::parse(self::PUBLISHED_AT)],
-            );
-        }
-    }
-}

docker-compose.deploy.yml

@@ -1,6 +1,6 @@
 # Shared Compose for Dokploy staging and production.
 # Both stacks use the same file with different env:
-#   APP_IMAGE=git.hellomanoel.com/manoel-freitas/amare
+#   APP_IMAGE=ghcr.io/<owner>/<repo>
 #   IMAGE_TAG=staging|production|<git-sha>
 # PostgreSQL is a separate Dokploy database service (not defined here).
 # Traefik/Dokploy domains should target service `web` port 8000.

docs/deployment/dokploy.md

@@ -1,11 +1,11 @@
 # Deploy Dokploy (staging → production)
 
-Runbook for operating Amare on a VPS with Dokploy connected to Gitea (git.hellomanoel.com), publishing immutable images to Gitea's container registry.
+Runbook for operating Amare on a VPS with Dokploy connected to GitHub, publishing immutable images to GHCR.
 
 ## Architecture
 
 ```
-CI (main) → build FrankenPHP image → git.hellomanoel.com registry :<sha> + :staging
+CI (main) → build FrankenPHP image → GHCR :<sha> + :staging
          → Dokploy staging compose.deploy
          → smoke /up / /admin/login
 
@@ -18,7 +18,7 @@ Promote (manual) → retag same digest as :production (no rebuild)
 |---|---|
 | Compose file | [`docker-compose.deploy.yml`](../../docker-compose.deploy.yml) |
 | Processes | `migrate` (one-shot) → `web` / `queue` / `scheduler` |
-| Image | `git.hellomanoel.com/manoel-freitas/amare:<sha>` (+ aliases `:staging`, `:production`) |
+| Image | `ghcr.io/<owner>/<repo>:<sha>` (+ aliases `:staging`, `:production`) |
 | Database | Dokploy PostgreSQL **per environment** (not in the app image) |
 | Media | Cloudflare R2 (`FILESYSTEM_DISK=r2`), separate buckets per environment |
 | Mail | Resend (`MAIL_MAILER=resend`) |
@@ -26,14 +26,11 @@ Promote (manual) → retag same digest as :production (no rebuild)
 
 ## Prerequisites (manual)
 
-1. Gitea repository `manoel-freitas/amare` at `https://git.hellomanoel.com`; **Repository Actions enabled** in repo settings; a registered **Gitea Actions runner** (see [docs.gitea.com usage/actions/quickstart](https://docs.gitea.com/usage/actions/quickstart)) with an `ubuntu-latest` label.
-2. Dokploy installed on the VPS.
-3. Container registry in Dokploy (`git.hellomanoel.com`) with a PAT that can **read** packages (`read:package`). Prefer a dedicated bot/token; do not store write tokens on the VPS. The **write** PAT (`write:package`) lives only in Gitea repo secrets for the pipeline.
-4. Two PostgreSQL services in Dokploy (staging + production), private (no public port).
-5. Two R2 buckets (or prefixes) and Resend credentials for each environment as needed.
-6. Domains (or temporary Dokploy/traefik.me hosts) pointing at the VPS with TLS.
-
-Note: Gitea's `GITEA_TOKEN` cannot push OCI packages ([gitea#23642](https://github.com/go-gitea/gitea/issues/23642)); registry authentication in the workflows uses a PAT (`REGISTRY_PAT`), not the token. Secret names must not use the reserved `GITEA_` prefix (Gitea rejects them as invalid).
+1. Dokploy installed on the VPS; GitHub provider connected.
+2. GHCR registry in Dokploy (`ghcr.io`) with a PAT that can **read** packages (`read:packages`). Prefer a dedicated bot/token; do not store write tokens on the VPS.
+3. Two PostgreSQL services in Dokploy (staging + production), private (no public port).
+4. Two R2 buckets (or prefixes) and Resend credentials for each environment as needed.
+5. Domains (or temporary Dokploy/traefik.me hosts) pointing at the VPS with TLS.
 
 ## Create Compose stacks
 
@@ -47,7 +44,7 @@ Create **two** Dokploy Compose services (same repo, same compose path):
 Dokploy Environment for each stack must set:
 
 ```bash
-APP_IMAGE=git.hellomanoel.com/manoel-freitas/amare
+APP_IMAGE=ghcr.io/<owner>/<repo>
 IMAGE_TAG=staging   # or production
 ```
 
@@ -55,11 +52,11 @@ Point Dokploy domain(s) at service **`web`**, port **`8000`**. Do not publish Po
 
 Compose services must join the external Docker network `dokploy-network` (declared in `docker-compose.deploy.yml`) so they can resolve the Dokploy-managed Postgres internal host (e.g. `amare-stg-pez43e`). Set `DB_HOST` to that **Internal Host** from the Dokploy database UI — not a public hostname.
 
-Source can be Gitea (so Dokploy clones the compose file) or Raw paste of `docker-compose.deploy.yml`. Prefer Gitea + fixed compose path so updates stay in sync with `main`.
+Source can be GitHub (so Dokploy clones the compose file) or Raw paste of `docker-compose.deploy.yml`. Prefer GitHub + fixed compose path so updates stay in sync with `main`.
 
 ## Required Laravel env (Dokploy only)
 
-Set these in Dokploy Environment UI (written to `.env` next to the compose file). **Never** put them in Gitea Actions secrets or image layers.
+Set these in Dokploy Environment UI (written to `.env` next to the compose file). **Never** put them in GitHub Actions secrets or image layers.
 
 ```env
 APP_NAME=Amare
@@ -123,9 +120,9 @@ Upload path does not need R2 CORS with the local temp-disk default. Still useful
 
 Also enable public access / custom domain for `R2_URL` so `<img>` URLs work after save.
 
-## Gitea Actions secrets
+## GitHub Actions secrets
 
-Repository secrets (Gitea → Settings → Actions → Secrets) used by workflows:
+Repository secrets used by workflows:
 
 | Secret | Purpose |
 |---|---|
@@ -135,48 +132,32 @@ Repository secrets (Gitea → Settings → Actions → Secrets) used by workflow
 | `DOKPLOY_PRODUCTION_COMPOSE_ID` | Production **Compose** service id (not an Application id) |
 | `STAGING_URL` | Public origin for staging smoke (e.g. `https://staging.example.com`) |
 | `PRODUCTION_URL` | Public origin for production smoke |
-| `REGISTRY_PAT` | Personal Access Token with `read:package` + `write:package` scopes — used to push images to `git.hellomanoel.com` (do not name secrets `GITEA_*`; that prefix is reserved) |
-| `REGISTRY_USER` | Gitea username that owns `REGISTRY_PAT` (`manoel-freitas`) |
 
 HTTP 404 from `compose.deploy` usually means the compose id is wrong (Application id instead of Compose) or `DOKPLOY_URL` still includes `/api`.
 
-The automatic `GITEA_TOKEN` runs workflows but **cannot push OCI packages** ([gitea#23642](https://github.com/go-gitea/gitea/issues/23642)); registry authentication therefore uses `REGISTRY_PAT` + `REGISTRY_USER`. No Laravel/`APP_KEY`/DB/R2/Resend secrets belong in Gitea for this pipeline.
+`GITHUB_TOKEN` (automatic) publishes to GHCR with `packages:write`. No Laravel/`APP_KEY`/DB/R2/Resend secrets belong in GitHub for this pipeline.
 
 ## Workflows
 
-Workflows live in [`.gitea/workflows/`](../../.gitea/workflows/).
-
-`actions/cache` and Docker Buildx `type=gha` are **not** used: the act_runner cache server is not reachable from job containers by default (`getCacheEntry` ETIMEDOUT). Re-enable only after configuring a reachable `cache.host`/`external_server` on the runner.
-
-CI Postgres services must **not** publish host port `5432` (use service hostname `postgres` on the job network). Publishing `5432:5432` on a shared VPS runner fails with `Bind for 0.0.0.0:5432 failed: port is already allocated` when another job/orphan still holds the port.
-
-Parallel CI jobs need the act_runner `config.yaml` to keep `container.network` **empty** (per-job Docker network + service DNS) and `runner.capacity` ≥ 2. Setting `network: bridge` puts every job on the default bridge and makes parallel Postgres collide. Nested app containers (browser/container jobs) must join that job network by name and must **not** publish host `:8000`. On the current 1 vCPU / ~4 GiB VPS, `capacity: 2` is the safe ceiling.
-
 ### Staging (automatic)
 
-[`.gitea/workflows/deploy-staging.yml`](../../.gitea/workflows/deploy-staging.yml) — separate workflow, triggered by `workflow_run` when **CI** completes on `main`.
+[`.github/workflows/deploy-staging.yml`](../../.github/workflows/deploy-staging.yml)
 
-Requires **Gitea ≥ 1.25** (`workflow_run` is not implemented as an Actions trigger in 1.24.x). Match both workflow display name `CI` and file id `ci.yml`.
-
-1. Waits for workflow `CI` success (`workflow_run`) on push to `main`.
-2. Builds once; pushes `:<full-sha>` and `:staging` to the Gitea registry.
+1. Waits for workflow `CI` success on push to `main`.
+2. Builds once; pushes `:<full-sha>` and `:staging`.
 3. Calls Dokploy `compose.deploy` and polls until done.
 4. Runs [`scripts/deploy/smoke.sh`](../../scripts/deploy/smoke.sh) against `STAGING_URL`.
 
-Manual re-deploy: **Actions → Deploy staging → Run workflow** (`workflow_dispatch`).
-
-`DOKPLOY_API_KEY` must be the **plaintext** key from Dokploy → Profile → API (starts like `amare…`). Do not paste the hashed `apikey.key` column from Postgres — that yields HTTP 401.
-
 ### Production (manual)
 
-[`.gitea/workflows/promote-production.yml`](../../.gitea/workflows/promote-production.yml)
+[`.github/workflows/promote-production.yml`](../../.github/workflows/promote-production.yml)
 
-1. Operator runs **Gitea → Actions → Promote production**.
-2. Inputs: full `sha` already in the Gitea registry; `confirm` must be exactly `PRODUCTION`.
+1. Operator runs **Actions → Promote production**.
+2. Inputs: full `sha` already on GHCR; `confirm` must be exactly `PRODUCTION`.
 3. Retags the **same digest** as `:production` (no rebuild).
 4. Deploys production compose + smoke.
 
-Human approval is the explicit `workflow_dispatch` + confirmation string (Gitea does not support GitHub Environment required reviewers).
+Private repos on GitHub Free do not get Environment required reviewers; human approval is the explicit `workflow_dispatch` + confirmation string. GitHub Pro Environment reviewers are optional later.
 
 ## First admin and authorized production seeding
 
@@ -275,10 +256,10 @@ No rebuild. Move the environment alias to a previous SHA digest and redeploy.
 ### Staging
 
 ```bash
-# Locally or in a one-off Actions shell with Gitea registry login
+# Locally or in a one-off Actions shell with GHCR login
 docker buildx imagetools create \
-  --tag git.hellomanoel.com/manoel-freitas/amare:staging \
-  git.hellomanoel.com/manoel-freitas/amare:<previous-sha>
+  --tag ghcr.io/<owner>/<repo>:staging \
+  ghcr.io/<owner>/<repo>:<previous-sha>
 
 # Then trigger Dokploy deploy (UI Deploy, or):
 DOKPLOY_URL=... DOKPLOY_API_KEY=... DOKPLOY_COMPOSE_ID=... \
@@ -316,7 +297,7 @@ Expects HTTP 200 for `/up`, `/`, and `/admin/login`.
 ## Local validation of Compose
 
 ```bash
-APP_IMAGE=git.hellomanoel.com/manoel-freitas/amare IMAGE_TAG=staging \
+APP_IMAGE=ghcr.io/<owner>/<repo> IMAGE_TAG=staging \
   docker compose -f docker-compose.deploy.yml config
 ```
 

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

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

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

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

@@ -1,18 +0,0 @@
-# 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/complete-foundation-parity/tasks.md

@@ -36,8 +36,8 @@
 
 ## 6. Phase 0 exit evidence
 
-- [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.1 Perform first successful staging deploy of a `main` SHA and capture evidence (workflow URL, smoke output)
 - [ ] 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 — local runtime/auth/audit/coverage evidence was recorded by PR #39, and the staging exit criterion was subsequently marked complete from successful run 31395107465.
-- [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 are complete — blocked by tasks 3.4 and 6.2, tracked separately in MAN-125.
+- [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)
+- [ ] 6.4 Run full `composer quality` and confirm all five CI jobs + staging deploy path green
+- [ ] 6.5 Report in SPEC §24 format; archive this change only after remaining parity tasks (1–3) also complete

openspec/changes/enhance-public-motion/tasks.md

@@ -21,4 +21,4 @@
 
 - [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
-- [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.
+- [ ] 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

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

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

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

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

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

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

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

@@ -1,14 +0,0 @@
-## 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/package-detail-pages/.openspec.yaml

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

openspec/changes/package-detail-pages/design.md

@@ -1,96 +0,0 @@
-## Context
-
-`WeddingPackage` já cobre cards ordenados + CTA WhatsApp/briefing (change `restructure-home-weddings-corporate`, capability ainda só no delta completo). Campos atuais: `name`, `level`, `summary`, `scope_items` (json), `cta_label`, `sort_order`, `published_at`. Sem slug, sem corpo de detalhe, sem imagens. Portfólio (`portfolio.show`, `FindPublishedPortfolioCaseBySlug`, PageMeta, sitemap) é o padrão de detalhe a espelhar. Mock visual: `/home/manoelfreitas/Downloads/amare-assessoria-completa.html`. Tokens: `DESIGN.md` / `resources/css/tokens.css` (Heritage Editorial) — não Cormorant/Inter do HTML estático.
-
-## Goals / Non-Goals
-
-**Goals:**
-
-- Detalhe CMS-driven `/pacotes/{slug}` para as 3 modalidades, publish-gated.
-- Composição mock → tokens do projeto (olive accent, EB Garamond via stack existente, bg cream).
-- CTA final = mesmo canal contextual dos cards (`wa.me` ou `/briefing?servico_interesse=`).
-- SEO mínimo: meta por registro, canonical, OG image (hero ou default), entrada no sitemap.
-- Admin Filament editável sem deploy de copy.
-
-**Non-Goals:**
-
-- Rota índice `/pacotes`; substituir cards da home; WhatsApp Business API; preços; multi-idioma; Livewire público; gallery multi-imagem além de hero + audience.
-
-## Decisions
-
-### Estender `WeddingPackage`, não criar modelo novo
-
-Uma entidade comercial já existe e é o que home/serviços já consomem. Detalhe é projeção do mesmo agregado. Modelo paralelo geraria sync de publicação/slug e viola YAGNI.
-
-### Slug único + publicação por `published_at`
-
-Igual portfólio: URL estável, scope `published()`, query Application `FindPublishedWeddingPackageBySlug`. Draft/inexistente → 404 HTTP, sem vazar campos internos.
-
-### Campos de detalhe (additive)
-
-| Campo | Uso |
-|-------|-----|
-| `slug` | string unique |
-| `eyebrow` | ex. "Assessoria" |
-| `title_line` | parte romana do H1 |
-| `title_emphasis` | parte itálica do H1 |
-| `hero_lead` | parágrafo do hero |
-| `hero_image_path` / `hero_image_alt` | foto hero |
-| `benefits` | jsonb `[{icon_key,label}]` — faixa escura |
-| `included_items` | jsonb `[{icon_key,title,description}]` — grid 3 col |
-| `audience_heading` | default editorial se vazio ok |
-| `audience_intro` | texto |
-| `audience_points` | jsonb `string[]` checklist |
-| `audience_image_path` / `audience_image_alt` | foto 50/50 |
-| `final_cta_heading` / `final_cta_body` | bloco final |
-| `meta_title` / `meta_description` | SEO opcional |
-
-Manter `summary` + `scope_items` para cards. Não migrar cards para `included_items` neste ciclo.
-
-### Catálogo fechado de ícones (`PackageIconCatalog`)
-
-Select Filament → `icon_key` string. Map PHP/Blade para SVGs inline (ou partials). Sem upload de SVG arbitrário (XSS/ops). Chaves mínimas cobrem mock (ex.: calendar, checklist, users, map, heart, spark — nomes estáveis kebab).
-
-### Hero de pacote vs `photo-hero` genérico
-
-Mock exige H1 bipartido (linha + ênfase itálica), divisor vertical, CTA outline no hero e foto. Preferir componente dedicado `x-public.package-hero` (ou estender `photo-hero` só se API ficar genérica sem branching feio). Seções: `package-benefits`, `package-included`, `package-audience`, reutilizar `final-cta` se encaixar.
-
-### CTA WhatsApp
-
-Reutilizar VO/helper já usado nos cards (digits de `SiteSetting.whatsapp_number`, mensagem com nome da modalidade). Mesma regra de fallback briefing. Não duplicar lógica de normalização.
-
-### Links a partir dos cards
-
-Card: título/área → `route('packages.show', $package)` quando slug presente; botão CTA continua WhatsApp/briefing. Sem quebrar testes de CTA existentes.
-
-### Imagens
-
-`PublicImageUploadRules` + disk público existente + `x-media.image`. Paths nullable; se hero ausente, layout degrada (omitir slot de imagem).
-
-### Camada Application
-
-- `FindPublishedWeddingPackageBySlug`
-- Estender `GetSitemapEntries` com slugs de pacotes publicados
-- PageMeta no controller (espelhar PortfolioCaseController)
-
-Sem repository genérico / BaseAction.
-
-## Risks / Trade-offs
-
-- [Capability `wedding-packages` ainda não está em `openspec/specs/`] → delta ADDED nesta change; ao arquivar, consolidar com requirements de cards do change completo ou arquivar ambos em ordem.
-- [Copy das 3 modalidades incompleta] → seeder: Essenza = mock; Conduzione/Grand Jour estrutura paralela adaptada; admin pode editar.
-- [Ícones insuficientes no catálogo] → adicionar chave no map + opção Filament; sem free-text SVG.
-- [Cards sem slug durante migrate] → migration backfill slug a partir do name; seeder garante os 3 oficiais.
-- [Duplicação visual mock vs tokens] → testes de tokens existentes + asserts de classes/roles; não copiar hex do HTML.
-
-## Migration Plan
-
-1. Deploy migration additive + código + assets Blade juntos.
-2. Rodar seeder/update das 3 modalidades (slug + detalhe).
-3. Verificar `/pacotes/essenza` (etc.), 404 draft, sitemap, CTA WA.
-4. Rollback: remover rota/views; colunas additive podem permanecer; unpublish pacotes se necessário.
-
-## Open Questions
-
-- Nenhuma bloqueante (decisões de produto já confirmadas: detalhe-only, extend model, 3 modalidades, WA CTA).
-- WEB-ID dedicado a package detail: não existe no SPEC; rastrear via WEB-02 + padrão WEB-03 até SPEC ganhar ID explícito.

openspec/changes/package-detail-pages/proposal.md

@@ -1,32 +0,0 @@
-## Why
-
-Modalidades de casamento (Essenza, Conduzione, Grand Jour) existem no CMS e na home/serviços só como cards com CTA WhatsApp. Não há página de detalhe: o visitante não consegue ler o que está incluso, para quem é o pacote ou prova visual editorial antes de converter. O mock aprovado (`amare-assessoria-completa.html`) define a jornada; falta rota CMS-driven `/pacotes/{slug}` alinhada a WEB-02/WEB-03 e ao padrão de detalhe do portfólio.
-
-## What Changes
-
-- Estender `WeddingPackage` com slug estável, campos editoriais de detalhe (hero, benefícios, itens inclusos, audiência, imagens, SEO opcional) sem remover `summary`/`scope_items` dos cards.
-- Expor rota pública `packages.show` em `/pacotes/{slug}`: só publicados; rascunho → 404 (mesmo contrato de `portfolio.show`).
-- Renderizar página de detalhe Heritage Editorial espelhando o mock (hero split, faixa de benefícios, grid “O que está incluso”, bloco audiência, CTA final WhatsApp contextual com fallback briefing).
-- Incluir slugs publicados no sitemap; meta title/description/canonical/OG por pacote.
-- Filament: seções de detalhe + catálogo fechado de ícones SVG; seeder preenche as 3 modalidades.
-- Cards na home e em `/servicos` passam a linkar para o detalhe (navegação secundária); CTA primário permanece WhatsApp/briefing.
-
-## Capabilities
-
-### New Capabilities
-
-- `wedding-packages`: modalidades publicáveis com detalhe por slug (baseline ainda não arquivada em `openspec/specs/`; esta change define o contrato de detalhe e reafirma cards/CTA já entregues).
-
-### Modified Capabilities
-
-- `public-site-pages`: incluir rota `packages.show` (`/pacotes/{slug}`) e regra de 404 para modalidade não publicada; cards de modalidade podem apontar ao detalhe.
-- `public-seo`: sitemap e metadados de página para modalidades publicadas.
-- `service-catalog`: listagem de serviços/casamentos referencia o detalhe da modalidade quando existir slug publicado.
-
-## Impact
-
-Migration/model/factory/seeder `WeddingPackage`; query `FindPublishedWeddingPackageBySlug`; controller + rota + view Blade; componentes de seção; `GetSitemapEntries` / PageMeta; Filament `WeddingPackageResource`; links em partials de packages (home/serviços); testes feature (200/404, sitemap, CTA, conteúdo). Atende extensão de WEB-01/WEB-02 e o padrão de detalhe de WEB-03. Sem page builder, sem índice `/pacotes`, sem integração oficial WhatsApp, sem CRM (SPEC.md §4.2).
-
-## Não objetivos
-
-- Índice de pacotes, substituir `/servicos`, builder genérico, preços dinâmicos, checkout, multi-idioma, Livewire no site público, inventar prova ou cases Corporate (SPEC.md §4.2).

openspec/changes/package-detail-pages/specs/public-seo/spec.md

@@ -1,84 +0,0 @@
-## MODIFIED Requirements
-
-### Requirement: Every public page emits title, description and canonical
-
-The system SHALL render a unique `<title>`, a `<meta name="description">` and a `<link rel="canonical">` on every public route (SPEC §6.6, §19). Portfolio cases and wedding modalities MUST use `meta_title`/`meta_description` when filled and fall back to title/name and summary/hero lead otherwise. Pages without page-level metadata MUST fall back to `default_meta_title` and `default_meta_description` from `site_settings`.
-
-#### Scenario: Page-level metadata overrides defaults
-
-- **GIVEN** a published case with `meta_title` and `meta_description` filled
-- **WHEN** a visitor loads the case detail
-- **THEN** the rendered title and description MUST use the case values
-
-#### Scenario: Wedding modality metadata overrides defaults
-
-- **GIVEN** a published wedding modality with `meta_title` and `meta_description` filled
-- **WHEN** a visitor loads `/pacotes/{slug}`
-- **THEN** the rendered title and description MUST use the modality values
-
-#### Scenario: Missing metadata falls back to site defaults
-
-- **GIVEN** a published case without `meta_title`
-- **WHEN** a visitor loads the case detail
-- **THEN** the rendered title MUST be derived from the case title
-- **AND** the description MUST fall back to the case summary or the site default
-
-#### Scenario: Canonical points to the absolute route URL
-
-- **WHEN** any public page is rendered
-- **THEN** the canonical URL MUST be the absolute URL of that route without query parameters
-
-### Requirement: Open Graph metadata is emitted for sharing
-
-The system SHALL emit Open Graph tags (`og:title`, `og:description`, `og:type`, `og:url`, `og:image`) on public pages. The image MUST use the page cover/hero image when available and `default_og_image_path` from `site_settings` otherwise.
-
-#### Scenario: Case detail uses its cover as OG image
-
-- **GIVEN** a published case with a cover image
-- **WHEN** the case detail is rendered
-- **THEN** `og:image` MUST reference the case cover image URL
-
-#### Scenario: Wedding modality detail uses hero as OG image
-
-- **GIVEN** a published wedding modality with a hero image
-- **WHEN** `/pacotes/{slug}` is rendered
-- **THEN** `og:image` MUST reference the modality hero image URL
-
-#### Scenario: Pages without cover use the default OG image
-
-- **WHEN** a page without its own image is rendered
-- **THEN** `og:image` MUST reference `default_og_image_path`
-
-### Requirement: Sitemap and robots are served by the application
-
-The system SHALL serve `/sitemap.xml` listing the home, institutional routes, the services listing, the portfolio listing, every published case slug, and every published wedding modality slug with its last modification date. `/robots.txt` MUST be served by an application route referencing the sitemap URL.
-
-#### Scenario: Sitemap contains only published slugs
-
-- **GIVEN** one published case and one draft case
-- **WHEN** `/sitemap.xml` is requested
-- **THEN** the response MUST include the published slug
-- **AND** MUST NOT include the draft slug
-
-#### Scenario: Sitemap contains published wedding modality slugs
-
-- **GIVEN** one published wedding modality and one draft wedding modality
-- **WHEN** `/sitemap.xml` is requested
-- **THEN** the response MUST include `/pacotes/{published-slug}`
-- **AND** MUST NOT include the draft modality slug
-
-#### Scenario: Newly published case enters the sitemap
-
-- **WHEN** an admin publishes a case
-- **THEN** the case slug MUST appear in `/sitemap.xml` on the next request
-
-#### Scenario: Newly published wedding modality enters the sitemap
-
-- **WHEN** an admin publishes a wedding modality
-- **THEN** the modality package URL MUST appear in `/sitemap.xml` on the next request
-
-#### Scenario: Robots references the sitemap
-
-- **WHEN** `/robots.txt` is requested
-- **THEN** the response MUST be `text/plain`
-- **AND** MUST contain the absolute `/sitemap.xml` URL

openspec/changes/package-detail-pages/specs/public-site-pages/spec.md

@@ -1,57 +0,0 @@
-## MODIFIED Requirements
-
-### Requirement: Public routes serve published content without authentication
-
-The system SHALL expose the public routes of SPEC §5.1 plus the additive package detail route: `home` (`/`), `services.index` (`/servicos`), `packages.show` (`/pacotes/{slug}`), `portfolio.index` (`/portfolio`), `portfolio.show` (`/portfolio/{slug}`), `about` (`/sobre`), `contact` (`/contato`) and `privacy` (`/privacidade`). Every public route MUST respond without authentication and MUST NOT expose unpublished content, internal fields, or internal notes (SPEC §19).
-
-#### Scenario: Guest reaches every public route
-
-- **WHEN** an unauthenticated visitor requests any public route listed above that has published content where required
-- **THEN** the response status MUST be 200
-- **AND** no redirect to `/admin/login` MUST occur
-
-#### Scenario: Unpublished content is invisible
-
-- **GIVEN** a service, portfolio case, wedding modality, or testimonial with `published_at` null
-- **WHEN** a visitor loads the corresponding public listing or home section
-- **THEN** the record MUST NOT appear in the rendered output
-
-#### Scenario: Unpublished case detail returns 404
-
-- **GIVEN** a portfolio case saved as draft
-- **WHEN** a visitor requests `/portfolio/{slug}` for that case
-- **THEN** the response status MUST be 404
-
-#### Scenario: Unpublished wedding modality detail returns 404
-
-- **GIVEN** a wedding modality saved as draft
-- **WHEN** a visitor requests `/pacotes/{slug}` for that modality
-- **THEN** the response status MUST be 404
-
-#### Scenario: Published case detail becomes reachable
-
-- **GIVEN** a portfolio case saved as draft
-- **WHEN** an admin fills the required fields and publishes the case
-- **THEN** `/portfolio/{slug}` MUST respond 200
-- **AND** the case MUST appear in the `/portfolio` listing
-
-#### Scenario: Published wedding modality detail becomes reachable
-
-- **GIVEN** a wedding modality saved as draft with required detail fields
-- **WHEN** an admin publishes the modality
-- **THEN** `/pacotes/{slug}` MUST respond 200
-
-## ADDED Requirements
-
-### Requirement: Wedding modality detail uses Heritage Editorial public layout
-The system SHALL render `/pacotes/{slug}` with the public layout (header/footer shared), Heritage Editorial tokens, and section order: package hero (eyebrow, bipartite title, lead, outline secondary actions as designed, hero media), dark benefit strip, included-items grid, audience split (media + checklist), final conversion CTA. The page MUST be server-rendered Blade without a public Livewire dependency. Missing optional images MUST NOT break the page (omit or degrade the media slot).
-
-#### Scenario: Detail page section order
-- **GIVEN** a published modality with complete detail content
-- **WHEN** a visitor loads `/pacotes/{slug}`
-- **THEN** the document MUST include the hero, benefits, included items, audience and final CTA regions in that order
-- **AND** MUST use the public layout chrome
-
-#### Scenario: Detail page has no console errors
-- **WHEN** the modality detail is loaded in a real browser at desktop and mobile viewports
-- **THEN** the browser console MUST contain no JavaScript errors

openspec/changes/package-detail-pages/specs/service-catalog/spec.md

@@ -1,9 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Services wedding section links to modality detail
-When the services page renders published wedding modalities, each modality card SHALL expose a link to `/pacotes/{slug}` for published records that have a slug, while keeping the existing WhatsApp/briefing conversion CTA.
-
-#### Scenario: Services card navigates to package detail
-- **GIVEN** at least one published wedding modality with a slug
-- **WHEN** a visitor loads `/servicos`
-- **THEN** the wedding modalities region MUST include a link to that modality's `/pacotes/{slug}` URL

openspec/changes/package-detail-pages/specs/wedding-packages/spec.md

@@ -1,58 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Wedding modalities are managed as publishable ordered content
-The system SHALL let an admin manage `WeddingPackage` records with name, unique slug, level, summary, ordered scope items, CTA label, sort order and `published_at`. Only published records SHALL appear in public wedding card 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 with stable unique slugs
-
-### 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`. The same rule MUST apply on modality cards and on the modality detail page final CTA.
-
-#### Scenario: Valid WhatsApp setting creates contextual link
-- **GIVEN** a valid official WhatsApp number
-- **WHEN** a visitor activates a wedding modality CTA on a card or detail page
-- **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 on a card or detail page
-- **THEN** the visitor reaches `/briefing` with `servico_interesse` prefilled
-
-### Requirement: Wedding modality detail content is CMS-managed
-The system SHALL store per-modality detail fields: eyebrow, bipartite title (`title_line`, `title_emphasis`), hero lead, optional hero image with alt, ordered benefits (`icon_key`, label), ordered included items (`icon_key`, title, description), audience heading/intro/points and optional audience image with alt, final CTA heading/body, and optional `meta_title` / `meta_description`. Icon keys MUST come from a closed catalog enforced in admin validation. `summary` and `scope_items` MUST remain available for card surfaces.
-
-#### Scenario: Admin can edit detail sections
-- **WHEN** an admin opens a WeddingPackage in Filament
-- **THEN** the form MUST expose detail sections for hero, benefits, included items, audience, final CTA and SEO
-- **AND** icon fields MUST offer only catalog keys
-
-#### Scenario: Seeder fills detail for official modalities
-- **WHEN** the content seeder runs
-- **THEN** each official modality MUST have slug and non-empty hero lead plus at least one benefit and one included item suitable for public render
-
-### Requirement: Published modality detail page is publicly reachable by slug
-The system SHALL expose `packages.show` at `/pacotes/{slug}` without authentication. Only modalities with non-null `published_at` in the past or present MUST resolve. Draft or unknown slugs MUST return HTTP 404 without exposing internal fields.
-
-#### Scenario: Published modality detail returns 200
-- **GIVEN** a published wedding modality with slug `essenza`
-- **WHEN** a visitor requests `/pacotes/essenza`
-- **THEN** the response status MUST be 200
-- **AND** the page MUST render hero title parts, benefits, included items, audience block and final CTA using CMS values
-
-#### Scenario: Draft modality detail returns 404
-- **GIVEN** a wedding modality saved as draft
-- **WHEN** a visitor requests `/pacotes/{slug}` for that modality
-- **THEN** the response status MUST be 404
-
-#### Scenario: Cards link to the detail page
-- **GIVEN** a published modality with a slug
-- **WHEN** a visitor views the home or services wedding cards
-- **THEN** a navigation control MUST link to `/pacotes/{slug}`
-- **AND** the primary conversion CTA MUST remain the WhatsApp or briefing channel

openspec/changes/package-detail-pages/tasks.md

@@ -1,29 +0,0 @@
-## 1. Data model and domain catalog
-
-- [x] 1.1 Migration additive em `wedding_packages`: `slug` unique (backfill a partir de `name`), campos de detalhe (eyebrow, title_line, title_emphasis, hero_lead, hero_image_*, benefits jsonb, included_items jsonb, audience_*, final_cta_*, meta_*), atualizar model `$fillable`/casts e factory. Evidência: `database/migrations/2026_08_12_120000_extend_wedding_packages_for_detail_pages.php` (roda limpo), `app/Models/WeddingPackage.php` (fillable+casts+booted slug), `database/factories/WeddingPackageFactory.php` (slug + campos de detalhe).
-- [x] 1.2 `PackageIconCatalog` (chaves fechadas + labels pt-BR) e validação de `icon_key` em benefits/included_items. Evidência: `app/Domain/Marketing/PackageIconCatalog.php` (6 chaves: calendar/checklist/users/map/heart/spark), Select icon_key em `WeddingPackageForm` usa `PackageIconCatalog::labels()`.
-- [x] 1.3 Feature/unit: factory published com slug; scope published inalterado; icon_key inválido rejeitado na validação admin/request path usado pelo Filament. Evidência: `WeddingPackageTest` (4 testes: scope published + seeder, factory slug autofill, icon catalog aceita/rejeita `paw`).
-
-## 2. Application + public route
-
-- [x] 2.1 Query `FindPublishedWeddingPackageBySlug` + teste 200/null para draft. Evidência: `app/Application/Queries/Marketing/FindPublishedWeddingPackageBySlug.php`; `FindPublishedWeddingPackageBySlugTest` (retorna published, null para draft/inexistente).
-- [x] 2.2 `PackageController@show`, rota nomeada `packages.show` `/pacotes/{slug}`, PageMeta (meta_title/description fallback name/summary|hero_lead, OG hero). Evidência: `app/Http/Controllers/PublicSite/PackageController.php`, `routes/web.php` (`packages.show`), `PageMeta::forPackage` (title=meta_title??title_line??name, description=meta_description??summary, ogImageUrl=hero_image_path).
-- [x] 2.3 Estender `GetSitemapEntries` com pacotes publicados; teste sitemap inclui/exclui draft. Evidência: `GetSitemapEntries` appends pacotes published; `SitemapTest::test_sitemap_includes_only_published_packages` (inclui `essenza`, exclui `rascunho-pacote`).
-
-## 3. Blade detail (Heritage Editorial)
-
-- [x] 3.1 View `pages/packages/show` + componentes `package-hero`, `package-benefits`, `package-included`, `package-audience`; layout `layouts.public`; tokens DESIGN.md (sem hex do mock). Evidência: `resources/views/pages/packages/show.blade.php` + `resources/views/components/public/package-{hero,benefits,included,audience}.blade.php` + `resources/views/components/package/icon.blade.php` (SVG de catálogo); classes `amare-*` e `text-hero-spread` (tokens), sem hex do mock.
-- [x] 3.2 CTA final reutiliza builder WhatsApp/briefing dos cards; teste feature assert `wa.me` / `briefing?servico_interesse`. Evidência: `app/Support/PackageContactLink::for()` (helper compartilhado), `package-final-cta.blade.php` usa builder; `PackageDetailTest` (tests 4-5: wa.me com número, briefing fallback).
-- [x] 3.3 Feature: render de seções a partir do CMS; 404 draft; guest sem auth. Evidência: `PackageDetailTest` (5 testes: render de seções CMS assertSee, 404 draft, 404 slug inexistente, CTA wa.me/briefing).
-
-## 4. Filament + seeder + card links
-
-- [x] 4.1 `WeddingPackageResource`: seções Hero, Benefícios, Inclusos, Audiência, CTA final, SEO; FileUpload imagens; Select icon_key do catálogo. Evidência: `app/Filament/Resources/WeddingPackages/Schemas/WeddingPackageForm.php` (sections Identificação/Hero/Diferenciais/Inclusos/Audiência/CTA final/SEO; `PublicImageUploadRules::fileUpload/altTextField`; `Select icon_key` options `PackageIconCatalog::labels()`); `WeddingPackagesTable` ganhou coluna `slug`.
-- [x] 4.2 Seeder/update Essenza (copy mock), Conduzione e Grand Jour (estrutura paralela) com slugs `essenza`, `conduzione`, `grand-jour`. Evidência: `database/seeders/WeddingPackagesSeeder.php` (3 pacotes com slug + campos de detalhe completos); `WeddingPackageTest::test_content_seeder_creates_official_wedding_modalities` verde.
-- [x] 4.3 Home + `/servicos` cards: link secundário para `packages.show`; CTA primário WA intacto; testes de regressão de CTA. Evidência: `home/packages.blade.php` + `home/wedding-packages.blade.php` + `services/index.blade.php` (link 'Conhecer esta modalidade' + CTA primário refatorado via `PackageContactLink`); `HomePageContentTest` (22 testes: 143 assertions, incl. href packages.show).
-
-## 5. Verification gate
-
-- [x] 5.1 `composer pint:check` + `composer phpstan` no escopo alterado. Evidência: `vendor/bin/pint --test` passou (fix `ordered_imports` em `routes/web.php`); `composer phpstan` (level 5, `--memory-limit=1G --debug`) = No errors.
-- [x] 5.2 `composer test:unit` + `composer test:feature` verdes (incl. novos testes de pacote). Evidência: `test:unit` 42 passed (186 assertions); `test:feature` 193 passed (1182 assertions); `PackageDetailTest` (5), `FindPublishedWeddingPackageBySlugTest`, `SitemapTest` (3) verdes.
-- [x] 5.3 `openspec validate package-detail-pages` e marcar tasks só com evidência. Evidência: `openspec validate package-detail-pages` = "Change 'package-detail-pages' is valid"; tasks 1.1-5.3 marcadas acima com referências.

openspec/changes/remodel-about-page/.openspec.yaml

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

openspec/changes/remodel-about-page/design.md

@@ -1,27 +0,0 @@
-# Design: remodel About page
-
-## Context
-
-Mock `amare-sobre(1).html` define composição e copy. O site já tem Heritage Editorial (`tokens.css`, `DESIGN.md`), `about_image_*` no CMS, e `PortfolioCase` featured na home.
-
-## Decisions
-
-1. **Hero** reusa `about_image_path` com layout split próprio (`x-about.hero`), não o full-viewport `x-public.photo-hero`. Fallback tonal quando sem imagem.
-2. **Michele** usa `founder_image_*` novos; sem path → coluna tonal, sem request de imagem inventada.
-3. **Portfólio** lê até 6 casos `published` + `is_featured` via `GetAboutContent` (mesma regra da home).
-4. **Copy** de pilares/Michele/processo/CTA fixa do mock; `about_summary` alimenta lead/SEO.
-5. **Visual**: estrutura do mock; radius 0, EB Garamond, botões `btn` existentes — desvios tipográficos/pill do HTML são descartados.
-
-## Spine
-
-```
-PageController::about
- → GetAboutContent
- → AboutContent
- → pages/about.blade.php + x-about.*
-```
-
-## Risks
-
-- Testes que acoplam `/sobre` a `data-photo-hero` full-vh precisam atualizar o contrato.
-- Home positioning continua usando `about_image_path` — não reaproveitar esse campo como foto da Michele.

openspec/changes/remodel-about-page/proposal.md

@@ -1,26 +0,0 @@
-# Remodel página Sobre conforme mock aprovado
-
-## Why
-
-A rota `/sobre` ainda usa abertura `photo-hero` full-viewport + lista de princípios. O cliente validou o mock `amare-sobre(1).html` com jornada editorial própria: hero split, pilares, bloco Michele, processo, portfólio em destaque e CTA. Sem essa remodelação, a página institucional fica desalinhada da home e do material aprovado.
-
-## What Changes
-
-- `/sobre` recomposta em seções `x-about.*` espelhando a ordem do mock (hero, pilares, Michele, processo, portfólio masonry, CTA).
-- Novo campo CMS `founder_image_path` / `founder_image_alt` no singleton `site_settings` para a foto da Michele; hero continua em `about_image_path`.
-- Query `GetAboutContent` + DTO `AboutContent` (featured cases ≤6) no spine Application.
-- Tokens Heritage Editorial do repo (sem Inter/Cormorant, sem pills do HTML estático).
-
-## Non-Goals
-
-- CMS para copy dos pilares/Michele/processo.
-- Replicar header/footer do HTML estático.
-- Alterar tokens globais assertados por `HeritageEditorialTokensTest`.
-- Gerar fotografia da Michele (apenas upload).
-
-## Capabilities
-
-### Modified Capabilities
-
-- `public-site-pages`: `/sobre` com composição do mock; motion contract preservado.
-- `site-settings`: campos `founder_image_path` e `founder_image_alt` administráveis no Filament.

openspec/changes/remodel-about-page/specs/public-site-pages/spec.md

@@ -1,32 +0,0 @@
-## ADDED Requirements
-
-### Requirement: About page follows approved editorial composition
-
-The `/sobre` route SHALL render the Heritage Editorial public layout with this section order: split hero (eyebrow “Sobre nós”, title “Sobre a Amare”, lead from `about_summary` or editorial default, CTA to `#michele`), three pillars, founder block `#michele` (Michele), process (“Como trabalhamos”), featured portfolio masonry (up to six published featured cases), and a final proposal CTA. The page MUST use shared motion markers (`data-motion="page-open"`, `data-reveal*`) without route transitions. Principles list MUST NOT appear on `/sobre` (home may still show them). Contact, privacy and error surfaces remain unchanged by this requirement.
-
-#### Scenario: Visitor sees the mock section order
-
-- **WHEN** a visitor loads `/sobre`
-- **THEN** the response MUST include the headings for Sobre a Amare, the three pillars, Conheça Michele, Como trabalhamos, Portfólio em destaque, and the proposal CTA copy
-- **AND** MUST NOT render the numbered principles list formerly used on About
-
-#### Scenario: Founder photo comes from CMS when configured
-
-- **GIVEN** `site_settings.founder_image_path` is set with alt text
-- **WHEN** a visitor loads `/sobre`
-- **THEN** the Michele section MUST render that image with the configured alt
-- **AND** MUST use eager loading only for the about hero image, not invent a founder asset path when unset
-
-#### Scenario: About hero uses about_image with tonal fallback
-
-- **WHEN** `about_image_path` is configured
-- **THEN** `/sobre` MUST render a split editorial hero with that media (`loading="eager"` and `fetchpriority="high"`)
-- **WHEN** `about_image_path` is empty
-- **THEN** `/sobre` MUST render a tonal hero fallback without an empty image request
-
-#### Scenario: Featured portfolio tiles use real cases
-
-- **GIVEN** published featured portfolio cases exist
-- **WHEN** a visitor loads `/sobre`
-- **THEN** the masonry MUST link to those cases (or the portfolio index)
-- **AND** MUST NOT invent decorative photography when no cases exist (tonal slots allowed)

openspec/changes/remodel-about-page/specs/site-settings/spec.md

@@ -1,47 +0,0 @@
-## MODIFIED Requirements
-
-### Requirement: Site settings singleton is manageable by admin only
-
-The system SHALL persist site-wide settings in a `site_settings` table as a typed singleton (SPEC WEB-06, §8.2). Fields MUST include brand name, optional logo path and logo alt text, hero copy (eyebrow, title, subtitle, primary CTA label, optional secondary CTA label, optional hero note), manifesto copy (title, lead, body), method steps (structured typed data for four editorial steps), principles (structured typed list), about summary, optional about hero image path and alt text, optional founder image path and alt text (Michele portrait for `/sobre`), contact email/phone/city, social links (jsonb), default meta title/description, default OG image path and alt text, and optional analytics fields disabled by default.
-
-#### Scenario: Admin updates site settings
-
-- **WHEN** an admin saves the site settings form in Filament
-- **THEN** the singleton record is updated
-- **AND** labels and validation messages are in pt-BR
-
-#### Scenario: Founder image upload requires alt text
-
-- **WHEN** an admin uploads a founder image without alt text
-- **THEN** validation MUST fail with a pt-BR error message
-- **AND** alt text MUST remain optional when no founder image is present
-
-#### Scenario: Assistant cannot access site settings
-
-- **WHEN** an assistant navigates to site settings in Filament
-- **THEN** access MUST be denied with HTTP 403
-
-#### Scenario: Default OG image requires alt text
-
-- **WHEN** an admin uploads a default OG image without alt text
-- **THEN** validation MUST fail with a pt-BR error message
-- **AND** alt text MUST remain optional when no default OG image is present
-
-#### Scenario: Logo upload requires alt text
-
-- **WHEN** an admin uploads a brand logo without alt text
-- **THEN** validation MUST fail with a pt-BR error message
-- **AND** alt text MUST remain optional when no logo is uploaded
-
-#### Scenario: Singleton avoids generic key-value store
-
-- **WHEN** site settings are stored
-- **THEN** the system MUST use typed columns on `site_settings`
-- **AND** MUST NOT introduce a generic key/value configuration table
-
-#### Scenario: Editorial defaults remain available when optional fields are empty
-
-- **GIVEN** manifesto, method steps or principles fields are empty
-- **WHEN** the home is rendered
-- **THEN** the page MUST still render those sections using safe editorial defaults
-- **AND** MUST NOT error

openspec/changes/remodel-about-page/tasks.md

@@ -1,8 +0,0 @@
-# Tasks: remodel-about-page
-
-- [x] 1. Migration + SiteSetting fillable/PHPDoc para `founder_image_path` / `founder_image_alt`
-- [x] 2. Filament ManageSiteSettings: labels hero Sobre + upload Michele; media variants + seeders
-- [x] 3. AboutContent DTO + GetAboutContent; PageController injeta query
-- [x] 4. Componentes `x-about.*` + reescrever `pages/about.blade.php`
-- [x] 5. Feature tests About + atualizar ImmersivePhotoHero / Media / Motion / PublicPages / Filament alt
-- [ ] 6. PR verde

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

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

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

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

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

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

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

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

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

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

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

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