Repository navigation
Propagate explicit issue category through PRD publication #476
Description
Parent
What to build
Carry an explicit GitHub issue category (bug or enhancement) from local PRD metadata through the generated epic into native tracking and task issue publication. Publication must fail closed when the category is missing or invalid instead of guessing from prose or defaulting every PRD to enhancement.
Acceptance criteria
- PRD creation records exactly one explicit category: bug or enhancement.
- PRD-to-epic conversion preserves that category without inference.
- Native epic publication applies the same category to the tracking issue and every task.
- Publication rejects missing, invalid, or conflicting category metadata before creating or editing any GitHub issue.
- Resumed publication verifies the existing issue category matches the source contract.
- Focused checks cover bug, enhancement, missing, invalid, and mismatch counterexamples.
- The change stays independently mergeable and below the repository review limit.
Blocked by
#468 must merge first because it owns the native publication path this contract extends.
Out of scope
- Historical category reconciliation; that remains Reconcile existing GitHub issue metadata against the lifecycle contract #459.
- Lifecycle auditor/workflow or branch protection; those remain Audit issue hygiene and PR closure semantics without mutation #458, Run the lifecycle auditor as a read-only GitHub check #467, and Enable the Issue Lifecycle required check after a green observation window #460.
- Runtime evidence, issue closure, collector, research, or trading behavior.
Activity
fix(pm): freeze category across publication batch (#476)
fix(pm): harden category publication checks (#476)
feat(pm): propagate issue category through publication (#476)
proerror77 commentedon Aug 2, 2026
Completion evidence
Acceptance checks: explicit bug or enhancement flows PRD -> epic -> tracking/tasks; missing invalid conflicting resumed and concurrent category drift fail before GitHub create/edit; focused tests and review fixes passed; PR #595 merged to main as 3d3b5b1
Result: passed
Validation: native epic publication focused test passed; bash -n, ShellCheck, and git diff --check passed; two-axis spec and standards review passed; required Monorepo CI gate, Prediction Markets CI gate, Security Summary Report, and CodeRabbit checks passed.
Rollback: revert squash commit 3d3b5b1.
Out of scope: historical category reconciliation (#459), lifecycle or branch-protection work (#458/#460/#467), runtime, research, trading, deployment, and parent issue closure.