You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
G00-01 — Re-home legacy issue provenance after the repository rename #111
Legacy references resolve to an archived legacy repository or a verified reset-suite issue, and an issue number from one repository can no longer verify against the other.
Parent and boundary
Parent: #108. Repository governance; no product behavior change. A change to a protected schema, persisted identifier, or root build contract stops and is reported as a contract change.
The legacy repository is located and archived under a distinct name, or its loss is recorded with the recoverable source (the Notion Loop Issues ledger).
Every legacy link in issue bodies, docs, overlays, and the roadmap page is rewritten to the archived repository or to a verified reset issue; none resolves to an unrelated reset issue.
Overlay issue records carry the repository full name, and the catalog generator refuses a record whose repository, title, or state disagrees with the live read-back.
Preflight backlog rows re-point to the reset issues filed for them (L01-08…L01-15 and X00-02…X00-05) or carry a reviewed deferral.
Failure case: a bare legacy number that resolves on the wrong repository must fail python scripts/generate-architecture-catalogs.py --check, not pass it.
Required proof
Link audit output before and after; python scripts/generate-architecture-catalogs.py --check. Record the exact source SHA and run the repository's check-change gate for a PR with an internal changelog fragment.
Handoff
Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review.
Sources
Approved master roadmap §2 and §6 · Gap review of the issue suite against the approved roadmap, 2026-09-27.
Outcome
Legacy references resolve to an archived legacy repository or a verified reset-suite issue, and an issue number from one repository can no longer verify against the other.
Parent and boundary
Parent: #108. Repository governance; no product behavior change. A change to a protected schema, persisted identifier, or root build contract stops and is reported as a contract change.
Grounding
38 open issues link 22 legacy numbers under
github.com/studio-berry/loop/issues/(L13-02 — Embed or outline fonts #128, L03-13g — Measure distance, perimeter, and area on the Quick canvas #238, #404, #418, #421, #424, #431, #443, #455, #477, #584, #586, #587, #590, #592–#598, #619); L13-02 — Embed or outline fonts #128 now resolves here to L13-02 (L13-02 — Embed or outline fonts #128); the others do not exist yet but will collide as numbering grows.docs/preflight-check-catalog-overlay.jsongithub_issuesrecords legacy L11 — Workflow Memory module gate #12, L06-01 — Pin Medic host boundary and research evidence #47, L06-03 — Recover authored exterior before synthesis #49, and L09-03 — Build deterministic spec-field parsers #70. Those numbers now resolve here to L11 (L11 — Workflow Memory module gate #12), L06-01 (L06-01 — Pin Medic host boundary and research evidence #47), L06-03 (L06-03 — Recover authored exterior before synthesis #49), and L09-03 (L09-03 — Build deterministic spec-field parsers #70), with different titles and states. Legacy L03-10 — Present undo and redo as governed revision history #124, L13-04 — Correct hairlines and white overprint #130, and L13-05 — Remove hidden, invisible, off-page, and active content #131 now resolve to L03-10, L13-04, and L13-05. Records for #600, #603, #604, #605, #664, and #665 point at numbers that do not exist here yet.docs/CORRECTION_COVERAGE_MATRIX.mdcites GitHub #587 for the selector AST.The approved roadmap page still names
loop2and cites legacy L04-02 — Enforce operation-owned save and impact policy #34, L06-01 — Pin Medic host boundary and research evidence #47, L06-08 — Shadow, canary, and rollback decision #54–L07-04 — Project queue and status over existing scheduler #58, and L08-01 — Define typed observation port #61, which now open unrelated reset issues.Collisions grow with every new issue or PR number: after this suite was filed, numbering reached X00-09 — PDF/UA accessibility preflight #148.
Acceptance
python scripts/generate-architecture-catalogs.py --check, not pass it.Required proof
Link audit output before and after;
python scripts/generate-architecture-catalogs.py --check. Record the exact source SHA and run the repository's check-change gate for a PR with aninternalchangelog fragment.Handoff
Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review.
Sources
Approved master roadmap §2 and §6 · Gap review of the issue suite against the approved roadmap, 2026-09-27.