test: speed browser suite via visit reuse

Collapse route×viewport cartesian products, merge home motion
asserts, skip existing VisualContentSeeder JPEGs, ignore Screenshots.

.gitignore

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

DESIGN.md

@@ -73,7 +73,7 @@ Estrutura base usa grade central de 12 colunas no desktop e 4 no mobile, com lar
 
 Composições editoriais alternam colunas assimétricas, imagens em diferentes proporções e blocos de leitura curtos. Formulários, listas e navegação mantêm alinhamento estrito. Ritmo estrutural usa múltiplos de `8px`; ajustes tipográficos usam `4px`.
 
-Desktop aceita spreads, conteúdo deslocado e relações 5/7 ou 4/5. Mobile lineariza ordem sem esconder conteúdo essencial, mantém CTA acessível e troca spreads por sequências verticais. Fotografia pode ocupar viewport amplo, desde que texto e ação permaneçam legíveis.
+Desktop aceita spreads, conteúdo deslocado e relações 5/7 ou 4/5. Nas aberturas narrativas com fotografia, o spread padrão reserva 5/12 para o texto e 7/12 para a mídia; a coluna de leitura não passa de 470px, e o título mantém quebra normal. Mobile lineariza a ordem para texto seguido da fotografia sem esconder conteúdo essencial e mantém CTA acessível. Fotografia pode ocupar viewport amplo, desde que texto e ação permaneçam legíveis.
 
 **The Editorial Rhythm Rule.** Seções alternam imagem, texto, densidade e silêncio; repetição de grades idênticas por toda página é proibida.
 
@@ -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,36 +14,42 @@ web
 
 ## Product Purpose
 
-A Amare Assessoria usa uma única plataforma para apresentar sua marca, converter visitantes em oportunidades e conduzir a operação dos eventos. O produto deve reduzir planilhas e informações dispersas, preservar o fluxo de trabalho da equipe e deixar claro o que exige atenção.
+No recorte de lançamento, a Amare Assessoria usa o site institucional e seu CMS para apresentar a marca, publicar conteúdo e converter visitantes em pedidos de proposta por e-mail. O produto futuro continua planejado como uma única plataforma para conduzir leads e a operação dos eventos, mas essa evolução não faz parte do lançamento de 31/08/2026.
 
-Sucesso significa:
+Sucesso no lançamento significa:
 
 - visitantes qualificados concluírem o briefing;
+- a assessora atualizar os conteúdos essenciais sem depender de desenvolvimento;
+- o site equilibrar eventos sociais e corporativos com conteúdo real e autorizado;
+- acessibilidade, desempenho, jornadas críticas e deploy serem verificados antes da publicação.
+
+Nas fases futuras, sucesso também significará:
+
 - leads avançarem pelo pipeline sem depender de planilhas externas;
 - leads conquistados virarem eventos sem redigitação;
 - pendências reais do dia aparecerem com clareza;
-- tarefas, fornecedores, orçamento, pagamentos manuais e documentos permanecerem organizados por evento;
+- tarefas, fornecedores, orçamento, pagamentos manuais e documentos permanecerem organizados por evento.
-- jornadas críticas, acessibilidade e qualidade visual serem verificadas antes de cada deploy.
 
 ## Positioning
 
-Site público premium e operação interna formam um fluxo único. A mesma plataforma que transmite profissionalismo e capta a demanda transforma o lead em evento e orienta a equipe pelas pendências e exceções que precisam de ação, sem exigir troca radical de processo.
+No lançamento, o site público premium e o CMS interno formam a superfície entregue: a mesma aplicação transmite profissionalismo, capta a demanda por e-mail e permite manter o conteúdo essencial. A operação interna completa permanece como direção futura para transformar leads em eventos e orientar a equipe pelas pendências e exceções que precisam de ação, sem exigir troca radical de processo.
 
 ## Operating Context
 
 - Atuação em São Paulo, capital.
 - Serviços: casamentos, eventos corporativos e celebrações.
 - Operação realizada por assessora principal e equipe pequena.
-- Jornada prevista: descoberta no site, briefing, qualificação do lead, pipeline comercial, conversão em evento, checklist, fornecedores, orçamento, pagamentos manuais e documentos.
+- Jornada de lançamento: descoberta no site, briefing por e-mail e contato comercial fora da plataforma.
+- Jornada futura prevista: qualificação do lead, pipeline comercial, conversão em evento, checklist, fornecedores, orçamento, pagamentos manuais e documentos.
 - Interface pública em português do Brasil; dados financeiros em reais.
 - Área interna acessível por administradora e assistentes com papéis simples.
 
 ## Capabilities and Constraints
 
 - Produto single-tenant para a operação da Amare; não é SaaS para várias assessorias.
-- Duas superfícies integradas: site público responsivo com CMS e área interna operacional em Filament.
+- O lançamento inclui site público responsivo, CMS em Filament, briefing enviado por e-mail sem persistência de Lead, usuários internos simples, SEO básico, acessibilidade automatizada e deploy em contêiner.
-- MVP inclui briefing, CRM de leads, conversão em evento, tarefas, fornecedores, orçamento, pagamentos manuais, documentos, dashboard orientado a exceções, notificações, auditoria, SEO básico e deploy automatizado.
+- CRM de leads, conversão em evento, tarefas, fornecedores, orçamento, pagamentos manuais, documentos, dashboard orientado a exceções, notificações e auditoria permanecem especificados para as Fases 2 a 5, adiadas sem data pela ADR-016.
-- Implementação atual cobre fundação, site público e CMS; módulos operacionais posteriores ainda fazem parte do escopo planejado.
+- O produto futuro mantém duas superfícies integradas: site público responsivo com CMS e área interna operacional em Filament; no lançamento, a área interna cobre apenas CMS, configurações e usuários.
 - Não inclui portal ou login para cliente final, aplicativo nativo, pagamentos online, RSVP, gestão de convidados, assinatura eletrônica, integração oficial com WhatsApp, multi-tenancy ou PWA offline avançada.
 - Contas internas usam os papéis `admin` e `assistant`; permissões granulares ficam fora do MVP.
 - Fatos ainda em aberto: processo real de qualificação comercial, política de retenção LGPD para leads perdidos, canais oficiais, domínio e infraestrutura de produção.

SPEC.md

@@ -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, visuais e arquitetura estão verdes;
+- testes unit, feature, browser funcionais e arquitetura estão verdes;
 - CI bloqueia regressões;
 - imagem FrankenPHP é reproduzível;
 - staging e produção usam a mesma imagem promovida;

app/Application/Data/HomeContent.php

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

app/Application/Queries/Marketing/GetHomeContent.php

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

app/Filament/Pages/ManageSiteSettings.php

@@ -212,6 +212,26 @@ class ManageSiteSettings extends Page
                             ->reorderable()
                             ->columnSpanFull(),
                     ]),
+                Section::make('Corporate')
+                    ->description('Etapas apresentadas na frente Amare Corporate da home.')
+                    ->schema([
+                        Repeater::make('corporate_steps')
+                            ->label('Etapas do serviço corporativo')
+                            ->schema([
+                                TextInput::make('title')
+                                    ->label('Título')
+                                    ->required()
+                                    ->maxLength(255),
+                                Textarea::make('body')
+                                    ->label('Descrição')
+                                    ->required()
+                                    ->rows(2),
+                            ])
+                            ->defaultItems(3)
+                            ->maxItems(6)
+                            ->reorderable()
+                            ->columnSpanFull(),
+                    ]),
                 Section::make('Princípios')
                     ->schema([
                         TagsInput::make('principles')
@@ -231,6 +251,11 @@ class ManageSiteSettings extends Page
                             ->label('Telefone')
                             ->required()
                             ->maxLength(255),
+                        TextInput::make('whatsapp_number')
+                            ->label('WhatsApp oficial para as modalidades')
+                            ->tel()
+                            ->maxLength(40)
+                            ->helperText('Use o número com DDD. Sem um número válido, as CTAs levam ao briefing.'),
                         TextInput::make('city')
                             ->label('Cidade')
                             ->maxLength(255),

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

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

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

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

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

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

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

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

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

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

app/Filament/Resources/WeddingPackages/WeddingPackageResource.php

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

app/Http/Controllers/PublicSite/ContactController.php

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

app/Http/Controllers/PublicSite/PageController.php

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

app/Http/Controllers/PublicSite/PartnerInquiryController.php

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

app/Http/Controllers/PublicSite/ServiceController.php

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

app/Http/Requests/PublicSite/PartnerInquiryRequest.php

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

app/Mail/PartnerInquiry.php

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

app/Models/SiteSetting.php

@@ -12,6 +12,7 @@ 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
@@ -51,9 +52,11 @@ use Illuminate\Database\Eloquent\Model;
     'manifesto_body',
     'method_intro',
     'method_steps',
+    'corporate_steps',
     'principles',
     'email',
     'phone',
+    'whatsapp_number',
     'city',
     'social_links',
     'default_meta_title',
@@ -82,9 +85,11 @@ class SiteSetting extends Model
             'manifesto_body' => 'A Amare combina sensibilidade e precisão para criar encontros coerentes com cada cliente, marca e ocasião — sem fórmulas prontas, excessos ou ruído.',
             'method_intro' => 'Clareza em cada etapa. Tranquilidade durante todo o processo.',
             'method_steps' => self::defaultMethodSteps(),
+            'corporate_steps' => self::defaultCorporateSteps(),
             'principles' => self::defaultPrinciples(),
             'email' => 'amareassessoriaeventos@gmail.com',
             'phone' => '(11) 99999-9999',
+            'whatsapp_number' => null,
             'city' => 'São Paulo - SP',
             'social_links' => [],
             'default_meta_title' => 'Amare Assessoria de Eventos',
@@ -118,6 +123,27 @@ class SiteSetting extends Model
         ];
     }
 
+    /**
+     * @return list<array{title: string, body: string}>
+     */
+    public static function defaultCorporateSteps(): array
+    {
+        return [
+            [
+                'title' => 'Planejamento',
+                'body' => 'Estruturação de escopo, cronograma e prioridades.',
+            ],
+            [
+                'title' => 'Produção',
+                'body' => 'Coordenação dos elementos necessários para colocar o evento de pé.',
+            ],
+            [
+                'title' => 'Execução',
+                'body' => 'Condução e acompanhamento do evento conforme o projeto aprovado.',
+            ],
+        ];
+    }
+
     /**
      * @return list<string>
      */
@@ -139,6 +165,7 @@ class SiteSetting extends Model
         return [
             'social_links' => 'array',
             'method_steps' => 'array',
+            'corporate_steps' => 'array',
             'principles' => 'array',
             'analytics_enabled' => 'boolean',
         ];

