Execute the coordinated production schema and application cutover

Depends on the scope/artifact manifest, reviewed runbook, per-tenant preflight, remediation plan, rehearsal, credential plan and verified rollout holds; required acceptance must pass or have an explicit release disposition.

During the approved window: merge PR #2 under the hold; verify production builds; stop all affected game/application/external writers; verify quiescence; take and validate coordinated backups; execute reviewed preparation/remediation and migrations per tenant; require expected successful schema history; deploy matching complete plugin bundles/images/configuration and rotate credentials. Start new code only when all tenants sharing the images are ready.

Done when the exact deployed revisions, backup receipts, schema outcomes and operator decisions are recorded and the stack is ready for the production verification subissue. On failure follow the reviewed restore procedure, not blind retries or jar-only rollback.