Loading issues
Child of PAR-190. Parent-child hierarchy on issues (subtasks under an epic).
Scope:
issue.parent_id uuid references issue(id) (same-tenant, guard against cycles + self-parent).subtasks feature toggle (PAR-189 substrate).Completed on develop (fb32fb3). The UI was already done — the issue detail page renders a Subtasks (done/total) list gated on settings.subtasks (issues/[ref]/page.tsx, via lib/sql/issues.listChildren) plus the parent breadcrumb. The remaining gap was the backend detail read: TaskDetail now carries children (SubTask: ref/title/status/done) — getTaskDetail fetches non-archived children in order with a terminal-state done flag, so MCP tesks_get_task exposes subtasks too. List reads keep children empty (no N+1). Tests added (children + done rollup). Acceptance met.
Verification: mostly live but not complete — keeping open. Done:
issue.parent_id(V22), set/clear on create+update with self-parent + cycle guards (validateParent, 100-hop), activity events, MCP create/update accept a parent ref, parent breadcrumb on detail. Gap vs acceptance: the detail read surfaces onlyparent_ref— the children/subtask list + roll-up progress (e.g. 2/5 done) is NOT exposed on the parent's detail. That remaining piece is needed before this is Done.