app/Models/WeddingPackage.php

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

app/Policies/WeddingPackagePolicy.php

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

app/Providers/AppServiceProvider.php

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

database/factories/WeddingPackageFactory.php

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

database/migrations/2026_08_11_010000_add_corporate_steps_to_site_settings_table.php

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

database/migrations/2026_08_11_190000_add_whatsapp_number_to_site_settings_table.php

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

database/migrations/2026_08_11_190100_create_wedding_packages_table.php

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

database/seeders/ContentSeeder.php

@@ -49,6 +49,7 @@ class ContentSeeder extends Seeder
         $this->seedServices();
         $this->seedPortfolioCases();
         $this->call(TestimonialsSeeder::class);
+        $this->call(WeddingPackagesSeeder::class);
     }
 
     private function seedSiteSettings(): void
@@ -75,6 +76,7 @@ class ContentSeeder extends Seeder
             'manifesto_body' => 'A Amare combina sensibilidade e precisão para criar encontros coerentes com cada cliente, marca e ocasião — sem fórmulas prontas, excessos ou ruído.',
             'method_intro' => 'Clareza em cada etapa. Tranquilidade durante todo o processo.',
             'method_steps' => SiteSetting::defaultMethodSteps(),
+            'corporate_steps' => SiteSetting::defaultCorporateSteps(),
             'principles' => SiteSetting::defaultPrinciples(),
             'email' => 'amareassessoriaeventos@gmail.com',
             'phone' => '(11) 99999-9999',

database/seeders/VisualContentSeeder.php

@@ -30,6 +30,7 @@ class VisualContentSeeder extends Seeder
         $this->seedServices();
         $this->seedPortfolioCases();
         $this->seedTestimonials();
+        $this->call(WeddingPackagesSeeder::class);
     }
 
     private function seedSiteSettings(): void
@@ -56,6 +57,7 @@ class VisualContentSeeder extends Seeder
             'manifesto_body' => 'A Amare combina sensibilidade e precisão para criar encontros coerentes com cada cliente, marca e ocasião — sem fórmulas prontas, excessos ou ruído.',
             'method_intro' => 'Clareza em cada etapa. Tranquilidade durante todo o processo.',
             'method_steps' => SiteSetting::defaultMethodSteps(),
+            'corporate_steps' => SiteSetting::defaultCorporateSteps(),
             'principles' => SiteSetting::defaultPrinciples(),
             'email' => 'amareassessoriaeventos@gmail.com',
             'phone' => '(11) 99999-9999',
@@ -198,16 +200,22 @@ class VisualContentSeeder extends Seeder
      */
     private function writeSolidJpeg(string $destination, int $width, int $height, array $rgb): string
     {
+        $disk = Storage::disk('public');
+
+        if ($disk->exists($destination)) {
+            return $destination;
+        }
+
         $image = imagecreatetruecolor($width, $height);
         $color = imagecolorallocate($image, $rgb[0], $rgb[1], $rgb[2]);
         imagefilledrectangle($image, 0, 0, $width, $height, $color);
 
         ob_start();
-        imagejpeg($image, null, 90);
+        imagejpeg($image, null, 80);
         $binary = (string) ob_get_clean();
         imagedestroy($image);
 
-        Storage::disk('public')->put($destination, $binary);
+        $disk->put($destination, $binary);
 
         return $destination;
     }

database/seeders/WeddingPackagesSeeder.php

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

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

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

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

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

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

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

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

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

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

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

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

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

openspec/changes/archive/2026-08-11-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
-- [ ] 4.3 Stage only scoped files, commit conventionally, open a PR with screenshots and verification evidence, watch CI to green, merge and remove the worktree
+- [x] 4.3 Stage only scoped files, commit conventionally, open a PR with screenshots and verification evidence, watch CI to green, merge and remove the worktree — delivered in PR #22 with the requested screenshots and local verification; the PR merged as `0aee15e`, the worktree/remote branch no longer exists, and the current implementation is covered by all five green CI jobs on `main` (run 31501097667). Pixel snapshots were later removed by PR #44 and are not part of the current gate.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -0,0 +1,25 @@
+## 1. CMS and public content model
+
+- [x] 1.1 Add the typed official WhatsApp setting with migration, model/form validation and regression coverage.
+- [x] 1.2 Add the publishable, ordered WeddingPackage model, migration, factory, policy and Filament resource with failing-first coverage.
+- [x] 1.3 Add official Essenza, Conduzione and Grand Jour seed content and production-safe visual fixture gating.
+- [x] 1.4 Extend the public marketing query/data object to load wedding modalities and truthful acervo state.
+
+## 2. Proposal and partner boundaries
+
+- [x] 2.1 Move the existing event proposal request/form/mail route to `/briefing`, including prefilled modality interest.
+- [x] 2.2 Add the isolated partner inquiry request, controller, rate limit, honeypot, duplicate guard and dedicated mailable.
+- [x] 2.3 Cover each public form's validation, delivery, privacy copy, anti-spam path and absence of cross-flow mail/persistence.
+
+## 3. Editorial public journey
+
+- [x] 3.1 Recompose home chapters and stable anchors for Amare, directions, weddings, Corporate, acervo and testimonials.
+- [x] 3.2 Render published wedding modalities with contextual WhatsApp/fallback CTAs and keep Corporate proof-free.
+- [x] 3.3 Update navigation, footer and deep-route `/#chapter` links; preserve the services, portfolio, about and privacy deep dives.
+- [x] 3.4 Update `/servicos`, `/briefing` and `/contato` with the approved factual copy and Heritage Editorial form/layout treatment.
+
+## 4. Verification and handoff
+
+- [x] 4.1 Run the focused feature suite and static/formatting gates; fix all scoped regressions.
+- [x] 4.2 Run browser coverage at desktop and mobile, keyboard/axe and reduced-motion checks without visual snapshots.
+- [x] 4.3 Validate the OpenSpec change and update every completed task only with recorded verification evidence.

openspec/specs/container-runtime/spec.md

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

openspec/specs/content-media/spec.md

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

openspec/specs/design-tokens/spec.md

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

openspec/specs/health-check/spec.md

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

openspec/specs/internal-authentication/spec.md

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

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

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

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

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

openspec/specs/quality-gates/spec.md

@@ -70,3 +70,40 @@ The system SHALL execute browser tests using Pest Browser/Playwright against an
 
 - **WHEN** a browser test fails in CI
 - **THEN** the job MUST publish application logs and browser logs as diagnostics
+
+### Requirement: Quality gate includes npm dependency audit
+
+The system SHALL run an npm audit as part of the quality/static gate according to the project policy (SPEC §12.6, §13.9). Audit failure MUST block merge unless an explicit, documented exception exists.
+
+#### Scenario: Vulnerable dependency fails static gate
+
+- **WHEN** `npm audit` reports a policy-violating vulnerability in production dependencies
+- **THEN** the static/quality gate MUST fail and block merge
+
+#### Scenario: Developer runs quality locally with audit
+
+- **WHEN** a developer runs `composer quality` (or the documented npm audit step it requires)
+- **THEN** the npm audit MUST execute as part of the gate sequence
+
+### Requirement: Domain and Application maintain minimum coverage
+
+The CI unit gate SHALL measure code coverage for `App\Domain` and `App\Application` and MUST fail when either namespace falls below 80% (SPEC §13.7). Views, migrations, generated code, and framework code MUST NOT be required to meet this threshold.
+
+#### Scenario: Coverage drop below threshold blocks merge
+
+- **WHEN** Domain or Application coverage is below 80% on the unit CI job
+- **THEN** the job MUST fail
+
+#### Scenario: Coverage ignores non-domain layers
+
+- **WHEN** coverage is computed for the gate
+- **THEN** Blade views and migrations MUST NOT be counted toward the Domain/Application threshold
+
+### Requirement: Staging deploy job runs only after blocking CI jobs
+
+When deploying from `main`, the staging deploy workflow MUST require the five blocking CI jobs (`static`, `unit`, `feature`, `browser`, `container`) to succeed before building/pushing the image and triggering Dokploy (SPEC §14.1, §14.3).
+
+#### Scenario: Failed browser job prevents staging deploy
+
+- **WHEN** the `browser` CI job fails on `main`
+- **THEN** the staging deploy workflow MUST NOT promote a new image

openspec/specs/staging-deployment/spec.md

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

openspec/specs/testimonials/spec.md

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

openspec/specs/web-accessibility/spec.md

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

phpunit.xml

@@ -24,6 +24,7 @@
         </include>
     </source>
     <php>
+        <env name="APP_ENV" value="testing"/>
         <env name="APP_KEY" value="base64:NXm/6jIyFcDGHoMKGc5QZuSaq0dRZFYPg1Isuy1fNvE="/>
         <env name="APP_MAINTENANCE_DRIVER" value="file"/>
         <env name="BCRYPT_ROUNDS" value="4"/>

resources/css/app.css

@@ -22,6 +22,10 @@
     --text-display--line-height: 0.94;
     --text-display--letter-spacing: -0.01em;
 
+    --text-hero-spread: clamp(3rem, 5.5vw, 5rem);
+    --text-hero-spread--line-height: 0.94;
+    --text-hero-spread--letter-spacing: -0.01em;
+
     --text-headline: clamp(2.375rem, 5.2vw, 4rem);
     --text-headline--line-height: 1.02;
 

resources/views/components/home/briefing.blade.php

