[Process] Constitution GitHub Issue Discipline is broken — open issues have no Feature → User Story parent linkage

## Summary

Constitution § DevOps GitHub Issue Discipline (NON-NEGOTIABLE) requires every User Story issue to be a GitHub **sub-issue** of its parent Feature issue. A 2026-09-08 audit of open issues found **no parent linkage**.

## Verified evidence

- Constitution: `.specify/memory/constitution.md` (GitHub Issue Discipline)
- GraphQL `parent` on the first 50 open issues: all `null` (sample includes #512, Wave 10 bugs, Thor findings, War Machine findings)
- Open issue count at audit time: **105**
- Specs exist through `076-oscal-full-compliance` under `specs/`, but open GitHub issues are almost entirely unlinked audit/bug tickets — not Feature → User Story trees

## Impact

- Spec-kit agents cannot trace Feature → User Story → tasks via GitHub
- Duplicate/overlapping tickets accumulate (see #845/#844, #837/#839, #836/#838, #678/#584)
- Wave 10 milestone still has 29 open issues with no parent Feature

## Suggested fix

1. For remaining spec-kit features: create/restore Feature parent issues and attach User Story sub-issues
2. For audit-bug swarms: either attach them under a Feature/epic parent or explicitly mark them as standalone bugs (and amend the constitution if standalone bugs are allowed)
3. Do not invent a fake hierarchy for closed historical work

Start with .specify/memory/constitution.md and the open-issue GraphQL parent audit described here; review the Feature and User Story records under specs/. Done means remaining feature issues have explicit User Story sub-issue links, standalone audit bugs are classified, and any needed constitution change is documented without fabricating hierarchy for closed work.

Written by the indexing model from the issue text.