ersatztv/docs/decisions/migration-map.md

Decision migration map (legacy heading → active record / archive)

Auditable mapping produced during the #521 lifecycle migration. Every legacy H2 heading maps to either an active record (key) or an archive location. Most headings in docs/decisions.md and the docs/decisions/*.md topic files are still status: legacy-unmigrated (no metadata block yet) — this table only covers records touched so far. PYTHONPATH=. python3 scripts/decisions_validate.py prints the running legacy-unmigrated count; it must trend to 0 over the arc, not drop to 0 in one PR.

Legacy heading	Key	Status	Location
2026-07-17 — No persistent compiler servers in CI; every services: container gets an explicit cap; #390's small-lane move reversed (#406)	ci.runner-placement	active	docs/decisions.md
2026-07-19 — CI test job reports a sampled true peak-anon, not cache-inflated memory.peak (#412)	ci.peak-anon-measurement	active	docs/decisions.md
2026-07-12 — decisions.md is append-only, enforced; root-screenshot guard (#303 H9/H3)	docs.append-only-guard	superseded (superseded-by: docs.decision-lifecycle@2026-07-21)	docs/decisions/archive/release-ci-governance.md
2026-07-21 — Decision records carry a lifecycle schema, validated by a script; append-only-by-diff is retired (#521)	docs.decision-lifecycle	active (supersedes: docs.append-only-guard@2026-07-12)	docs/decisions.md

Notes on records considered but NOT given a standalone entry

• #390 (small-lane move for api-docs/format). Investigated whether #390's reversal (described in #406's prose, point 3: "#390's small-lane move ... reversed") ever existed as its own ## record. It did not — grep for #390 across docs/decisions.md and docs/decisions/*.md finds it only inside #406's own body text (and one other unrelated mention of #390's apt-ffmpeg estimate, also inside #406). #390 was prose-only: no separate heading, so nothing to mark superseded or move to archive. ci.runner-placement (#406) therefore carries supersedes: none; the reversal is recorded only in its **Signals:** line (#390 (prose-reversed, no standalone record)) and in this note.
• #411 (the earlier memory.peak-headline measurement). Investigated the "#411 obsolescence" the brief references. #411 is mentioned twice in docs/decisions.md, both inside #412's own body ("the test job's memory instrument (added in #411) now reports ..." and "the older #411 probe ... is superseded"). Like #390, #411 never had its own ## heading — its "decision" was narrated retroactively inside #406 (the "Measurement is now continuous" paragraph, which describes the instrument #411 actually shipped) and explicitly marked obsolete inside #412's own prose. Since there is no standalone #411 record, there is nothing to move to archive/; ci.peak-anon-measurement (#412) — the record that supersedes #411's approach — carries supersedes: none and documents the prose reversal in its **Signals:** line. The governed surface (CI memory measurement) still exists and is very much active, so this is a straightforward supersession of an unnamed predecessor, not a retirement — there's no case to make for retired here since the surface it measures is live.

Still open (tracked for later migration passes, not this PR)

• ## 2026-07-11 — Queue state lives in the pinned Gitea tracker (#237), not in the handoff file is reversed by #520, not #521 — per the task-5 brief its supersession lands in PR2/Task 8, not here.
• The remaining ~90 headings in docs/decisions.md and the other three docs/decisions/*.md topic files (optimistic-concurrency.md, api-auth-security.md, spa-modularization.md, and the rest of release-ci-governance.md) are unmigrated (status: legacy-unmigrated, no metadata block). They are valid under the schema as-is (the validator treats an unmigrated H2 as a migration target, not an error) and migrate incrementally as each is next touched, per the arc's design.