@@ -0,0 +1,250 @@
+@props([])
+
+<section
+    aria-labelledby="briefing-heading"
+    class="home-chapter border-b border-amare-border bg-amare-bg"
+    data-chapter="contato"
+    id="contato"
+>
+    <div class="container-amare grid gap-12 py-16 md:py-24 lg:grid-cols-[0.8fr_1.2fr] lg:gap-[80px]" data-reveal-group>
+        <div class="flex flex-col gap-6" data-reveal data-reveal-from="up">
+            <div class="space-y-4">
+                <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">07 — Briefing comercial</p>
+                <h2 id="briefing-heading" class="text-[clamp(2.375rem,5vw,4rem)] font-medium leading-[1.05] tracking-[-0.02em] text-amare-text">Conte sobre o evento que você está imaginando.</h2>
+            </div>
+            <p class="max-w-[760px] text-[clamp(1.1875rem,2vw,1.5rem)] leading-[1.55] text-amare-text-muted">Este formulário é para potenciais clientes. Ele continua existindo mesmo com os CTAs dos pacotes: são portas de entrada complementares.</p>
+            <p class="max-w-xl text-sm text-amare-muted">Para quem já sabe a modalidade, WhatsApp contextual. Para quem quer contextualizar o projeto, briefing. Para fornecedores/parcerias, outro fluxo.</p>
+        </div>
+
+        <form
+            method="POST"
+            action="{{ route('briefing.store') }}"
+            class="flex flex-col gap-[18px]"
+            data-contact-form
+            data-reveal
+            data-reveal-from="up"
+        >
+            @csrf
+
+            <div class="honeypot" aria-hidden="true">
+                <label for="empresa">Não preencha este campo</label>
+                <input type="text" id="empresa" name="empresa" tabindex="-1" autocomplete="off">
+            </div>
+
+            @if ($errors->any())
+                <div role="alert" class="border border-amare-error/40 bg-amare-error/5 px-6 py-5">
+                    <p class="font-semibold text-amare-error">Não foi possível enviar.</p>
+                    <p class="mt-1 text-sm text-amare-muted">Revise os campos destacados abaixo e tente novamente.</p>
+                </div>
+            @endif
+
+            <div class="grid gap-[18px] sm:grid-cols-2">
+                <div>
+                    <label for="briefing-nome" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Nome *</label>
+                    <input
+                        type="text"
+                        id="briefing-nome"
+                        name="nome"
+                        value="{{ old('nome') }}"
+                        required
+                        autocomplete="name"
+                        maxlength="120"
+                        placeholder="Seu nome"
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('nome') border-amare-error @enderror"
+                        @error('nome') aria-invalid="true" aria-describedby="briefing-nome-error" @enderror
+                    >
+                    @error('nome')
+                        <p id="briefing-nome-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+
+                <div>
+                    <label for="briefing-email" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">E-mail *</label>
+                    <input
+                        type="email"
+                        id="briefing-email"
+                        name="email"
+                        value="{{ old('email') }}"
+                        required
+                        autocomplete="email"
+                        maxlength="254"
+                        placeholder="voce@email.com"
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('email') border-amare-error @enderror"
+                        @error('email') aria-invalid="true" aria-describedby="briefing-email-error" @enderror
+                    >
+                    @error('email')
+                        <p id="briefing-email-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+
+                <div>
+                    <label for="briefing-telefone" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Telefone/WhatsApp *</label>
+                    <input
+                        type="tel"
+                        id="briefing-telefone"
+                        name="telefone"
+                        value="{{ old('telefone') }}"
+                        required
+                        autocomplete="tel"
+                        maxlength="40"
+                        placeholder="(11) 90000-0000"
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('telefone') border-amare-error @enderror"
+                        @error('telefone') aria-invalid="true" aria-describedby="briefing-telefone-error" @enderror
+                    >
+                    @error('telefone')
+                        <p id="briefing-telefone-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+
+                <div>
+                    <label for="briefing-tipo_evento" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Tipo de evento *</label>
+                    <select
+                        id="briefing-tipo_evento"
+                        name="tipo_evento"
+                        required
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors focus:border-amare-accent focus:outline-none @error('tipo_evento') border-amare-error @enderror"
+                        @error('tipo_evento') aria-invalid="true" aria-describedby="briefing-tipo_evento-error" @enderror
+                    >
+                        <option value="" selected disabled>Selecione...</option>
+                        <option value="Casamento" @selected(old('tipo_evento') === 'Casamento')>Casamento</option>
+                        <option value="Evento corporativo" @selected(old('tipo_evento') === 'Evento corporativo')>Evento corporativo</option>
+                        <option value="Celebração intimista" @selected(old('tipo_evento') === 'Celebração intimista')>Celebração intimista</option>
+                        <option value="Outro" @selected(old('tipo_evento') === 'Outro')>Outro tipo de evento</option>
+                    </select>
+                    @error('tipo_evento')
+                        <p id="briefing-tipo_evento-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+
+                <div>
+                    <label for="briefing-data_periodo" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Data ou período desejado</label>
+                    <input
+                        type="text"
+                        id="briefing-data_periodo"
+                        name="data_periodo"
+                        value="{{ old('data_periodo') }}"
+                        maxlength="80"
+                        placeholder="Ex.: novembro de 2027"
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('data_periodo') border-amare-error @enderror"
+                        @error('data_periodo') aria-invalid="true" aria-describedby="briefing-data_periodo-error" @enderror
+                    >
+                    @error('data_periodo')
+                        <p id="briefing-data_periodo-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+
+                <div>
+                    <label for="briefing-cidade" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Cidade do evento *</label>
+                    <input
+                        type="text"
+                        id="briefing-cidade"
+                        name="cidade"
+                        value="{{ old('cidade') }}"
+                        required
+                        maxlength="80"
+                        placeholder="Ex.: São Paulo"
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('cidade') border-amare-error @enderror"
+                        @error('cidade') aria-invalid="true" aria-describedby="briefing-cidade-error" @enderror
+                    >
+                    @error('cidade')
+                        <p id="briefing-cidade-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+
+                <div>
+                    <label for="briefing-convidados" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Número estimado de convidados</label>
+                    <input
+                        type="number"
+                        id="briefing-convidados"
+                        name="convidados"
+                        value="{{ old('convidados') }}"
+                        min="1"
+                        max="100000"
+                        inputmode="numeric"
+                        autocomplete="off"
+                        placeholder="Ex.: 120"
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('convidados') border-amare-error @enderror"
+                        @error('convidados') aria-invalid="true" aria-describedby="briefing-convidados-error" @enderror
+                    >
+                    @error('convidados')
+                        <p id="briefing-convidados-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+
+                <div>
+                    <label for="briefing-servico_interesse" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Serviço de interesse</label>
+                    <input
+                        type="text"
+                        id="briefing-servico_interesse"
+                        name="servico_interesse"
+                        value="{{ old('servico_interesse') }}"
+                        maxlength="120"
+                        placeholder="Ex.: planejamento completo"
+                        class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('servico_interesse') border-amare-error @enderror"
+                        @error('servico_interesse') aria-invalid="true" aria-describedby="briefing-servico_interesse-error" @enderror
+                    >
+                    @error('servico_interesse')
+                        <p id="briefing-servico_interesse-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                    @enderror
+                </div>
+            </div>
+
+            <div>
+                <label for="briefing-mensagem" class="mb-2 block text-xs font-bold uppercase tracking-[0.1em] text-amare-accent-deep">Mensagem / principal preocupação *</label>
+                <textarea
+                    id="briefing-mensagem"
+                    name="mensagem"
+                    required
+                    rows="5"
+                    maxlength="3000"
+                    placeholder="O que já está definido? Em que ponto você precisa de ajuda?"
+                    class="w-full min-h-[110px] border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('mensagem') border-amare-error @enderror"
+                    @error('mensagem') aria-invalid="true" aria-describedby="briefing-mensagem-error" @enderror
+                >{{ old('mensagem') }}</textarea>
+                @error('mensagem')
+                    <p id="briefing-mensagem-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                @enderror
+            </div>
+
+            <div>
+                <label for="briefing-privacidade" class="flex items-start gap-3 py-2">
+                    <input
+                        type="checkbox"
+                        id="briefing-privacidade"
+                        name="privacidade"
+                        value="1"
+                        required
+                        @checked(old('privacidade'))
+                        class="mt-1 h-5 w-5 shrink-0 accent-amare-accent"
+                        @error('privacidade') aria-invalid="true" aria-describedby="briefing-privacidade-error" @enderror
+                    >
+                    <span class="text-sm text-amare-muted">
+                        Li e aceito a
+                        <a href="{{ route('privacy') }}" class="text-amare-accent underline underline-offset-2 transition-colors hover:text-amare-accent-deep">política de privacidade</a>
+                        e autorizo o tratamento dos meus dados para fins de atendimento.*
+                    </span>
+                </label>
+                @error('privacidade')
+                    <p id="briefing-privacidade-error" class="mt-2 text-sm text-amare-error">{{ $message }}</p>
+                @enderror
+            </div>
+
+            <div class="flex flex-col items-start gap-4 pt-2">
+                <button
+                    type="submit"
+                    data-submit-button
+                    class="inline-flex min-h-[48px] items-center justify-center border border-transparent bg-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-text transition-colors hover:bg-amare-accent-deep"
+                >
+                    Enviar briefing
+                </button>
+                <p class="text-sm text-amare-muted">
+                    * Campos obrigatórios. Seus dados são usados apenas para responder à sua solicitação.
+                </p>
+            </div>
+
+            <div class="border border-dashed border-amare-sage px-6 py-5">
+                <p class="text-sm text-amare-muted">Fornecedores e parcerias — pós-MVP. Não misturar este público ao briefing comercial. Quando validado, criar um canal/formulário institucional próprio.</p>
+            </div>
+        </form>
+    </div>
+</section>

resources/views/components/home/corporate.blade.php

@@ -0,0 +1,45 @@
+@props([
+    'settings',
+])
+
+<section
+    aria-labelledby="corporate-heading"
+    class="home-chapter border-b border-amare-border bg-amare-bg"
+    data-chapter="corporate"
+    id="corporate"
+>
+    <div class="container-amare grid gap-12 py-16 md:py-24 lg:grid-cols-2 lg:gap-[70px]" data-reveal-group>
+        <div class="flex flex-col gap-8">
+            <div class="space-y-4" data-reveal data-reveal-from="up">
+                <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">04 — Amare Corporate</p>
+                <h2 id="corporate-heading" class="text-[clamp(2.375rem,5vw,4rem)] font-medium leading-[1.05] tracking-[-0.02em] text-amare-text">Projetos corporativos tratados como experiência, não apenas operação.</h2>
+            </div>
+
+            <p class="max-w-[760px] text-[clamp(1.1875rem,2vw,1.5rem)] leading-[1.55] text-amare-text-muted" data-reveal data-reveal-from="up">
+                No MVP, esta frente pode apresentar claramente o que a Amare oferece mesmo sem inventar um portfólio corporativo que ainda não existe.
+            </p>
+
+            <div class="border-t border-amare-border" data-reveal data-reveal-from="up">
+                @foreach ($settings->corporate_steps ?? [] as $index => $step)
+                    <div class="flex gap-8 border-b border-amare-border py-[23px]">
+                        <p class="w-[44px] shrink-0 text-xs font-bold uppercase tracking-[0.16em] text-amare-accent">{{ str_pad((string) ($index + 1), 2, '0', STR_PAD_LEFT) }}</p>
+                        <div class="space-y-1">
+                            <h3 class="text-xl font-medium text-amare-text">{{ $step['title'] }}</h3>
+                            <p class="text-amare-text-muted">{{ $step['body'] }}</p>
+                        </div>
+                    </div>
+                @endforeach
+            </div>
+
+            <a href="#contato" class="mt-7 inline-flex min-h-[48px] items-center justify-center self-start border border-transparent bg-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-text transition-colors hover:bg-amare-accent-deep" data-reveal data-reveal-from="up">
+                Falar sobre um evento corporativo
+            </a>
+        </div>
+
+        <div class="flex min-h-[420px] flex-col items-center justify-center gap-4 bg-amare-bg-deep p-10 text-center" data-reveal data-reveal-from="up">
+            <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">Portfólio Corporate</p>
+            <h3 class="text-[clamp(1.5625rem,2.7vw,2.125rem)] font-medium leading-tight text-amare-text">Conteúdo em construção</h3>
+            <p class="max-w-sm text-amare-text-muted">Em vez de usar fotografias genéricas como se fossem cases, a página assume com elegância que o portfólio será construído com projetos reais.</p>
+        </div>
+    </div>
+</section>

