define-deploymentlisted

# Purpose Ground the project in *where* and *how* it runs — for the developer inner loop and for production. # Questions to ask (in order) ## Production 1. Hosting target: self-hosted (VM or Kubernetes), managed PaaS (Fly, Render, Railway, Heroku), serverless (AWS Lambda, Cloudflare Workers, Vercel, Netlify), managed containers (ECS, Cloud Run, App Runner), on-prem, or hybrid. 2. Cloud provider (if any): AWS, GCP, Azure, Cloudflare, DigitalOcean, other. 3. Infrastructure as Code: none (manual), Terraform, Pulumi, CDK, CloudFormation, or provider-native manifests (`fly.toml`, `render.yaml`, etc.). 4. CI/CD: GitHub Actions, GitLab CI, CircleCI, Jenkins, Buildkite, or none. 5. Environments: prod only / prod + staging / prod + staging + preview-per-PR. 6. Secrets management: `.env` plus platform secrets, HashiCorp Vault, AWS Secrets Manager, Doppler, 1Password CLI, SOPS. 7. Observability in production: log sink, metrics sink, tracing sink. 8. Backup and disaster-recovery expectations: none, daily snapshot, point-in-time recovery, multi-region. ## Development 9. Local dev environment: native toolchain, devcontainer, Nix, Docker Compose, Vagrant, or remote dev (Codespaces, Gitpod). 10. Containerization: not used, optional, or required (include Dockerfile). 11. Hot reload / fast feedback expectations. 12. Seed data strategy: none, fixtures, factories, synthetic generator, or anonymized prod snapshot. 13. Database migrations tool (if applicable). Use `AskUserQuestion` for the