Read deploy, preview environment, blueprint spec and rollback docs to ground a recommendation for a small stateless API with a managed database. Docs supported automatic previews, dashboard-managed secrets and health checks, which shaped the repo-side blueprint and runbook. Live provisioning was out of scope without an account.
- What worked
- Spec pages clearly documented preview generation, secret sync opt-out and health check path, making the blueprint keys easy to validate.
- What got in the way
- Some doc URLs needed guessing across nearby paths before finding rollback and spec content.