resources/views/components/home/final-cta.blade.php

@@ -17,7 +17,7 @@
         </p>
         <div>
             <a
-                href="{{ route('contact') }}"
+                href="{{ route('briefing') }}"
                 class="inline-flex min-h-11 items-center bg-amare-accent px-5 py-3 text-sm font-semibold uppercase tracking-[0.12em] text-amare-accent-text transition-colors duration-(--amare-duration-normal) ease-(--amare-ease-standard) hover:bg-amare-accent-deep"
             >
                 {{ $settings->hero_cta_label ?: 'Solicitar proposta' }}

resources/views/components/home/hero.blade.php

@@ -4,52 +4,46 @@
 
 <section
     aria-labelledby="hero-heading"
-    class="home-chapter min-h-[100dvh] border-b border-amare-border bg-amare-bg"
+    class="home-chapter border-b border-amare-border bg-amare-bg"
     data-chapter="hero"
     data-motion="page-open"
 >
-    <div @class([
+    <div class="container-amare grid items-end gap-12 pb-12 pt-16 md:grid-cols-[1.1fr_0.9fr] md:gap-[clamp(3rem,6vw,7rem)] md:pb-[72px] md:pt-24">
-        'container-amare grid min-h-[100dvh] gap-12 py-20 md:py-10',
+        <div data-hero-content data-reveal-group class="flex flex-col gap-8">
-        'md:grid-cols-[minmax(0,0.9fr)_minmax(0,1.1fr)] md:items-stretch' => filled($settings->hero_image_path),
+            <div data-motion-beat="eyebrow">
-        'md:max-w-4xl md:items-center' => blank($settings->hero_image_path),
+                <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">Assessoria &amp; produção de eventos &bull; São Paulo</p>
-    ]) data-reveal-group @if (blank($settings->hero_image_path)) data-tonal-hero @endif>
-        <div class="flex flex-col justify-center space-y-8 md:py-12">
-            <div data-motion-beat="seal" class="flex items-center gap-4">
-                <x-brand.logo mark variant="on-light" class="h-8 w-auto" alt="" />
-                @if (filled($settings->hero_eyebrow))
-                    <p class="text-sm font-medium uppercase tracking-[0.18em] text-amare-accent">{{ $settings->hero_eyebrow }}</p>
-                @endif
             </div>
 
-            <h1 id="hero-heading" data-motion-beat="title" class="max-w-3xl text-display font-medium text-amare-text">
+            <h1 id="hero-heading" data-motion-beat="title" class="text-[clamp(3rem,8vw,5.75rem)] font-medium leading-[0.95] tracking-[-0.04em] text-amare-text">
-                {{ $settings->hero_title ?: 'Celebrações com propósito' }}
+                Eventos com intenção, cuidado e presença.
             </h1>
 
-            @if (filled($settings->hero_subtitle))
+            <p class="max-w-[760px] text-[clamp(1.1875rem,2vw,1.5rem)] leading-[1.55] text-amare-text-muted">
-                <p class="max-w-2xl text-lg text-amare-text-muted">{{ $settings->hero_subtitle }}</p>
+                Uma boutique de assessoria que une sensibilidade, organização e condução profissional para transformar cada projeto em uma experiência bem cuidada.
-            @endif
+            </p>
 
             <div data-motion-beat="cta" class="flex flex-wrap items-center gap-4">
-                <a href="{{ route('contact') }}" data-testid="home-primary-cta" class="inline-flex min-h-11 items-center bg-amare-accent px-5 py-3 text-sm font-semibold text-amare-accent-text transition-colors duration-(--amare-duration-normal) ease-(--amare-ease-standard) hover:bg-amare-accent-hover">
+                <a href="#sobre" data-testid="home-primary-cta" class="inline-flex min-h-[48px] items-center justify-center border border-transparent bg-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-text transition-colors hover:bg-amare-accent-deep">
-                    {{ $settings->hero_cta_label ?: 'Solicitar proposta' }}
+                    Conhecer a Amare
+                </a>
+                <a href="#contato" class="inline-flex min-h-[48px] items-center justify-center border border-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-deep transition-colors hover:bg-amare-accent hover:text-amare-accent-text">
+                    Enviar briefing
                 </a>
-
-                @if (filled($settings->hero_secondary_cta_label))
-                    <a href="{{ route('portfolio.index') }}" class="inline-flex min-h-11 items-center text-sm font-semibold text-amare-accent transition-colors hover:text-amare-accent-deep">
-                        <span class="border-b border-amare-accent pb-1">{{ $settings->hero_secondary_cta_label }}</span>
-                    </a>
-                @endif
             </div>
-
-            @if (filled($settings->hero_note))
-                <p class="max-w-xl text-sm text-amare-text-muted">{{ $settings->hero_note }}</p>
-            @endif
         </div>
 
-        @if (filled($settings->hero_image_path))
+        <div
-            <div data-split-hero data-motion-beat="media" class="min-h-80 overflow-hidden bg-amare-bg-deep md:min-h-full" data-reveal-media>
+            data-split-hero
-                <x-media.image :path="$settings->hero_image_path" :alt="$settings->hero_image_alt ?: $settings->brand_name" loading="eager" fetchpriority="high" sizes="(max-width: 768px) 100vw, 55vw" class="img-editorial h-full w-full object-cover" />
+            data-motion-beat="media"
-            </div>
+            class="min-h-[320px] overflow-hidden bg-amare-bg-deep md:min-h-[520px]"
-        @endif
+        >
+            @if (filled($settings->hero_image_path))
+                <x-media.image :path="$settings->hero_image_path" :alt="$settings->hero_image_alt ?: $settings->brand_name" loading="eager" fetchpriority="high" sizes="(max-width: 1023px) 100vw, 45vw" class="img-editorial h-full w-full object-cover" />
+            @else
+                <div data-tonal-hero class="flex h-full min-h-[320px] items-center justify-center bg-gradient-to-br from-amare-bg-deep to-amare-bg-archive md:min-h-[520px]">
+                    <p class="text-xs font-semibold uppercase tracking-[0.16em] text-amare-muted">Fotografia hero</p>
+                </div>
+            @endif
+        </div>
     </div>
 </section>

resources/views/components/home/manifesto.blade.php

@@ -1,22 +1,24 @@
-@props([
+@props([])
-    'settings',
-])
 
-@php
+<section
-    $title = $settings->manifesto_title ?: 'Sofisticação que também se traduz em organização.';
+    aria-labelledby="manifesto-heading"
-    $lead = $settings->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.';
+    class="home-chapter border-b border-amare-border bg-amare-bg"
-    $body = $settings->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.';
+    data-chapter="sobre"
-@endphp
+    id="sobre"
-
+>
-<section aria-labelledby="manifesto-heading" class="home-chapter border-b border-amare-border bg-amare-bg-deep py-24 md:py-32" data-chapter="manifesto">
+    <div class="container-amare grid gap-10 py-16 md:grid-cols-[0.8fr_1.2fr] md:gap-[90px] md:py-24" data-reveal-group>
-    <div class="container-amare grid gap-10 md:grid-cols-12" data-reveal-group>
+        <div data-reveal data-reveal-from="up">
-        <div class="space-y-5 md:col-span-4 md:pt-20" data-reveal data-reveal-from="left">
+            <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">01 — A Amare</p>
-            <p class="max-w-52 text-lg leading-snug text-amare-text">Humana no cuidado. Precisa na entrega.</p>
         </div>
-        <div class="space-y-6 md:col-span-7 md:col-start-6" data-reveal data-reveal-from="up">
+
-            <h2 id="manifesto-heading" class="max-w-3xl text-headline font-medium text-amare-text">{{ $title }}</h2>
+        <div class="flex flex-col gap-8" data-reveal data-reveal-from="up">
-            <p class="max-w-2xl text-xl leading-relaxed text-amare-text">{{ $lead }}</p>
+            <h2 id="manifesto-heading" class="text-[clamp(1.875rem,4vw,3.25rem)] font-medium leading-[1.15] tracking-[-0.02em] text-amare-text">
-            <p class="max-w-2xl text-amare-text-muted">{{ $body }}</p>
+                Mais do que organizar um evento, a Amare conduz pessoas, decisões e detalhes para que cada experiência aconteça com clareza e tranquilidade.
+            </h2>
+
+            <p class="max-w-[760px] text-[clamp(1.1875rem,2vw,1.5rem)] leading-[1.55] text-amare-text-muted">
+                Aqui entra a apresentação institucional da marca e da Michele, com texto real aprovado pela cliente. A home deve construir confiança antes de pedir uma conversão.
+            </p>
         </div>
     </div>
 </section>

resources/views/components/home/packages.blade.php

