review-production-readinesslisted

# Review Production Readiness Determine whether the changed system can be deployed, observed, operated, recovered, and owned safely in its real production environment. Read `references/evidence.md` when selecting go-live criteria, rollout, or recovery evidence. ## Respect the Delivery Contract - For a readiness review, work read-only and report evidence and blockers. - For an authorized implementation task, fix readiness gaps only when they are required by the requested production outcome and remain in scope. - Do not invent availability targets, traffic forecasts, retention policy, ownership, compliance requirements, or rollback guarantees. - Reuse established runbooks, service standards, SLOs, deployment mechanisms, and observability conventions before proposing new ones. ## Define the Production Surface Identify: - critical user and operator journeys; - runtime, regions, tenants, traffic shape, and data sensitivity; - upstream and downstream dependencies; - stateful components and irreversible effects; - deployment owner, operational owner, and support path; - existing reliability objectives and release criteria. When a material target or ownership decision is missing, make the gap explicit. Ask only if it blocks a sound readiness decision. ## Trace Failure and Degradation Map the important request, event, and data flows. For each critical dependency or state transition, verify: - timeouts, cancellation, bounded retries, and retry safety; - idempotency and