fix(catalog): separate live and legacy issue records (#111)

[mberrys]

Refs #111. Repo-side half of G00-01; the issue-body and roadmap-page halves are under "Outside the repo".

Problem

The preflight overlay's github_issues records were numbered against the retired repository. Its numbers overlap this repository's sequence, so every record and most open backlog rows resolved to an unrelated issue (legacy #47 and #49 opened L06-01 and L06-03; legacy #12 opened L11). The generator checked record shape only, so nothing could catch it.

Changes

• github_issues entries carry repository. Live records are #<n> in studio-berry/loop; frozen legacy snapshots are legacy#<n> with repository legacy.
• The generator refuses an open legacy record as a row's closed_by, and a bare #<n> in gap text no longer satisfies a legacy#<n> record.
• New --verify-github (opt-in, needs gh, not run in CI) reads live records back and rejects a missing issue, a pull request, or a changed title, state, or milestone. Issue and PR numbers share one sequence, so a PR collision is reported as such.
• Sixteen open backlog rows re-point to the reset issues filed for them (L01-08 — Classify ICC-based color by its painted space #113–L01-15 — Close the sparse-mark bleed raster false pass #120, X00-02 — Re-file parked legacy expansion candidates with value cases #141–X00-05 — Standards currency: PDF/X-6, PDF 2.0 output intents, and GWG 2022 check sets #144); rows that landed or closed keep legacy#<n> snapshots. Provenance table in docs/LEGACY_ISSUE_PROVENANCE.md.
• 25 of 28 legacy issue/PR URLs under docs/ became legacy #<n> text. docs/PREFLIGHT_COVERAGE_MATRIX.md documents the two record kinds and the flag.

Outside the repo

• 38 legacy links in 38 original suite issue bodies (L01 — Evidence Core module gate #2–Completed drags are discarded: EditorHost::onDragCompleted drops the DragSession #104) were rewritten to legacy #<n> text. Links from the parent issues to the new sub-issues were left alone.
• The Notion master roadmap's 41 legacy issue links and three legacy-repository links became plain text, with a note on the first that numbers overlap and content is recoverable from the ledgers.

Not in this PR

Three legacy links stay: docs/GOVERNED_EXECUTION.md (1) and docs/adr/adr-011-architecture-contracts-d1-d5.md (2). Both belong to the governed-execution subsystem, whose binding proof lanes (UnitTestsGovernedExecution, packaging builds) a documentation change cannot carry, and building needs approval. check-architecture.py failed on them, so I restored both files rather than claim evidence I don't have.

The retired repository is not reachable from studio-berry or mberrys, so links cannot be re-homed to an archive. Content is recoverable from the Notion Loop Issues and Sessions ledgers.

Verification

• python scripts/generate-architecture-catalogs.py --check passes; --check --verify-github passes against live GitHub.
• scripts/ci/test_preflight_check_catalog.py, test_preflight_corpus_coverage.py, test_correction_operation_catalog.py: 62 tests pass (10 new, 1 updated).
• python scripts/agent/check-change.py --base origin/dev: pass (modules: documentation).
• No C++ changed, so nothing was built or configured.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}