Branch retirement 2026-09-22 — 111 remote branches measured against origin/main

Owner directive (2026-09-22): every branch that has not landed on main is to be migrated to main, then all branches other than main deleted. This report is the measurement, the disposition, and the restore map. Claim labels: everything below is measured (command shown) unless marked otherwise.

1. Method

Base: origin/main = 6c0dbbd2d (PR #1128 merge) after git fetch --prune. Authoritative branch set: gh api --paginate repos/MIZOKI-3-5/MIZOKICloudRun/branches = 112 names including main. Open PRs at start: 0. Open coordination claims: 0. main moved twice during the run — PR #1130 (d25abcc7c) and PR #1131 (e336c03fa), both owner merges of the two branches this lane had queued to land; this PR is built on e336c03fa. Per branch:

git rev-list --count origin/main..origin/<b>                 # ahead
git cherry origin/main origin/<b> | grep -c '^+'             # commits with no patch-equivalent on main
git merge-tree --write-tree origin/main origin/<b>           # conflict? result tree == main tree?
# for every non-ancestor commit, in a throwaway worktree on origin/main:
git cherry-pick -n --allow-empty <sha> && git status --porcelain   # empty => content already on main
python3 .github/scripts/deploy_router.py --base origin/main --head <probe-commit>   # deploy count

2. Classification

3. The nine non-ancestor branches, settled by content

4. What this PR lands on main

Nothing that was on a branch — both carrying branches were merged by the owner (#1130, #1131) before this PR opened. This PR is the truth fix and the record:

• f3ae34f0a ops/decision-studio/README.md: the source is on main; it no longer says "not on main and does not need to be". a7ba0f519 production/service-registry.yaml: the mizoki-decision-studio source: row no longer names a branch that does not exist (rule 01: the tree wins, fix the doc in the same run). Line counts unchanged so path:line citations hold.
• This report, its docs/INDEX.md row, and the memory-ledger record.

Deploy Router over this PR's diff: 0 workflows. Gates measured on the probe tree that carried the same .decision/ + preserved-docs content plus these two doc edits: .github/scripts/content_gates.sh rc=0 (148 governance-gate tests passed; canon spec, canon audit, skill parity and WO-16 ratchet clean); gate_leak_scan --check 0 new files; tests/reports/test_evidence_manifest.py 12 passed; tests/governance/test_service_registry_revision_literals.py, test_incident_scripts.py, test_docs_index.py, tests/test_marketsignal_closure_register.py, tests/test_migration_closure_register.py green.

A direct push to main was refused by the Claude Code harness (merge without review), so the reviewed PR path is used.

5. Deletion record — final state: main is the only branch

1. 109 branches whose content is on main by the measurements above — deleted 2026-09-22 ~15:5xZ by this lane in four git push origin --delete batches (30/30/30/19, every batch rc=0, every ref reported [deleted]).
2. review/preserve-local-reports-2026-09-22 — deleted by GitHub on the owner's #1130 merge (15:55Z).
3. review/decision-studio-mirror-20260914-a439b5f380704668 — deleted by GitHub on the owner's #1131 merge (16:00Z).
4. rescue/drive-clone-state-20260830 — its tip is preserved as annotated tag archive/rescue-drive-clone-state-20260830 (pushed 15:5xZ) before the branch was deleted in step 1.

Measured after: gh api --paginate repos/MIZOKI-3-5/MIZOKICloudRun/branches → main only. Local tracking branches in shared clones are untouched (git fetch --prune drops the remote refs only); the pr/* refs are a local fetch refspec, not GitHub branches. No workflow triggers on branch deletion (on: delete appears in none).

6. Restore map (name → tip SHA at deletion)

Any branch below can be recreated exactly with git push origin <sha>:refs/heads/<name> while the object is still reachable on GitHub (merged commits are reachable from main forever; the rescue wreck is reachable from its tag).