Problem
The canonical fleet currently exposes hundreds of open Issues, open pull requests, and non-default branches. Mechanical census and branch cleanup removed proven residue, but many remaining records have not been semantically adjudicated together. A large ambiguous corpus makes the authoritative work graph difficult for maintainers and autonomous contributors to use.
Proposed outcome
Converge the live GitHub corpus so every actionable outcome has exactly one open Issue at its semantic owner; every open pull request implements a live owning Issue; and every ordinary development branch backs an open pull request or carries an explicit recovery or lifecycle purpose. Preserve historical records by closing them with accurate reasons rather than deleting them.
Reconcile Institute Work membership and native hierarchy to the surviving authoritative Issues. Delete a branch only after exact-head proof that its unique outcome landed, was explicitly superseded, or is no longer planned.
Parallel execution boundary
This Task owns GitHub corpus semantics only. It does not own source, workflows, package configuration, CI execution, consolidation, publication, visibility, archival, or fleet mutation.
The CI/CD programme remains exclusively owned by swift-institute/institute-continuous-integration#35 and its ratified D1–D5 hierarchy. This Task must not mutate that hierarchy, the central repositories named by D1–D4, the Research-report lane, caller/configuration surfaces, or uniformity implementation work while the peer programme owns them.
Acceptance
- Every open Issue is retained as an independently live exact-owner outcome or closed with a durable completed/not-planned receipt.
- Every open pull request links to a retained live outcome or is closed with its disposition.
- Every remaining non-default branch backs an open pull request or has a recorded lifecycle, recovery, or unresolved exact-owner adjudication.
- Superseded/not-planned records do not retain Institute Work membership; genuinely completed records retain programme history.
- In-flight assignment, Issue type, native hierarchy, and Project authority are internally consistent.
- A final complete census and mutation receipt is published here, with exact coordinates and no copied CI execution ledger.
Problem
The canonical fleet currently exposes hundreds of open Issues, open pull requests, and non-default branches. Mechanical census and branch cleanup removed proven residue, but many remaining records have not been semantically adjudicated together. A large ambiguous corpus makes the authoritative work graph difficult for maintainers and autonomous contributors to use.
Proposed outcome
Converge the live GitHub corpus so every actionable outcome has exactly one open Issue at its semantic owner; every open pull request implements a live owning Issue; and every ordinary development branch backs an open pull request or carries an explicit recovery or lifecycle purpose. Preserve historical records by closing them with accurate reasons rather than deleting them.
Reconcile Institute Work membership and native hierarchy to the surviving authoritative Issues. Delete a branch only after exact-head proof that its unique outcome landed, was explicitly superseded, or is no longer planned.
Parallel execution boundary
This Task owns GitHub corpus semantics only. It does not own source, workflows, package configuration, CI execution, consolidation, publication, visibility, archival, or fleet mutation.
The CI/CD programme remains exclusively owned by swift-institute/institute-continuous-integration#35 and its ratified D1–D5 hierarchy. This Task must not mutate that hierarchy, the central repositories named by D1–D4, the Research-report lane, caller/configuration surfaces, or uniformity implementation work while the peer programme owns them.
Acceptance