Define Epic, PBI, Task, and Bug issue bodies

[MariusStorhaug]

The native issue types represent different planning altitudes and cannot share one undifferentiated three-section body. Aggregators need outcome and decomposition guidance; delivery leaves need implementation-ready detail.

Request

Add one concise Types page for Epic, PBI, Task, and Bug, and reduce Hierarchy to the shared taxonomy, promotion/demotion, and containment overview.

Acceptance criteria

• Epic defines strategic outcome, Initiative/OKR relationship, Why/How/What framing, success measures, scope, decomposition decisions, readiness, and aggregate closure
• PBI defines a bounded body-of-work outcome, aggregate acceptance criteria, interface/decomposition decisions, readiness, nested-PBI rules, and aggregate closure
• Task defines one deliverable, implementation-ready acceptance criteria and decisions, test-first checklist, one-PR repository delivery, and an audited operational completion path when no repository artifact exists
• Bug is a Task-level delivery subtype with observed/expected behavior, reproduction, environment, regression, workaround, root-cause boundary, and regression-test-first plan
• A defect requiring multiple pull requests becomes a PBI with Bug/Task children rather than an oversized Bug
• Feature is described as temporary live metadata pending migration, not a hierarchy level
• Type guidance treats Bug as a native delivery type and Feature as temporary metadata, never as hierarchy labels
• Hierarchy remains concise and links to type pages instead of repeating their bodies
• Types index, links, lint, clean build, CI, and Copilot review are green

---

Technical decisions

Single type slot: Epic, PBI, Task, and Bug use native issue types. Feature describes work kind rather than planning altitude and is retired only after migration.

Leaf delivery: Task and Bug are the only issue types that directly own implementation branches and closing pull requests. Operational Tasks without a repository artifact close through explicit, verified evidence recorded in the issue.

Aggregate delivery: Epic and PBI progress comes from native sub-issues. They close only when children and aggregate acceptance criteria are complete.

File ownership: This Task owns only the Types subtree and Types/Hierarchy.md. Process Task #88 exclusively owns Process/Format.md, including removal of legacy Bug/Feature label wording.

---

Implementation plan

Type pages

• Add the Epic body and lifecycle page
• Add the PBI body and lifecycle page
• Add the Task body and lifecycle page
• Add the Bug body and lifecycle page
• Reduce Hierarchy to shared taxonomy and routing

Validation

• Verify Types index and cross-type links
• Run documentation checks, CI, and the Copilot review loop

[MariusStorhaug]

Scope correction before implementation: Process Task #88 already owns the canonical Format page, so this Task now owns only Issues/Types/ and Types/Hierarchy.md. The duplicated Format acceptance line was replaced with a Types-only rule. This preserves true parallel execution and avoids a shared-file conflict; #88 still explicitly removes the legacy label wording from Format.

[MariusStorhaug]

Implementation is published in draft PR #93 from commit 26c217a.

• Confirmed the branch started exactly at live origin/main (39411c5) and contains blocker squash 3e04c260
• Added dedicated OKF pages for Epic, PBI, Task, and Bug with complete frontmatter
• Updated only the owned Types navigation subsection and generated Types index
• Index and full-link validation pass for this checkpoint
• Hierarchy reduction and complete validation remain in progress

[MariusStorhaug]

The owned implementation is complete through commit c4e9d24 and local validation is green.

• Reduced Hierarchy to shared taxonomy, routing, native containment/dependencies, and promotion/demotion; detailed bodies now live only on the four type pages
• Preserved the existing inbound #how-to-express-the-hierarchy anchor without editing any Process or cross-document page
• Update-DocumentationIndex.ps1 update and -Check passed
• Full Test-DocumentationLink.ps1 passed: all documentation links resolve
• Zensical 0.0.50 clean build passed with no issues
• The branch remains limited to Issues/Types/ and the Types subsection of src/zensical.toml; pinned Super-Linter and the other PR jobs are running in CI

[MariusStorhaug]

All pull request CI jobs are green on PR #93.

• Build passed, including index verification and clean Zensical generation
• Links passed across the full documentation tree
• Lint passed, including Markdown, natural-language, codespell, merge-marker, and security/config validators
• The explicit Copilot review round is now starting