governance: register legacy repository branches

[magicalfeyfenny]

Primary issue

Issue #47 is the sole primary issue for this legacy-branch registration migration.

Intent

This draft creates the durable repository inventory and GitHub registration trail for pre-policy branch identities. It closes Issue #47 only if this exact reviewed migration candidate merges into dev with separately granted authority.

The migration preserves historical evidence without granting it new lifecycle authority.

Closes #47.

Scope

This PR adds the single migration snapshot at docs/LEGACY_BRANCH_INVENTORY.md. It records all 27 non-default branch names, approved categories, full observed identities, completed marker-label and issue registrations, and the unresolved immutable-PR exact-base condition.

The scoped documentation records branch provenance and nothing else.

Non-goals

This PR does not modify, rename, rebase, force-push, merge, or delete any legacy branch. It does not resume underlying ornate UI work, modify production or GameMaker resources, rerun workflows, alter release state, or repair the separate PR-base mismatch.

Acceptance mapping

The inventory provides one concise evidence entry for every approved branch name and preserves divergent local and remote identities. It records the required characterization, extraction, validation-documentation, visual-tour, crystal, post-mortem, and reverted-update evidence, while the linked GitHub records document the authorized label and issue mutations.

The completed remote mutations created legacy-branch-name, applied it to Issues #50, #54, and #60 and PRs #51 and #52, updated Issues #50 and #54, and created Issue #60. No legacy PR body was saved because the live exact-base checker rejects both immutable heads.

Important files and ownership

docs/LEGACY_BRANCH_INVENTORY.md is the sole changed file and is the durable owner of this migration snapshot. No runtime, generated, asset, GameMaker-resource, workflow, or release owner changes.

This single-document boundary keeps all production and asset ownership unchanged.

Risk

Risk is high because this governance record determines how immutable historical evidence may be interpreted, and an incorrect claim could imply merge, validation, or deletion authority that does not exist. The candidate is limited to one documentation file and explicitly preserves exact ref identities and the unresolved base mismatch.

• Target branch and authority are correct.
• LFS payload availability is not applicable.
• Generated/runtime ownership is not applicable.
• Documentation is updated through the durable inventory.
• Rollback is concrete and safe through a corrective governed documentation PR.

Validation

python3 tools/check_governance.py, python3 tools/check_repository_hygiene.py, and python3 -m unittest discover -s tools/tests -p 'test_*.py' pass on this exact candidate. The test suite completed 81 tests successfully; its intentionally failing negative checker fixtures print expected findings before the final pass line.

git diff --cached --check, full-SHA resolution for the inventory, and the 27-entry census passed before commit. The retained characterization, extraction, visual-tour CI, validation-documentation, crystal, post-mortem, and reverted-update heads were re-fetched and verified unchanged.

The completed checks verify documentation scope, identity integrity, and historical evidence routing.

Review status

This high-risk governance candidate requires fresh correctness, validation, and governance attestations bound to this complete contract. It is a draft and no review, readiness, Required CI, or merge claim is made.

Remaining risks

PR #51 and PR #52 have immutable heads that do not contain their live dev base 7cbb17daa5f8da86f4da14b49a329297a743cbd1. Their proposed archival bodies pass grammar and contract validation but cannot pass the live exact-base gate, so their bodies were intentionally not updated.

Logs, manifests, hashes, and review conclusions for the historical visual-tour evidence still require durable preservation before archival closure can be considered.

Merge intention

This migration branch is intended to merge only after exact-head review, Required CI, readiness, and separately granted authority.

The legacy branch sources receive no merge authority from this governance record.

External-action authority

Issue #47 authorized the inventory, marker label, retrospective issue, issue and PR label registrations, push, and this draft PR. It does not authorize merge, branch modification, deletion, workflow reruns, release, deployment, or publication.

Rollback or final disposition

A corrective governance PR can amend or revert the inventory without changing immutable legacy branches. The applied GitHub labels and archival issues remain traceable evidence; branch deletion remains separately authorized work.

Non-merge record

This merge-intended migration branch has no non-merge record. Its inventory describes non-merge legacy branches without granting this migration candidate archival-only status.

Lifecycle exception

No lifecycle exception applies to this conforming Issue #47 migration branch. The inventory records legacy exceptions for the frozen historical branches without altering their refs.

Independent agent review

Fresh reviewers must inspect the complete 27-entry census, exact identities, all remote mutations, the unresolved archival-PR base failure, and the non-expansion boundary. After final attestation, rerun the newest exact pull-request workflow and re-fetch the live PR before any separately authorized merge.

[magicalfeyfenny]

Correctness delegated review: PASS. No blocking or advisory findings. The reviewer independently verified the complete branch census, exact identities, candidate and workflow attribution, integration evidence, and historical dispositions against the bound base and head.

[magicalfeyfenny]

Validation delegated review: PASS. No blocking or advisory findings. The reviewer independently reproduced governance, hygiene, Python test, census, identity, ancestry, and diff checks on the exact candidate.

[magicalfeyfenny]

Governance delegated review: PASS. No blocking or advisory findings. The reviewer independently verified issue authority, authorized registrations, unchanged archival objects, contract completeness, preservation deferrals, and the separation of review from merge authority.