deployment-readinesslisted

# Deployment Readiness Prepare a managed application for deployment based on its assurance profile. This skill produces the evidence the maturity ladder's **Shipped** stage looks for: a deploy configuration matching the profile's `deployment` target, and the `.aidd/deployment.md` runbook. It never performs a deployment and never touches credentials or secrets. ## Usage ``` deployment-readiness [app] ``` If `[app]` is omitted, infer from the current working directory. ## Context - `.aidd/project-profile.json`: the assurance profile. Its `deployment` field (`local | lan | private_server | public_server | cloud`) is the single source of truth for where the app is expected to run. If the file is absent, treat the target as `local` (the inference default) and say so in the report. - The maturity ladder (`shared/src/metadata/maturity.ts`, stage `shipped`) recognizes deploy config at any of: `.github/workflows/`, `Dockerfile`, `docker-compose.production.yml`, `fly.toml`, `netlify.toml`, `vercel.json`, `wrangler.jsonc`, `wrangler.toml`. For `deployment: local` profiles the deploy-config artifact is not required. Only the runbook and a release tag. - Spernakit-derived apps (a `spernakit_version` or `stack` field in `package.json`) already have a canonical container shape: single monolithic container (nginx + supervisord + Bun backend + built frontend), TLS terminated by an external reverse proxy, config mounted as JSON, secrets injected via env. `audits/DEPLO