observability-baseline

stack-baseline names Sentry and wires it nowhere — so every shipped product's first prod incident is invisible, and l3-support triages blind. This skill makes three things exist at scaffold time. Defaults baked in; no founder question.

1. Error capture (Sentry)

• instrumentation.ts (Next.js) / SDK init at process start; DSN from SENTRY_DSN env (never hardcoded).
• CI uploads source maps on release so stack traces are readable (release = git sha).
• Capture unhandled rejections + a global error boundary on the client.

2. Request-id structured logging