@@ -0,0 +1,69 @@
+@props([
+    'packages',
+    'settings',
+])
+
+@php
+    $whatsappDigits = preg_replace('/\D/', '', (string) $settings->whatsapp_number);
+    $hasWhatsapp = strlen($whatsappDigits) >= 10;
+@endphp
+
+<section
+    aria-labelledby="packages-heading"
+    class="home-chapter border-b border-amare-border bg-amare-bg"
+    data-chapter="casamentos"
+    id="casamentos"
+>
+    <div class="container-amare py-16 md:py-24" data-reveal-group>
+        <div class="flex flex-col gap-6 md:flex-row md:items-end md:justify-between" data-reveal data-reveal-from="up">
+            <div class="max-w-2xl space-y-4">
+                <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">03 — Amare Casamentos</p>
+                <h2 id="packages-heading" class="text-[clamp(2.375rem,5vw,4rem)] font-medium leading-[1.05] tracking-[-0.02em] text-amare-text">Um acompanhamento para cada momento.</h2>
+            </div>
+            <p class="max-w-[600px] text-amare-text-muted">As modalidades são pontos de partida. O site apresenta o conceito e ajuda o casal a reconhecer seu momento; detalhes operacionais e comerciais ficam para a conversa e proposta.</p>
+        </div>
+
+        @if ($packages->isNotEmpty())
+            <div class="mt-12 grid border-l border-t border-amare-border md:mt-16 md:grid-cols-3">
+                @foreach ($packages as $package)
+                    <article class="flex min-h-[480px] flex-col justify-between gap-8 border-b border-r border-amare-border p-8 md:p-10" data-reveal data-reveal-from="up">
+                        <div class="space-y-5">
+                            <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent">{{ $package->level }}</p>
+                            <h3 class="text-[clamp(1.5625rem,2.7vw,2.125rem)] font-medium leading-tight text-amare-text">{{ $package->name }}</h3>
+                            <p class="text-amare-text-muted">{{ $package->summary }}</p>
+                            <ul class="space-y-3 text-amare-text-muted">
+                                @foreach ($package->scope_items as $item)
+                                    <li class="flex gap-3"><span aria-hidden="true" class="text-amare-accent">&bull;</span><span>{{ $item }}</span></li>
+                                @endforeach
+                            </ul>
+                        </div>
+                        @php
+                            $waLink = $hasWhatsapp
+                                ? 'https://wa.me/'.$whatsappDigits.'?text='.rawurlencode('Olá, gostaria de conversar sobre a modalidade '.$package->name.' para meu casamento.')
+                                : route('briefing', ['servico_interesse' => $package->name]);
+                        @endphp
+                        <a
+                            href="{{ $waLink }}"
+                            @if ($hasWhatsapp) target="_blank" rel="noopener noreferrer" @endif
+                            class="inline-flex min-h-[48px] items-center justify-center border border-transparent bg-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-text transition-colors hover:bg-amare-accent-deep"
+                        >
+                            {{ $package->cta_label }}
+                        </a>
+                    </article>
+                @endforeach
+            </div>
+        @endif
+
+        <div class="mt-6 flex flex-col justify-between gap-8 bg-amare-accent-deep p-8 text-amare-accent-text md:flex-row md:items-center md:p-12" data-reveal data-reveal-from="up">
+            <div class="max-w-xl space-y-3">
+                <h3 class="text-[clamp(1.5625rem,2.7vw,2.125rem)] font-medium leading-tight">Ainda não sabe qual modalidade é ideal?</h3>
+                <p class="text-amare-accent-text/80">Conte um pouco sobre o seu casamento. A Amare entende o momento de vocês e orienta o melhor formato de acompanhamento sem depender de um quiz automático.</p>
+            </div>
+            <a href="{{ route('briefing') }}" class="inline-flex min-h-[48px] items-center justify-center self-start border border-amare-accent-text px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-text transition-colors hover:bg-amare-accent-text hover:text-amare-accent-deep md:self-auto">
+                Conversar com a Amare
+            </a>
+        </div>
+
+        <p class="mt-6 text-sm text-amare-muted">Nomenclaturas exibidas conforme materiais/reunião; confirmar versão final antes da publicação.</p>
+    </div>
+</section>

resources/views/components/home/portfolio.blade.php

@@ -2,65 +2,55 @@
     'cases',
 ])
 
-@if ($cases->isNotEmpty())
+<section
-    <section aria-labelledby="portfolio-heading" class="home-chapter border-b border-amare-accent-deep bg-amare-accent-deep py-24 text-amare-accent-text" data-chapter="portfolio">
+    aria-labelledby="portfolio-heading"
-        <div class="container-amare space-y-10" data-reveal-group>
+    class="home-chapter border-b border-amare-border bg-amare-bg"
-            <div class="grid gap-4 md:grid-cols-12" data-reveal data-reveal-from="up">
+    data-chapter="portfolio"
-                <div class="md:col-span-7 md:col-start-5 space-y-3">
+    id="portfolio"
-                    <h2 id="portfolio-heading" class="text-headline font-medium">Celebrações que ganham forma com intenção.</h2>
+>
-                    <p class="max-w-2xl text-amare-accent-text/80">Recortes de eventos conduzidos com escuta, direção e presença em cada etapa.</p>
+    <div class="container-amare py-16 md:py-24" data-reveal-group>
-                </div>
+        <div class="flex flex-col gap-6 md:flex-row md:items-end md:justify-between" data-reveal data-reveal-from="up">
-            </div>
+            <h2 id="portfolio-heading" class="max-w-2xl text-[clamp(2.375rem,5vw,4rem)] font-medium leading-[1.05] tracking-[-0.02em] text-amare-text">Trabalhos que carregam a assinatura Amare.</h2>
-
+            <p class="max-w-[600px] text-amare-text-muted">Priorizar fotografias reais e uma curadoria pequena. O portfólio não precisa explicar tudo: deve provar cuidado, execução e consistência visual.</p>
-            <div class="grid gap-8 md:grid-cols-12 md:gap-x-8 md:gap-y-14" data-editorial-portfolio>
-                @foreach ($cases as $case)
-                    @php
-                        $isFeature = $loop->first;
-                        $isOffset = ! $isFeature && $loop->even;
-                    @endphp
-                    <article
-                        @class([
-                            'space-y-4 border-t border-amare-accent-text/30 pt-4',
-                            'md:col-span-7' => $isFeature,
-                            'md:col-span-5 md:col-start-8 md:pt-12' => $isOffset,
-                            'md:col-span-5' => ! $isFeature && ! $isOffset,
-                        ])
-                        data-editorial-portfolio-item="{{ $isFeature ? 'feature' : ($isOffset ? 'offset' : 'standard') }}"
-                        data-reveal
-                        data-reveal-from="up"
-                    >
-                        @if (filled($case->cover_image_path))
-                            <x-media.image
-                                :path="$case->cover_image_path"
-                                :alt="$case->cover_image_alt ?: $case->title"
-                                sizes="(max-width: 768px) calc(100vw - 3rem), 50vw"
-                                @class([
-                                    'img-editorial w-full object-cover',
-                                    'aspect-[5/4]' => $isFeature,
-                                    'aspect-[4/5]' => $isOffset,
-                                    'aspect-[4/3]' => ! $isFeature && ! $isOffset,
-                                ])
-                            />
-                        @endif
-                        <div class="space-y-2">
-                            <h3 class="text-2xl font-medium">{{ $case->title }}</h3>
-                            <p class="text-amare-accent-text/80">{{ $case->summary }}</p>
-                            <a href="{{ route('portfolio.show', $case->slug) }}" class="inline-flex min-h-11 items-center text-sm font-semibold transition-colors hover:text-amare-accent-text">
-                                <span class="border-b border-amare-accent-text pb-1">Ver caso</span>
-                            </a>
-                        </div>
-                    </article>
-                @endforeach
-            </div>
-
-            <div class="flex flex-col gap-4 border-t border-amare-accent-text/30 pt-5 md:flex-row md:items-end md:justify-between">
-                <p class="max-w-2xl text-sm text-amare-accent-text/75">
-                    Imagens demonstrativas enquanto o acervo autorizado da Amare está em organização.
-                </p>
-                <a href="{{ route('portfolio.index') }}" class="inline-flex min-h-11 items-center text-sm font-semibold transition-colors hover:text-amare-accent-text">
-                    <span class="border-b border-amare-accent-text pb-1">Conhecer o portfólio</span>
-                </a>
-            </div>
         </div>
-    </section>
+
-@endif
+        @php
+            $slots = collect([
+                ['label' => 'FOTO DE CASAMENTO 01', 'tall' => true],
+                ['label' => 'FOTO 02', 'tall' => false],
+                ['label' => 'FOTO 03', 'tall' => false],
+                ['label' => 'FOTO 04', 'tall' => false],
+                ['label' => 'FOTO 05', 'tall' => false],
+            ]);
+            $cases = $cases->take(5)->values();
+        @endphp
+
+        <div class="mt-12 grid grid-cols-1 gap-[14px] sm:grid-cols-2 lg:grid-cols-[1.2fr_0.8fr_0.8fr]" data-editorial-portfolio data-reveal-group>
+            @foreach ($slots as $index => $slot)
+                @php
+                    $case = $cases->get($index);
+                @endphp
+                <div
+                    @class([
+                        'overflow-hidden bg-amare-bg-deep',
+                        'sm:col-span-2 sm:min-h-[420px] lg:col-span-1 lg:row-span-2 lg:min-h-[634px]' => $slot['tall'],
+                        'min-h-[220px] sm:min-h-[310px]' => ! $slot['tall'],
+                    ])
+                    @if ($slot['tall']) data-editorial-portfolio-item="feature" @endif
+                    data-reveal
+                    data-reveal-from="up"
+                >
+                    @if ($case && filled($case->cover_image_path))
+                        <a href="{{ route('portfolio.show', $case) }}" class="block h-full w-full" aria-label="{{ $case->title }}">
+                            <x-media.image :path="$case->cover_image_path" :alt="$case->cover_image_alt ?: $case->title" sizes="(max-width: 1023px) 100vw, 33vw" class="img-editorial h-full w-full object-cover transition-opacity hover:opacity-90" />
+                        </a>
+                    @else
+                        <div class="flex h-full w-full items-center justify-center">
+                            <p class="px-4 text-center text-xs font-semibold uppercase tracking-[0.16em] text-amare-muted">{{ $slot['label'] }}</p>
+                        </div>
+                    @endif
+                </div>
+            @endforeach
+        </div>
+    </div>
+</section>

resources/views/components/home/services.blade.php

@@ -3,7 +3,7 @@
 ])
 
 @if ($services->isNotEmpty())
-    <section aria-labelledby="services-heading" class="home-chapter border-b border-amare-border py-24" data-chapter="services">
+    <section id="vertentes" aria-labelledby="services-heading" class="home-chapter border-b border-amare-border py-24" data-chapter="services">
         <div class="container-amare space-y-10" data-reveal-group>
             <div class="grid gap-6 md:grid-cols-12 md:items-end" data-reveal data-reveal-from="up">
                 <div class="space-y-3 md:col-span-4">

resources/views/components/home/testimonials.blade.php

@@ -3,46 +3,52 @@
 ])
 
 @php
-    $testimonials = $testimonials
+    $quotes = collect($testimonials)
-        ->filter(fn ($testimonial): bool => filled(trim((string) $testimonial->quote)))
+        ->filter(fn ($testimonial) => filled($testimonial->quote) && filled(trim((string) $testimonial->quote)))
+        ->take(3)
         ->values();
+    $cards = $quotes->map(fn ($testimonial) => [
+        'quote' => $testimonial->quote,
+        'author' => $testimonial->author_name,
+        'context' => $testimonial->context,
+    ])->all();
+    while (count($cards) < 3) {
+        $cards[] = [
+            'quote' => 'Depoimento real aprovado pela cliente entra aqui.',
+            'author' => 'Nome e data reais — aguardando autorização',
+            'context' => null,
+        ];
+    }
 @endphp
 
