Marketing site and landing page

Implementation

• Public marketing at `/` with the same header and footer chrome as today’s landing experience; primary CTAs target `/app`.
• No pricing surfaces—the product is free; do not add a pricing page or paid-tier messaging.
• Planned production host is `herosheet.bybear.dk`. Visible branding keeps **Hero Sheet** as the name; parent domain appears as a quiet postfix (e.g. muted `bybear.dk`), not loud “marketing shout” treatment.
• Stub routes until later tasks flesh them out—`/app` (non-breaking placeholder for the signed-in experience), `/privacy`, `/terms` (placeholder legal copy). No dedicated `/about`; deeper product narrative and specification live under **Product** at `/product`; the task roadmap lives at `/roadmap` (retire standalone `/spec` and `/tasks` URLs in favor of those paths).
• **Header nav**: only one product entry—link label **Product** pointing to `/product`. No separate header links for spec vs roadmap.
• **Landing copy**: hero and section text on `/` are **marketing prose** maintained for the landing page (length, tone, CTAs). Factual claims and feature descriptions must **not contradict** the Product spec at `/product`; prefer linking into `/product` for detail rather than pasting diverging spec blocks on `/`.
• **Footer internal reports**: show links to internal HTML reports **only in development** builds; **hide entirely** on the public production deploy (same host behavior as “dev-only chrome”).
• Reuse Skeleton + Tailwind (Cerberus) tokens; full responsive layout per AGENTS.md.

Questions

None yet.