[Release Track] Release operations and rollout

[jjoonleo]

Prepare rejection response, release ownership/monitoring, and the final reusable checklist after the build/QA flow settles.

Recommended sub-issue order

1. [Release] Create Play review rejection response playbook #461 (codex-ready) - [Release] Create Play review rejection response playbook
2. [Release] Create release ownership and rollout monitoring checklist #463 (codex-ready) - [Release] Create release ownership and rollout monitoring checklist
3. [Release] Create reusable app release checklist #462 (blocked) - [Release] Create reusable app release checklist

Codex thread guidance

• Take this parent issue as the thread entrypoint.
• Work through sub-issues in the recommended order unless a sub-issue is marked blocked or manual.
• For codex-ready sub-issues, implement or verify only that issue's scope.
• For blocked sub-issues, stop at the prerequisite and leave a status note instead of forcing closure.
• For manual sub-issues, prepare checklist/text/instructions when useful, but do not claim completion without the required human or console access.
• Do not modify issues outside this parent track unless the sub-issue explicitly says to coordinate with them.