Configure Epic and PBI issue types

[MariusStorhaug]

MSX issue guidance defines Epic, PBI, and Task as native GitHub issue types, but the live organization currently enables only Task, Bug, and Feature. The platform configuration must match the documented hierarchy before typed parent issues and their child work can be created consistently.

Request

Add the Epic and PBI organization issue types while retaining Task and Bug. Keep Feature enabled until a later migration has reassigned every applicable live issue. Verify that native sub-issue and blocked-by/blocking relationships are available and queryable, and document the target operational type model in the repository.

Acceptance criteria

• Epic and PBI are enabled as organization issue types alongside Task, Bug, and the temporarily retained Feature type
• The issue-type configuration is verified through the GitHub API
• Native sub-issue and blocked-by/blocking relationships are verified through the supported GitHub CLI or API surfaces
• The documentation records that Epic/PBI aggregate work, Task/Bug are delivery leaves, and Feature remains until migration
• Existing documentation checks and CI remain green

---

Technical decisions

Bootstrap order: This Task is created with the existing Task type. The parent PBI and remaining typed issues are created only after Epic and PBI exist.

Feature migration: Feature is not disabled in this Task. Retirement happens only after a separate migration Task confirms that no applicable issue still uses it.

Delivery evidence: The Task includes a small documentation pull request plus an issue comment recording the verified live configuration and API probes, satisfying the current PR-based completion model.

Relationship semantics: Sub-issues represent containment. Blocked-by/blocking relationships represent execution order.

---

Implementation plan

Documentation

• Record the target issue-type and relationship model in the current issue hierarchy guidance

Organization configuration

• Add Epic and PBI issue types without removing Feature
• Verify the complete enabled issue-type list through the GitHub API
• Verify native sub-issue and dependency relationship operations

Validation

• Run index, link, lint, and clean Zensical checks
• Complete repository CI and the Copilot review loop

[MariusStorhaug]

Configured the organization issue types and recorded the supported relationship surfaces.

• The createIssueType GraphQL mutation created Epic and PBI as enabled organization types.
• The complete organization.issueTypes query now returns exactly five enabled types:

Type	ID	Color	Description	Enabled
Task	IT_kwDOBakL784A9Ymf	Yellow	A specific piece of work	Yes
Bug	IT_kwDOBakL784A9Ymh	Red	An unexpected problem or behavior	Yes
Feature	IT_kwDOBakL784A9Ymj	Blue	A request, idea, or new functionality	Yes
Epic	IT_kwDOBakL784CHCqN	Purple	A strategic body of work composed of multiple product backlog items	Yes
PBI	IT_kwDOBakL784CHCqO	Green	A body of work composed of multiple delivery issues	Yes

• The GraphQL schema exposes Issue.parent, Issue.subIssues, Issue.blockedBy, Issue.blocking, Issue.subIssuesSummary, and Issue.issueDependenciesSummary; querying those fields on this Task succeeded and returned no current relationships.
• The supported GraphQL mutations are available as addSubIssue, removeSubIssue, reprioritizeSubIssue, addBlockedBy, and removeBlockedBy.
• GitHub CLI 2.96.0 also exposes native relationship mutations through gh issue edit --parent, --add-sub-issue, --add-blocked-by, and --add-blocking, with matching removal flags. GraphQL is the query surface used for the relationship audit.
• No disposable issues or relationships were created. Relationship mutation waits for the real parent PBI and orchestration children created after this bootstrap Task; containment will use sub-issues, and execution order will use blocked-by / blocking dependencies.
• The focused hierarchy guidance is in the linked draft pull request. Local index, link, Markdown lint, and clean Zensical checks pass; CI and the Copilot review loop remain open.

[MariusStorhaug]

Completed the validation and automated review gates.

• Documentation index check passed.
• Documentation link validation passed.
• Targeted Markdown lint passed with zero issues.
• Clean Zensical build passed with no issues.
• Pull request CI passed: Build, Links, and Lint are green; Publish correctly skipped for the pull request event.
• An explicit Copilot review was requested with the repository script. The round completed cleanly with no inline comments and no changes requested.
• The implementation checklist is now complete. The pull request can move from draft to ready and wait for the independent approval gate through squash auto-merge.