Reconcile the legacy issue backlog with repository ownership and native dependencies

[szmyty]

Why

The organization has 311 open issues across 29 repositories. The bodies are generally strong, but the management surface has drifted:

• 310 of 311 open issues have no labels.
• 53 are unassigned.
• Only 27 have milestones.
• 42 have not been updated in more than 30 days, including 39 in the private product repository.
• Some platform work remains filed in the product repository.
• At least one exact duplicate is open: egohygiene#294 and egohygiene#312.
• Cross-repository dependencies are often written in bodies rather than represented consistently in GitHub's issue relationships/project fields.

A one-time reconciliation is needed before automation can keep the backlog healthy.

Scope

• Inventory every open issue and classify owner repository, architectural plane, status, priority, dependency, milestone/release, and duplicate/supersession state.
• Preserve original discussion and provenance: prefer linking and closing as superseded over copying issue bodies into new disconnected issues.
• Move or re-home work only when GitHub supports a traceable path; otherwise create the correct owner issue and cross-link both sides.
• Resolve exact duplicates and document intentional overlaps.
• Apply the canonical label taxonomy after Pace#10 provides the rollout surface.
• Represent blocking relationships using native issue dependencies/project fields where available.
• Define exceptions for private/security-sensitive issues.
• Produce a repeatable triage report and follow-up cadence.

Acceptance criteria

• All 311 currently open issues have a recorded owner/status decision.
• Exact duplicates and superseded issues are linked and reconciled.
• Platform work stranded in product repositories is routed to its architectural owner.
• Labels, assignments, milestones, and project fields are applied consistently or have explicit exceptions.
• Cross-repository blockers are represented in a queryable form.
• No issue history is discarded.
• The resulting backlog is consumable by Pace and Observatory.
• A bounded recurring triage cadence is documented.

Dependencies

• .github#8 (closed taxonomy/routing contract)
• Pace#10
• Observatory#1
• Organization checkpoint-audit contract