observability-baseline

To add observability, the skill integrates Sentry for error capture and implements request-id structured logging during new product setups, ensuring diagnostic traceability from day one.

Production readiness requires liveness and readiness checks, which this skill provides by setting up standard `/healthz` and `/readyz` endpoints for infrastructure monitoring.

Error capture and structured logging should be configured at scaffold time when creating a new product, preventing production blindness and ensuring immediate traceability for incident triage.

Yes, the observability baseline captures unhandled rejections and client-side errors by integrating Sentry directly into the application scaffold for comprehensive error tracking.

Yes, you activate the observability baseline within your existing app-scaffolder or infra-provisioner setup to automatically inject health endpoints, Sentry, and logging configurations.

New deployments lack traceability because observability was not configured at scaffold time, a problem solved by integrating request-id structured logging and Sentry error capture upfront.