-@if ($testimonials->isNotEmpty())
+<section
-    <section aria-labelledby="testimonials-heading" class="home-chapter border-b border-amare-border bg-amare-bg py-24" data-chapter="testimonials">
+    aria-labelledby="testimonials-heading"
-        <div class="container-amare space-y-10" data-reveal-group>
+    class="home-chapter border-b border-amare-border bg-amare-bg"
-            <div class="max-w-2xl space-y-3 md:ml-[16.666667%]" data-reveal data-reveal-from="up">
+    data-chapter="depoimentos"
-                <h2 id="testimonials-heading" class="text-3xl font-medium text-amare-text">Depoimentos</h2>
+    id="depoimentos"
-                <p class="text-amare-text-muted">Quem celebrou com a Amare conta como foi a experiência.</p>
+>
-            </div>
+    <div class="container-amare py-16 md:py-24" data-reveal-group>
-
+        <div class="space-y-4" data-reveal data-reveal-from="up">
-            <div class="grid gap-6 md:grid-cols-12">
+            <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">06 — Depoimentos</p>
-                @foreach ($testimonials as $testimonial)
+            <h2 id="testimonials-heading" class="text-[clamp(2.375rem,5vw,4rem)] font-medium leading-[1.05] tracking-[-0.02em] text-amare-text">Confiança construída na experiência.</h2>
-                    @php
-                        $paragraphs = preg_split('/\n\s*\n/', trim((string) $testimonial->quote)) ?: [];
-                        $paragraphs = array_values(array_filter(array_map('trim', $paragraphs), fn (string $p): bool => $p !== ''));
-                    @endphp
-                    <blockquote @class([
-                        'space-y-4 border-t border-amare-border pt-4 md:col-span-5' => $loop->odd,
-                        'space-y-4 border-t border-amare-border pt-4 md:col-span-5 md:col-start-7 md:mt-16' => $loop->even,
-                    ]) data-reveal data-reveal-from="{{ $loop->odd ? 'left' : 'right' }}">
-                        <div class="grid grid-cols-[1.5rem_minmax(0,1fr)] gap-2">
-                            <span class="text-3xl leading-none text-amare-sage" aria-hidden="true">“</span>
-                            <div class="space-y-3 text-lg text-amare-text">
-                                @foreach ($paragraphs as $paragraph)
-                                    <p>{{ $paragraph }}</p>
-                                @endforeach
-                            </div>
-                        </div>
-                        <footer class="pl-8 text-sm text-amare-text-muted">
-                            <cite class="not-italic font-semibold text-amare-text">{{ $testimonial->author_name }}</cite>
-                            @if (filled($testimonial->context))
-                                <span> — {{ $testimonial->context }}</span>
-                            @endif
-                        </footer>
-                    </blockquote>
-                @endforeach
-            </div>
         </div>
-    </section>
+
-@endif
+        <div class="mt-12 grid gap-6 md:mt-16 md:grid-cols-3">
+            @foreach ($cards as $card)
+                <figure class="flex flex-col justify-between gap-6 border border-amare-border bg-white p-8" data-reveal data-reveal-from="up">
+                    <blockquote class="text-lg leading-[1.55] text-amare-text">
+                        <p>{{ $card['quote'] }}</p>
+                    </blockquote>
+                    <figcaption class="text-sm text-amare-muted">
+                        @if (filled($card['context']))
+                            <p class="font-semibold text-amare-text">{{ $card['author'] }}</p>
+                            <p>{{ $card['context'] }}</p>
+                        @else
+                            <p>{{ $card['author'] }}</p>
+                        @endif
+                    </figcaption>
+                </figure>
+            @endforeach
+        </div>
+    </div>
+</section>

resources/views/components/home/vertentes.blade.php

@@ -0,0 +1,41 @@
+@props([])
+
+<section
+    aria-labelledby="vertentes-heading"
+    class="home-chapter border-b border-amare-border bg-amare-bg"
+    data-chapter="vertentes"
+    id="vertentes"
+>
+    <div class="container-amare py-16 md:py-24" data-reveal-group>
+        <div class="max-w-3xl space-y-4" data-reveal data-reveal-from="up">
+            <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">02 — Duas vertentes, uma mesma forma de cuidar</p>
+            <h2 id="vertentes-heading" class="text-[clamp(2.375rem,5vw,4rem)] font-medium leading-[1.05] tracking-[-0.02em] text-amare-text">Como podemos acompanhar você?</h2>
+        </div>
+
+        <div class="mt-12 grid gap-6 md:mt-16 md:grid-cols-2 md:gap-[24px]">
+            <article class="relative flex min-h-[420px] flex-col justify-end bg-amare-bg-deep p-8 md:p-10" data-reveal data-reveal-from="up">
+                <div aria-hidden="true" class="pointer-events-none absolute inset-x-0 top-0 h-[43%] bg-gradient-to-b from-amare-bg to-transparent"></div>
+                <div class="relative flex flex-col gap-5">
+                    <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">Amare Casamentos</p>
+                    <h3 class="text-[clamp(1.5625rem,2.7vw,2.125rem)] font-medium leading-tight text-amare-text">Planejamento e condução para viver o processo com mais leveza.</h3>
+                    <p class="text-amare-text-muted">Do início da organização à reta final, modalidades pensadas para diferentes momentos do casal.</p>
+                    <a href="#casamentos" class="mt-2 inline-flex min-h-[48px] items-center justify-center self-start border border-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-deep transition-colors hover:bg-amare-accent hover:text-amare-accent-text">
+                        Conhecer casamentos
+                    </a>
+                </div>
+            </article>
+
+            <article class="relative flex min-h-[420px] flex-col justify-end bg-amare-bg-deep p-8 md:p-10" data-reveal data-reveal-from="up">
+                <div aria-hidden="true" class="pointer-events-none absolute inset-x-0 top-0 h-[43%] bg-gradient-to-b from-amare-bg to-transparent"></div>
+                <div class="relative flex flex-col gap-5">
+                    <p class="text-xs font-bold uppercase tracking-[0.16em] text-amare-accent-deep">Amare Corporate</p>
+                    <h3 class="text-[clamp(1.5625rem,2.7vw,2.125rem)] font-medium leading-tight text-amare-text">Eventos empresariais com organização, intenção e execução segura.</h3>
+                    <p class="text-amare-text-muted">Uma frente própria para projetos corporativos, com linguagem e necessidades diferentes das celebrações sociais.</p>
+                    <a href="#corporate" class="mt-2 inline-flex min-h-[48px] items-center justify-center self-start border border-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-deep transition-colors hover:bg-amare-accent hover:text-amare-accent-text">
+                        Conhecer Corporate
+                    </a>
+                </div>
+            </article>
+        </div>
+    </div>
+</section>

resources/views/components/home/wedding-packages.blade.php

@@ -0,0 +1,18 @@
+@props(['packages', 'settings'])
+
+<section id="casamentos" aria-labelledby="weddings-heading" class="home-chapter border-b border-amare-border bg-amare-bg-deep py-24" data-chapter="weddings">
+    <div class="container-amare space-y-10" data-reveal-group>
+        <div class="grid gap-6 md:grid-cols-12" data-reveal data-reveal-from="up"><div class="md:col-span-5"><p class="text-xs font-semibold uppercase tracking-[.14em] text-amare-accent">Casamentos</p><h2 id="weddings-heading" class="mt-3 text-headline font-medium">Uma condução à altura do que importa.</h2></div><p class="max-w-xl text-amare-muted md:col-span-5 md:col-start-7">Modalidades para diferentes momentos de planejamento, sempre construídas a partir do contexto de cada celebração.</p></div>
+        @if ($packages->isEmpty())
+            <p class="border-t border-amare-border pt-5 text-amare-muted">As modalidades de casamento estão em atualização. Conte-nos sobre o seu momento no briefing.</p>
+        @else
+            <ol class="grid gap-8 border-t border-amare-border pt-6 md:grid-cols-3">
+                @foreach ($packages as $package)
+                    @php($digits = preg_replace('/\D/', '', (string) $settings->whatsapp_number))
+                    @php($href = strlen((string) $digits) >= 10 ? 'https://wa.me/'.$digits.'?text='.rawurlencode('Olá, gostaria de conversar sobre a modalidade '.$package->name.' para meu casamento.') : route('briefing', ['servico_interesse' => $package->name]))
+                    <li class="space-y-5 border-t border-amare-border pt-4" data-reveal data-reveal-from="up"><p class="text-xs font-semibold uppercase tracking-[.14em] text-amare-accent">{{ $package->level }}</p><h3 class="text-3xl font-medium">{{ $package->name }}</h3><p class="text-amare-muted">{{ $package->summary }}</p><ul class="space-y-2 text-sm text-amare-text-muted">@foreach ($package->scope_items as $item)<li class="border-l border-amare-border pl-3">{{ $item }}</li>@endforeach</ul><a href="{{ $href }}" @if (str_starts_with($href, 'https://wa.me/')) target="_blank" rel="noopener" @endif class="inline-flex min-h-11 items-center text-sm font-semibold text-amare-accent hover:text-amare-accent-deep"><span class="border-b border-amare-accent pb-1">{{ $package->cta_label }}</span></a></li>
+                @endforeach
+            </ol>
+        @endif
+    </div>
+</section>

resources/views/components/public/photo-hero.blade.php

@@ -7,25 +7,16 @@
     'metadata' => null,
     'headingId' => 'hero-heading',
     'brandMark' => false,
+    'fullHeightFallback' => false,
 ])
 
 <section aria-labelledby="{{ $headingId }}" {{ $attributes->class(['border-b border-amare-border bg-amare-bg']) }} data-motion="page-open">
     @if (filled($imagePath))
-        <div class="relative flex min-h-[calc(100dvh-5.5rem)] items-end overflow-hidden" data-photo-hero>
+        <div class="grid min-h-[calc(100dvh-5rem)] lg:h-[calc(100dvh-5rem)] lg:min-h-0 lg:grid-cols-12" data-photo-hero>
-            <x-media.image
+            <div class="flex min-w-0 items-center bg-amare-bg px-6 py-16 lg:col-span-5 lg:px-[clamp(3rem,6vw,7rem)]" data-hero-content data-reveal-group>
-                :path="$imagePath"
+                <div class="w-full max-w-[470px] space-y-7">
-                :alt="$imageAlt ?: $title"
-                loading="eager"
-                fetchpriority="high"
-                sizes="100vw"
-                class="img-editorial absolute inset-0 h-full w-full object-cover"
-                data-motion-beat="media"
-            />
-
-            <div class="container-amare relative z-10 w-full py-8 md:py-12">
-                <div class="max-w-3xl border border-amare-border bg-amare-bg p-6 text-amare-text md:p-10" data-motion-beat="heading">
                     @if ($brandMark || filled($eyebrow))
