Estimate: 12m · Depends on: 2.4.1
Navigation through the work-item tree (the AI-native execution DAG + Jira-style epic→story→task→bug→subtask hierarchy from 2.1.1). A parent breadcrumb walks the ancestor chain (each ancestor = type icon + PROD-N + title, linking to its own detail page) so a Subtask shows its Task → Story → Epic lineage. A child list shows the item's direct children (type icon + identifier + title + status pill + assignee), each a link to its detail page; an item with no children shows nothing (no empty scaffold).
Reads. Children come from the getIssueDetail bundle (2.4.1). The ancestor chain is bounded (Story 1.4's depth limit is 4) so it's a short parent-walk; if a dedicated read is cleaner than threading it through the aggregate, add workItemRepository.findAncestors (a single recursive-CTE read mirroring findSubtree) with the explicit workspaceId filter. Breadcrumb + child links are plain <a>/next/link to /issues/[childKey] — clicking one navigates to that item's detail page (the recursion the tree implies).
listChildren; cross-workspace isolation holds.lib/repositories/workItemRepository.ts — findChildren, findSubtree (the recursive-CTE pattern to mirror for ancestors), the workspaceId-filter conventionlib/issues/issueTypes.ts (2.1.1) — type icons for breadcrumb/child rowsIssueDetailDto — extend with the ancestor chain if not bundled already