Create the OKF issue guidance section

[MariusStorhaug]

The issue model needs a dedicated OKF subtree so agents can navigate from a small index to process guidance or the body rules for one native issue type without loading a monolithic format page.

Request

Create the Ways-of-Working/Issues/ section by relocating the existing issue guidance atomically, then add separate process and type pages. Preserve green navigation and links at every step.

Acceptance criteria

• Issues/index.md routes readers into Process and Types subtrees
• Process contains concise Format, Lifecycle, Planning, and Relationships pages
• Types contains a concise Hierarchy overview plus Epic, PBI, Task, and Bug pages
• Every page has title and description frontmatter and one clear conceptual owner
• Existing Issue Format and Issue Hierarchy content is relocated without broken inbound links, anchors, navigation, or generated indexes
• Workflow remains authoritative for phase definitions
• Sub-issues, dependencies, and parallelism have one canonical explanation
• The four native operational issue types have distinct, non-duplicative body and lifecycle guidance
• All child pull requests pass index, link, lint, clean-build, CI, and Copilot review gates

---

Technical decisions

Structure: Process and Types are separate indexed subtrees so their child Tasks can proceed independently after the atomic relocation.

Atomic relocation: Moving the existing pages, navigation entries, generated indexes, and every inbound reference is one Task and one pull request. No compatibility stubs remain.

Parallel content: After relocation, Process content and Types content touch separate subtrees and may execute in parallel.

Small pages: Each page states one concept once and links outward rather than copying Workflow or another type page.

---

Delivery plan

Delivery is tracked through native Task sub-issues. Relocation completes first; Process and Types content then proceed as dependency-free siblings and may run concurrently.

[MariusStorhaug]

Created the OKF-section child graph. Relocation Task #89 runs first. Process Task #88 and Types Task #87 are siblings blocked by #89 and may run in parallel after it completes. Their separate Process and Types subtrees avoid shared-file conflicts; both must complete before parent Task #86 aligns consuming guidance.

[MariusStorhaug]

Execution started for relocation Task #89 after bootstrap #82 closed. Its coordinated session is implementing only the atomic OKF path/navigation cutover. Process #88 and Types #87 remain blocked and will start in parallel only after #89 merges.

[MariusStorhaug]

Relocation PR #91 is ready, green, Copilot-clean, and squash auto-merge enabled. Independent approval is the only remaining gate. Process Task #88 and Types Task #87 remain correctly blocked; both coordinated sessions will start from the post-merge live default branch, in parallel, after #89 closes.

[MariusStorhaug]

Relocation #89 is complete. Types #87 and Process #88 are now executing in parallel from live main. #87 exclusively owns Issues/Types/; #88 exclusively owns Issues/Process/; each may make only its own subsection change in shared Zensical navigation. Their completion will unblock #86.

[MariusStorhaug]

PR #93 for Types #87 is ready, green, Copilot-clean, and awaiting only independent approval. Its merge will provide the four canonical type pages and corrected Hierarchy semantics required to unblock Process PR #94.

[MariusStorhaug]

Source-of-truth synchronization is complete: PR #93 head 6d48368 contains every Types-owned correction found during combined PR #94 review, and PR #94 includes that exact head. #93 is green/clean and approval-blocked; #94 remains draft pending #93 merge and final Process-only reconciliation.