-                        <div class="mb-5 flex items-center gap-4" data-motion-beat="seal">
+                        <div class="flex items-center gap-4" data-motion-beat="seal">
                             @if ($brandMark)
                                 <x-brand.logo mark variant="on-light" class="h-8 w-auto" alt="" />
                             @endif
@@ -34,22 +25,36 @@
                             @endif
                         </div>
                     @endif
-                    <h1 id="{{ $headingId }}" data-motion-beat="title" class="max-w-3xl text-display font-medium text-amare-text">{{ $title }}</h1>
+                    <h1 id="{{ $headingId }}" data-motion-beat="title" class="max-w-[470px] whitespace-normal break-normal text-hero-spread font-medium text-amare-text">{{ $title }}</h1>
                     @if (filled($summary))
-                        <p class="mt-5 max-w-2xl text-lg text-amare-text-muted">{{ $summary }}</p>
+                        <p class="max-w-[470px] text-lg text-amare-text-muted">{{ $summary }}</p>
                     @endif
                     @if (filled($metadata))
-                        <p class="mt-4 text-sm break-words text-amare-text-muted">{{ $metadata }}</p>
+                        <p class="max-w-[470px] text-sm break-words text-amare-text-muted">{{ $metadata }}</p>
                     @endif
                     @if (trim((string) $slot) !== '')
-                        <div class="mt-7" data-motion-beat="cta">{{ $slot }}</div>
+                        <div data-motion-beat="cta">{{ $slot }}</div>
                     @endif
                 </div>
             </div>
+
+            <div data-split-hero data-motion-beat="media" class="min-h-[56dvh] overflow-hidden bg-amare-bg-deep max-lg:aspect-[4/5] lg:col-span-7 lg:min-h-0" data-reveal-media>
+                <x-media.image
+                    :path="$imagePath"
+                    :alt="$imageAlt ?: $title"
+                    loading="eager"
+                    fetchpriority="high"
+                    sizes="(max-width: 1023px) 100vw, 58vw"
+                    class="img-editorial h-full w-full object-cover"
+                />
+            </div>
         </div>
     @else
-        <div class="container-amare py-16 md:py-24" data-tonal-hero>
+        <div @class([
-            <div class="max-w-3xl space-y-4" data-motion-beat="heading">
+            'container-amare py-16 md:py-24',
+            'min-h-[100dvh]' => $fullHeightFallback,
+        ]) data-tonal-hero>
+            <div class="max-w-[470px] space-y-4" data-motion-beat="heading">
                 @if ($brandMark || filled($eyebrow))
                     <div class="flex items-center gap-4" data-motion-beat="seal">
                         @if ($brandMark)
@@ -60,12 +65,12 @@
                         @endif
                     </div>
                 @endif
-                <h1 id="{{ $headingId }}" data-motion-beat="title" class="text-headline font-medium tracking-tight text-amare-text">{{ $title }}</h1>
+                <h1 id="{{ $headingId }}" data-motion-beat="title" class="max-w-[470px] whitespace-normal break-normal text-headline font-medium tracking-tight text-amare-text">{{ $title }}</h1>
                 @if (filled($summary))
-                    <p class="text-lg text-amare-muted">{{ $summary }}</p>
+                    <p class="max-w-[470px] text-lg text-amare-muted">{{ $summary }}</p>
                 @endif
                 @if (filled($metadata))
-                    <p class="text-sm break-words text-amare-muted">{{ $metadata }}</p>
+                    <p class="max-w-[470px] text-sm break-words text-amare-muted">{{ $metadata }}</p>
                 @endif
                 @if (trim((string) $slot) !== '')
                     <div data-motion-beat="cta">{{ $slot }}</div>

resources/views/emails/partner-inquiry-text.blade.php

@@ -0,0 +1,5 @@
+Nova consulta de fornecedor ou parceria
+
+@foreach ($fields as $label => $value)
+{{ $label }}: {{ $value ?: '—' }}
+@endforeach

resources/views/emails/partner-inquiry.blade.php

@@ -0,0 +1,10 @@
+<!DOCTYPE html>
+<html lang="pt-BR"><head><meta charset="utf-8"><title>Nova consulta de parceria</title></head>
+<body>
+    <h1>Nova consulta de fornecedor ou parceria</h1>
+    <table>
+        @foreach ($fields as $label => $value)
+            <tr><th scope="row">{{ $label }}</th><td>{{ $value ?: '—' }}</td></tr>
+        @endforeach
+    </table>
+</body></html>

resources/views/layouts/public.blade.php

@@ -55,23 +55,23 @@
         Ir para o conteúdo
     </a>
 
-    <header class="site-header sticky top-0 z-40 border-b border-amare-border/80 bg-amare-bg/90 backdrop-blur-sm">
+    <header class="site-header sticky top-0 z-40 border-b border-amare-border bg-amare-bg/95 backdrop-blur-sm">
-        <div class="container-amare grid grid-cols-[auto_1fr_auto] items-center gap-4 py-4 md:grid-cols-[1fr_auto_1fr]">
+        <div class="container-amare grid grid-cols-[auto_1fr_auto] items-center gap-4 py-4 md:grid-cols-[1fr_auto_1fr] md:h-[74px] md:py-0">
             <nav id="main-nav" class="main-nav order-3 col-span-3 hidden flex-col gap-4 border-t border-amare-border pt-4 md:order-1 md:col-span-1 md:flex md:flex-row md:items-center md:gap-1 md:border-0 md:pt-0" aria-label="Principal" data-main-nav>
-                <a href="{{ route('home') }}" class="inline-flex items-center py-3 text-sm font-semibold uppercase tracking-[0.12em] text-amare-muted transition-colors hover:text-amare-accent md:px-2">Início</a>
+                <a href="{{ route('home') }}" class="inline-flex items-center py-3 text-[13px] font-semibold uppercase tracking-[0.08em] text-amare-muted transition-colors hover:text-amare-accent md:px-3">Início</a>
-                <a href="{{ route('services.index') }}" class="inline-flex items-center py-3 text-sm font-semibold uppercase tracking-[0.12em] text-amare-muted transition-colors hover:text-amare-accent md:px-2">Serviços</a>
+                <a href="{{ route('services.index') }}" class="inline-flex items-center py-3 text-[13px] font-semibold uppercase tracking-[0.08em] text-amare-muted transition-colors hover:text-amare-accent md:px-3">Serviços</a>
-                <a href="{{ route('portfolio.index') }}" class="inline-flex items-center py-3 text-sm font-semibold uppercase tracking-[0.12em] text-amare-muted transition-colors hover:text-amare-accent md:px-2">Portfólio</a>
+                <a href="{{ route('portfolio.index') }}" class="inline-flex items-center py-3 text-[13px] font-semibold uppercase tracking-[0.08em] text-amare-muted transition-colors hover:text-amare-accent md:px-3">Portfólio</a>
-                <a href="{{ route('about') }}" class="inline-flex items-center py-3 text-sm font-semibold uppercase tracking-[0.12em] text-amare-muted transition-colors hover:text-amare-accent md:px-2">Amare</a>
+                <a href="{{ route('about') }}" class="inline-flex items-center py-3 text-[13px] font-semibold uppercase tracking-[0.08em] text-amare-muted transition-colors hover:text-amare-accent md:px-3">Amare</a>
-                <a href="{{ route('contact') }}" class="inline-flex items-center py-3 text-sm font-semibold uppercase tracking-[0.12em] text-amare-muted transition-colors hover:text-amare-accent md:hidden">Solicitar proposta</a>
+                <a href="{{ route('briefing') }}" class="inline-flex items-center py-3 text-[13px] font-semibold uppercase tracking-[0.08em] text-amare-muted transition-colors hover:text-amare-accent md:hidden">Solicitar proposta</a>
             </nav>
 
             <a href="{{ route('home') }}" class="order-1 justify-self-start md:order-2 md:justify-self-center" aria-label="{{ $siteSettings->brand_name }} — página inicial">
-                <x-brand.logo variant="on-light" class="h-10 w-auto md:h-12" />
+                <x-brand.logo variant="on-light" class="h-10 w-auto md:h-11" />
             </a>
 
             <div class="order-2 flex items-center justify-end gap-3 md:order-3">
-                <a href="{{ route('contact') }}" class="hidden items-center py-3 text-sm font-semibold uppercase tracking-[0.12em] text-amare-accent transition-colors hover:text-amare-accent-deep md:inline-flex">
+                <a href="{{ route('briefing') }}" class="hidden items-center justify-center border border-amare-accent px-6 text-xs font-bold uppercase tracking-[0.09em] text-amare-accent-deep transition-colors hover:bg-amare-accent hover:text-amare-accent-text md:inline-flex min-h-[48px]">
-                    Solicitar proposta
+                    Conte seu evento
                 </a>
 
                 <button
@@ -97,50 +97,34 @@
         @yield('content')
     </main>
 
-    <footer class="border-t border-amare-border bg-amare-bg-deep">
+    <footer class="border-t border-amare-border bg-amare-bg">
-        <div class="container-amare grid gap-10 py-12 md:grid-cols-[minmax(0,1.4fr)_repeat(2,minmax(0,1fr))]">
+        @php
-            <div class="space-y-4">
+            $footerSocialLabel = static function (string $network): string {
-                <x-brand.logo variant="on-light" class="h-12 w-auto" />
+                return match ($network) {
-                <p class="max-w-md text-amare-muted">
+                    'instagram' => 'Instagram',
-                    {{ $siteSettings->about_summary ?: 'Assessoria boutique em São Paulo - SP.' }}
+                    'whatsapp' => 'WhatsApp',
-                </p>
+                    'linkedin' => 'LinkedIn',
+                    default => ucfirst($network),
+                };
+            };
+            $footerSocials = collect($siteSettings->social_links ?? [])->filter(static fn ($url) => filled($url));
+        @endphp
+
+        <div class="container-amare flex flex-col gap-8 py-14 md:flex-row md:items-end md:justify-between md:py-[58px]">
+            <div class="space-y-3">
+                <x-brand.logo variant="on-light" class="h-10 w-auto" />
+                <p class="text-sm text-amare-muted">Assessoria &amp; produção de eventos &bull; São Paulo</p>
             </div>
 
