<!-- LOVABLE:BEGIN -->
> [!IMPORTANT]
> This project is connected to [Lovable](https://lovable.dev). Avoid rewriting
> published git history — force pushing, or rebasing/amending/squashing commits
> that are already pushed — as it rewrites history on Lovable's side and the
> user will likely lose their project history.
>
> Commits you push to the connected branch sync back to Lovable and show up in
> the editor, so keep the branch in a working state.

## What Lovable manages

Rules outside this block are the project's own. Change the pieces below in
Lovable, not by hand. With the [Lovable MCP](https://mcp.lovable.dev)
connected, `send_message` asks Lovable to do it; otherwise ask the user to
use the editor.

- **Database.** Do not add or edit `supabase/migrations/` or `drizzle/`.
  Ask Lovable to change the schema.
- **Generated files.** Do not edit a file whose header says it is automatically
  generated.
- **AI gateway.** Keep model calls on Lovable's gateway, and keep
  `LOVABLE_API_KEY` out of browser code.
- **Connectors.** Lovable provides native connectors. `list_connectors` shows
  which are enabled; `add_connector` only returns the dashboard link. When a
  connector is enabled, calls go through the connector gateway and need
  `LOVABLE_API_KEY`. When Lovable does not provide one, users can bring their
  own key and store it in Secrets.
- **Secrets.** Lovable manages them. Do not put secret values in the repo.
<!-- LOVABLE:END -->

- Keep reusable agency sections, layout, and inquiry controls in src/components; content routes own metadata and page composition so pages remain independently navigable.
- Keep the service catalog and domain-name validation in src/lib/agency.ts so links and validation share one source of truth.
- Use GSAP in an effect with matchMedia and cleanup; respect reduced-motion preferences and keep animation imports safe for SSR.
- Never report an inquiry as sent until a secure email service confirms it; pending email setup uses explicitly labeled direct email/WhatsApp handoff.
- Mount one persistent Canvas galaxy in the shared shell and dynamically import Three.js inside the spacecraft effect; dispose graphics, observers, and timelines on unmount to keep SSR and navigation safe.
- Keep demonstration portfolio assets separately identified from client work; never convert generated concepts into claimed commissions or testimonials.
