Migrate live issue metadata to the operational model

[MariusStorhaug]

After the canonical issue model and consuming guidance land, live MSXOrg issue metadata must be reconciled so organization configuration and active work follow the same rules.

Request

Inventory and migrate applicable live issues from Feature or obsolete Bug/Feature hierarchy labels to Epic, PBI, Task, or Bug. Retire Feature only after no applicable issue depends on it, then verify representative sub-issue progress and dependency queries.

Acceptance criteria

• Every open issue using Feature is reviewed and assigned the correct operational issue type or explicitly documented as an exception
• Obsolete Bug/Feature hierarchy labels or textual parent/dependency conventions are removed or migrated where applicable
• Parent/sub-issue relationships are native and produce correct progress summaries
• Sequenced work uses native blocked-by/blocking relationships and dependency queries return the expected graph
• Ready siblings without dependency edges remain independently executable
• Feature is disabled or retired only after the migration proves no applicable live issue still requires it
• The final enabled issue-type set and representative relationship queries are recorded in the issue audit trail
• Parent PBI acceptance criteria and child progress are updated accurately

---

Technical decisions

Operational delivery: This Task may have no repository diff. Completion evidence is the verified GitHub configuration, migration inventory, relationship queries, and audit comments recorded in the issue.

No bulk guessing: Each Feature assignment is classified from its actual scope. One-PR work becomes Task; multi-deliverable work becomes PBI; strategic work becomes Epic; defects remain Bug leaves.

Retirement last: Feature remains enabled until migration and verification are complete.

---

Implementation plan

Inventory and migration

• Inventory open Feature assignments and obsolete hierarchy labels/conventions
• Classify and migrate each applicable issue
• Create or repair native sub-issue and dependency relationships

Retirement and verification

• Verify sub-issue progress and dependency queries on representative real work
• Disable or retire Feature only when safe
• Record final configuration and update parent progress