childhood

1# Childhood
2 
3Stay with a release after it ships. Verify what users receive and what production serves, then fix verified regressions within the user's authorized scope. A successful merge or publish command is the start of this work.
4 
5## Establish the release
6 
7- Identify the repository, release version, immutable tag commit, merge commit, production deployment, and affected delivery surfaces. Use the release receipt and actual provider/registry state; do not guess from the current branch or today's latest build.
8- Record the release, observation start/end, checks, findings, and next action with `work_state_write` when available. Keep announcements and unrelated infrastructure failures distinguishable from product regressions.
9- Carry forward existing authorization. Monitoring does not itself authorize another release, rollback, production migration, or external announcement. Prepare and validate a concrete fix before requesting any authorization still missing.
10 
11## Verify the delivered release
12 
13Choose the checks relevant to its delivery surfaces; independent checks can run in parallel.
14 
15| Surface | Evidence to collect |
16| --- | --- |
17| Source and CI | Confirm the tag resolves to the shipped commit. Inspect CI for that commit and any release/changelog commits, including late failures. Paginate new issue reports, merged-PR comments, reviews, and review threads since release; verify actionable reports against the shipped code. |
18…