Epic: Projects & Per-project Settings (script tag + error-tracking DSN)

Each project Settings centers on the two essentials: the analytics script tag and the error-tracking API key (DSN).

Tracks (4):

• #63 — Settings: focus per-project Settings on the two essentials (script tag + DSN/API key)
• #64 — Settings: error-tracking API key as a Sentry-style DSN (copy, regenerate, scope)
• #65 — Settings: analytics script panel polish (what is tracked + verify)
• #66 — Settings: gate non-functional extras behind "coming soon" until their jobs run

Part of the Fathom + Sentry product backlog. See #44 for the original roadmap.

All four tracks shipped — closing the epic.

• #64 — Sentry-style DSN endpoint (GET /api/sites/{siteId}/dsn) with an ingest-only scoped key
• #63 — Settings leads with the two essentials: the analytics one-liner, then a copyable Error Tracking panel (DSN + standalone SDK snippet)
• #65 — install panel is self-explanatory: privacy line + capture chips (page views, SPA routes, clicks, engagement, vitals, JS errors) + the Verify installation button (#84)
• #66 — webhook form fixed to send valid event names, alert.triggered wired through the signed delivery queue, unsent events gated as coming soon; the rest was overtaken by the jobs runtime (#110)

Opening a project's Settings, a new user can copy the script tag and the DSN without hunting — the epic's done-when.