deploy-projectlisted

# Deploy Project Turn an accepted deployment design into controlled, observable implementation. Production activity is never implied by development completion. ## Reconfirm readiness Before changing deployment state: 1. Read project instructions, `THE-FIRST.md`, accepted requirements, technical and deployment sources, active feedback rules, completed feature slices, and existing runbooks. 2. Verify all release-scope slices are accepted and committed. List intentionally deferred work. 3. Inspect actual Git branch, commit, tags, working tree, build configuration, lock files, migrations, infrastructure, CI, container definitions, and deployment target state available to the current environment. 4. Confirm the preliminary deployment design still matches the current code, data, environment, target platform, and user intent. 5. Surface stale assumptions, uncommitted release changes, missing access, or environment drift before proceeding. Do not turn a green local suite, a successful build, or an old runbook into proof that production is ready. ## Complete the deployment contract Resolve and document: - Exact source commit, version, artifact, or image digest. - Target environment, hosts, services, regions, topology, domains, and ports. - Build location, reproducibility, artifact storage, image registry, and promotion path. - Configuration owners, secret references, certificates, and environment-specific values. Never copy secret values into project documents or `THE-FIRST.md