-            <div class="text-sm">
+            <p class="text-sm text-amare-muted md:text-right">
-                <h2 class="text-xs font-semibold uppercase tracking-[0.14em] text-amare-text">Navegação</h2>
+                @if ($footerSocials->isEmpty())
-                <ul class="mt-3 space-y-3">
+                    Instagram &middot; WhatsApp &middot; E-mail &middot; LinkedIn (quando confirmado)
-                    <li><a href="{{ route('services.index') }}" class="inline-flex min-h-11 items-center text-amare-muted transition-colors hover:text-amare-accent">Serviços</a></li>
+                @else
-                    <li><a href="{{ route('portfolio.index') }}" class="inline-flex min-h-11 items-center text-amare-muted transition-colors hover:text-amare-accent">Portfólio</a></li>
+                    @foreach ($footerSocials as $network => $url)
-                    <li><a href="{{ route('about') }}" class="inline-flex min-h-11 items-center text-amare-muted transition-colors hover:text-amare-accent">A Amare</a></li>
+                        <a href="{{ $url }}" class="inline-flex min-h-11 items-center transition-colors hover:text-amare-accent" rel="noopener noreferrer" target="_blank">{{ $footerSocialLabel((string) $network) }}</a>@unless ($loop->last) &nbsp;&middot;&nbsp; @endunless
-                    <li><a href="{{ route('contact') }}" class="inline-flex min-h-11 items-center text-amare-muted transition-colors hover:text-amare-accent">Contato</a></li>
-                </ul>
-            </div>
-
-            <div class="text-sm">
-                <h2 class="text-xs font-semibold uppercase tracking-[0.14em] text-amare-text">Contato</h2>
-                <address class="mt-3 space-y-3 not-italic">
-                    @if ($siteSettings->city)
-                        <p class="text-amare-muted">{{ $siteSettings->city }}</p>
-                    @endif
-                    @if ($siteSettings->email)
-                        <p>
-                            <a href="mailto:{{ $siteSettings->email }}" class="inline-flex max-w-full min-h-11 items-center text-amare-muted transition-colors hover:text-amare-accent"><span class="min-w-0 break-words">{{ $siteSettings->email }}</span></a>
-                        </p>
-                    @endif
-                    @if ($siteSettings->phone)
-                        <p>
-                            <a href="tel:{{ preg_replace('/\D/', '', (string) $siteSettings->phone) }}" class="inline-flex max-w-full min-h-11 items-center text-amare-muted transition-colors hover:text-amare-accent"><span class="min-w-0 break-words">{{ $siteSettings->phone }}</span></a>
-                        </p>
-                    @endif
-                    @foreach ($siteSettings->social_links ?? [] as $network => $url)
-                        @if (filled($url))
-                            <p>
-                                <a href="{{ $url }}" class="inline-flex max-w-full min-h-11 items-center text-amare-muted transition-colors hover:text-amare-accent" rel="noopener noreferrer" target="_blank"><span class="min-w-0 break-words">{{ ucfirst((string) $network) }}</span></a>
-                            </p>
-                        @endif
                     @endforeach
-                </address>
+                @endif
-            </div>
+            </p>
         </div>
 
         <div class="border-t border-amare-border">

resources/views/pages/contact.blade.php

@@ -49,7 +49,7 @@
             @else
                 <form
                     method="POST"
-                    action="{{ route('contact.store') }}"
+                    action="{{ route('briefing.store') }}"
                     class="mt-10 max-w-3xl space-y-10"
                     data-contact-form
                 >
@@ -135,8 +135,8 @@
                                 @error('tipo_evento') aria-invalid="true" aria-describedby="tipo_evento-error" @enderror
                             >
                                 <option value="" selected disabled>Selecione...</option>
-                                <option value="Casamento" @selected(old('tipo_evento') === 'Casamento')>Casamento</option>
+                                <option value="Casamento" @selected(old('tipo_evento', request('tipo_evento')) === 'Casamento')>Casamento</option>
-                                <option value="Evento corporativo" @selected(old('tipo_evento') === 'Evento corporativo')>Evento corporativo</option>
+                                <option value="Evento corporativo" @selected(old('tipo_evento', request('tipo_evento')) === 'Evento corporativo')>Evento corporativo</option>
                                 <option value="Celebração intimista" @selected(old('tipo_evento') === 'Celebração intimista')>Celebração intimista</option>
                                 <option value="Outro" @selected(old('tipo_evento') === 'Outro')>Outro tipo de evento</option>
                             </select>
@@ -206,7 +206,7 @@
                                 type="text"
                                 id="servico_interesse"
                                 name="servico_interesse"
-                                value="{{ old('servico_interesse') }}"
+                                value="{{ old('servico_interesse', request('servico_interesse')) }}"
                                 maxlength="120"
                                 placeholder="Ex.: planejamento completo"
                                 class="w-full border-0 border-b border-amare-border bg-transparent py-3 text-amare-text transition-colors placeholder:text-amare-muted/60 focus:border-amare-accent focus:outline-none @error('servico_interesse') border-amare-error @enderror"

resources/views/pages/home.blade.php

@@ -3,12 +3,12 @@
 @section('content')
     <div class="home-chapters">
         <x-home.hero :settings="$content->settings" />
-        <x-home.manifesto :settings="$content->settings" />
+        <x-home.manifesto />
-        <x-home.services :services="$content->featuredServices" />
+        <x-home.vertentes />
+        <x-home.packages :packages="$content->packages" :settings="$content->settings" />
+        <x-home.corporate :settings="$content->settings" />
         <x-home.portfolio :cases="$content->featuredCases" />
-        <x-home.method :settings="$content->settings" />
         <x-home.testimonials :testimonials="$content->testimonials" />
-        <x-home.positioning :settings="$content->settings" />
+        <x-home.briefing />
-        <x-home.final-cta :settings="$content->settings" editorial />
     </div>
 @endsection

resources/views/pages/partners.blade.php

@@ -0,0 +1,41 @@
+@extends('layouts.public')
+
+@section('content')
+    <section class="border-b border-amare-border bg-amare-bg" data-motion="page-open">
+        <div class="container-amare grid gap-12 py-16 md:grid-cols-[1.15fr_.85fr] md:py-24" data-reveal-group>
+            <div class="space-y-6" data-motion-beat="heading" data-reveal data-reveal-from="up">
+                <p class="text-xs font-semibold uppercase tracking-[0.14em] text-amare-accent">Contato profissional</p>
+                <h1 class="text-headline font-medium tracking-tight text-amare-text">Fornecedores e parcerias</h1>
+                <p class="max-w-2xl text-lg text-amare-muted">Se o seu trabalho conversa com a forma de atuar da Amare, apresente-se. Usaremos suas informações somente para avaliar uma possível relação profissional.</p>
+            </div>
+            <div class="border-t border-amare-border pt-6 text-amare-muted md:border-l md:border-t-0 md:pl-10 md:pt-0" data-reveal data-reveal-from="up">
+                <p>{{ $siteSettings->city ?: 'São Paulo - SP' }}</p>
+                @if ($siteSettings->email)<a class="mt-3 inline-flex min-h-11 items-center text-amare-accent underline hover:text-amare-accent-deep" href="mailto:{{ $siteSettings->email }}">{{ $siteSettings->email }}</a>@endif
+                <p class="mt-5 text-sm">Para solicitar uma proposta para um evento, use o <a class="text-amare-accent underline" href="{{ route('briefing') }}">briefing</a>.</p>
+            </div>
+        </div>
+    </section>
+
+    <section class="border-b border-amare-border bg-amare-bg-deep" aria-labelledby="partner-form-heading">
+        <div class="container-amare py-16 md:py-24" data-reveal-group>
+            <h2 id="partner-form-heading" class="text-3xl font-medium text-amare-text" data-reveal data-reveal-from="up">Apresente seu trabalho</h2>
+            @if (session('status') === 'partner-inquiry-sent')
+                <div role="status" class="mt-8 border border-amare-border bg-amare-bg px-6 py-5"><p class="font-semibold">Mensagem enviada.</p><p class="mt-1 text-amare-muted">Recebemos sua apresentação e entraremos em contato se houver aderência.</p></div>
+            @else
+                <form method="POST" action="{{ route('contact.store') }}" class="mt-10 max-w-3xl space-y-8" data-contact-form data-reveal data-reveal-from="up">
+                    @csrf
+                    <div class="honeypot" aria-hidden="true"><label for="website">Não preencha este campo</label><input id="website" name="website" tabindex="-1" autocomplete="off"></div>
+                    @if ($errors->any())<div role="alert" class="border border-amare-error/40 px-6 py-5">Revise os campos destacados abaixo.</div>@endif
+                    <div class="grid gap-8 sm:grid-cols-2">
+                        @foreach (['nome' => 'Nome *', 'empresa' => 'Nome profissional ou empresa', 'email' => 'E-mail *', 'atuacao' => 'Atuação ou serviço *', 'area_atendimento' => 'Área de atendimento *', 'portfolio_redes' => 'Portfólio ou redes', 'telefone' => 'Telefone'] as $field => $label)
+                            <div><label class="mb-2 block text-xs font-semibold uppercase tracking-[.14em]" for="{{ $field }}">{{ $label }}</label><input class="w-full border-0 border-b border-amare-border bg-transparent py-3 focus:border-amare-accent focus:outline-none @error($field) border-amare-error @enderror" id="{{ $field }}" name="{{ $field }}" value="{{ old($field) }}" maxlength="{{ $field === 'portfolio_redes' ? 500 : ($field === 'email' ? 254 : 160) }}" @required(in_array($field, ['nome','email','atuacao','area_atendimento'], true)) @error($field) aria-invalid="true" @enderror>@error($field)<p class="mt-2 text-sm text-amare-error">{{ $message }}</p>@enderror</div>
+                        @endforeach
+                    </div>
+                    <div><label class="mb-2 block text-xs font-semibold uppercase tracking-[.14em]" for="mensagem">Mensagem *</label><textarea class="w-full border border-amare-border bg-transparent p-3 focus:border-amare-accent focus:outline-none" id="mensagem" name="mensagem" rows="6" required maxlength="3000">{{ old('mensagem') }}</textarea>@error('mensagem')<p class="mt-2 text-sm text-amare-error">{{ $message }}</p>@enderror</div>
+                    <p class="max-w-2xl text-sm text-amare-muted">Ao enviar, você reconhece o uso destes dados exclusivamente para analisar uma possível parceria, conforme a <a class="text-amare-accent underline" href="{{ route('privacy') }}">política de privacidade</a>.</p>
+                    <button type="submit" data-submit-button class="inline-flex min-h-11 bg-amare-accent px-6 py-3 text-sm font-semibold uppercase tracking-[.12em] text-amare-accent-text hover:bg-amare-accent-deep">Enviar apresentação</button>
+                </form>
+            @endif
+        </div>
+    </section>
+@endsection