Skip to content

G00-01 — Re-home legacy issue provenance after the repository rename #111

Closed

Description

@mberrys

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

Acceptance

  • 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.

G00 implementation record, 2026-10-10

PR #262 completes residual legacy #193 and product-follow-up disambiguation, refreshes live overlay states/milestones, and records the deleted-ledger limitation in the source register. No history or product behavior is rewritten.

Implementation head: 78f9c0bce909bca7f95cc5b6c701043e61332087. The required check-change gate passed using the existing build with identical plugin ABI inputs. 117 Python cases and the mapped ABI test passed; one optional PdfTool runtime case skipped. Hosted CodeQL checks passed at this head; the native CI build is still running. Full package qualification remains pending. This record does not grant release admission.

Activity

  1. mberrys commented on Sep 29, 2026

    @mberrys
    ContributorAuthor

    Status against the acceptance criteria:

    Leaving this open until #149 merges and the 3 remaining links are rewritten.

  2. added a commit that references this issue on Oct 2, 2026
  3. mberrys commented on Oct 7, 2026

    @mberrys
    ContributorAuthor

    Two more bare legacy numbers that now resolve to unrelated reset items and are not in the list above:

    Also: pre-reset commit subjects on dev carry legacy numbers, e.g. 623f40fa Issue #103: Bookmark sidebar greyed out... and 91952e56 Issue #104: Try to fix license. Those collide with reset #103 and #104.

  4. mberrys commented on Oct 7, 2026

    @mberrys
    ContributorAuthor

    More legacy collisions, in a machine-read file this time: every follow_up_issue in docs/product-surface.json is a legacy number. The values are 193, 195, 66, 30, 41 and 126. In this repo they now open PR #193, PR #195, L08-06 (#66), L03-04 (#30), L05-01 (#41) and L03-12 (#126). The absorbed GUI surfaces they meant are now tracked under #231. #231 requires those rows to point at live reset issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Promotion stage

    Stable present

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions