Add epic hierarchy to Project Planning by leoncheng57 · Pull Request #206 · leoncheng57/custom-dca-opencode

leoncheng57 · 2026-08-26T04:57:24Z

Summary

resolve bounded GitHub sub-issue relationships and expose deterministic parent ownership
render collapsed, persistent epic rows with child progress, compact checklist children, and filter-safe breadcrumbs
preserve priority promotion, read-only hierarchy, all density modes, and honest truncation warnings
add deterministic server, simulator, unit, and Playwright coverage

Verification

npm run typecheck - VERIFIED
npm test - VERIFIED: 631 tests / 53 files
npm run build - VERIFIED
CI=1 PORT=3541 MOCK_OPENCODE_PORT=4744 MOCK_PREVIEW_PORT=4745 npm run test:e2e - VERIFIED: 322 passed, 1 screenshot-runner-gated skip
npm run test:preview - VERIFIED: 1 passed after one unrelated transient iframe timeout on the first attempt

Human verification

VERIFIED (Playwright): Open /planning; an epic is collapsed by default. Expected: child titles are absent and the parent shows an Epic marker plus progress. Failure: child rows render top-level or expanded.
VERIFIED (Playwright): Activate the epic chevron with Enter. Expected: two thinner child rows appear beneath the parent, including the closed child. Failure: the title dialog opens or children duplicate elsewhere.
VERIFIED (Playwright): Click a child title. Expected: the existing item dialog opens; the external-link control remains separate. Failure: expansion changes or GitHub navigation replaces the dialog.
VERIFIED (Playwright): Inspect the parent progress. Expected: 1/2 closed and a 50% semantic progressbar. Failure: closed children are omitted or counts disagree.
VERIFIED (Playwright): Select Closed and open Low priority. Expected: the filtered child appears top-level with Child of #101. Failure: it silently disappears.
VERIFIED (unit + Playwright): Expand an epic and reload, then test malformed storage. Expected: valid state persists; malformed storage safely collapses all. Failure: reload loses valid state or page errors.
VERIFIED (Playwright): Cycle all five densities and inspect at 390px with the epic expanded. Expected: controls remain usable and body width never exceeds viewport. Failure: horizontal overflow or inaccessible controls.
VERIFIED (Playwright): Simulate epicsTruncated. Expected: warning appears while the planning feed remains visible. Failure: no warning or blank page.
UNVERIFIED: Review the generated desktop/mobile screenshots for subjective visual polish after the screenshot workflow publishes them. Expected: hierarchy is immediately legible. Failure: cramped badges, weak parent/child distinction, or clipped content.

Remote hierarchy mutations

The approved GitHub issue grouping will be applied only after live preflight. A follow-up PR comment will contain the mutation log, final tree, and exact rollback commands.

full:/planning

GitHub's issue list reports sub_issues_summary but never a parent link, and the only endpoint that names an epic's children is /issues/{n}/sub_issues. So the snapshot now resolves edges itself, after pagination, with a bounded fan-out: issues with childCount > 0, sorted by number descending, capped at PLANNING_LIMITS.epics, at most epicConcurrency requests in flight, at most epicChildren entries read per epic. It fails open per parent exactly like the comments fetch in getPlanningItemDetails, so one unlucky epic cannot blank a backlog that is mostly about other work, and it reports epicsTruncated rather than implying the hierarchy is complete. Requests run concurrently but assignments are applied afterwards in parent order, so a child claimed by two epics always lands on the same one. groupPlanningItems now returns nodes rather than flat items. A child folds into its parent and gets no top-level row; a child whose parent is absent from the filtered input keeps its row with orphanedParentNumber set, since silently deleting it is the one outcome worse than a missing breadcrumb. Section placement gains one deliberate exception to "the exact label selects the section": a node sits at the highest priority anywhere in its epic, so a priority:high child cannot be buried inside an unlabelled parent. The parent's own priority conflict still wins outright — it needs triage whatever its children say — and the tag group still comes from the parent alone. planningView.ts persists which epics a device has expanded, defaulting to none, because folding the backlog down to its parents is the point. Planning.tsx is touched only enough to keep typecheck honest: it flattens each node back to parent-then-children rows until the epic UI lands.

leoncheng57 · 2026-08-26T05:00:26Z

GitHub epic grouping mutation log

Live preflight completed before mutation: only #110 and #132 were parents; every proposed child was unparented; no proposed new parent title existed. PR #116 remained open, so #53 was included. PRs #176 and #178 were merged; closed #91 was omitted, while open #182 and #90 left two eligible sub-agent children. #104 was untouched.

Applied

Labels: Improve File patch viewing. Also just improve the run log grouping and readability - brainstorm on this more #132 [] -> [priority:medium]; Build out the public custom-dca-opencode website #110 [priority:medium] -> [priority:high]; Make Playwright workflow route selection easier #181 [] -> [priority:medium].
Existing parents: Build out the public custom-dca-opencode website #110 -> Publish the migrated agent-skills catalog from this repository #109, Deploy secure pull-request previews and a public simulator #112, Create an interactive leoncheng.dev simulation guide for the DCA runner #53; Improve File patch viewing. Also just improve the run log grouping and readability - brainstorm on this more #132 -> Add a conversation-only Run log view with user and assistant prose #166, Plan a universal historical change modal for agent turns #134, Wrap long terminal action commands in transcript headers #159, File disk should only show up in the changes right sidebar instead of showing up in the chat transcript. #172, cleanup and make the "Changes" panel more useful #183.
Notifications: reduce noise and make the inbox actionable #207 Notifications -> (notifications) include a truncated output of the agent's response so that different notifications from the same session are differentiated #186, Needs Investigation. I am getting more user notifications than expected, and it's causing noise and leading to user frustration. #180, Quick: Make the resolve checkbox a big button #99, Expand notification history retention and UI window #135, quick: the notification/active URL route should have its own directly linkable link. #127, Quick: Add the ability toggle on grouping notifs by session #96.
Sub-agents: make delegated work legible and controllable #208 Sub-agents -> The human-launched child agents should be distinguished more visually from the native subagents. #182, Allow explicit model selection when delegating a sub-agent #90.
PR screenshots: fix the pipeline and document the capture paths #209 PR screenshots -> pr-screenshots: duplicate requested routes pass validation, then crash Playwright with 'duplicate test title' #83, Add a pr-screenshots skill for capturing and attaching PR screenshots #119, Document transient UI screenshots using temporary Playwright specs #164, Update the playwright cicd screenshot process to have full height screenshots by default #39.
E2E: no shared mutable state across parallel spec files #210 E2E shared state -> e2e: auto-permissions state races across parallel spec files #82, E2E: notification state files are shared across parallel workers and never reset between runs #80.
Skills and reminders catalogue: new entries and delivery #211 Skills/reminders -> Add a Senior SWE System Design Artifacts skill #103, Add a mini-design-doc skill for concise visual engineering decisions #142, New skill: cmux-cross-session — hand a task to an agent in another cmux workspace #108, Explore repository-scoped reminders for custom-dca-opencode workflows #165, Add /leaving-now-wrap-up skill: force stop-work, push, status-sync, and human summary before the user goes idle #107, (skills) new skill proposal - tell it to oneshot the rest of the prompt and make best guesses for any questions that popup, although document them #187.
Composer: make the mode, model, reminder and workflow pickers fast to use #212 Composer pickers -> The reminders/commands UI selection should quick filter options in order to search and filter. Or maybe tags. #115, Idea: Having easily clickable preset options for plan/build + model combinations #157, Make Playwright workflow route selection easier #181.
Session lists: find, name and triage sessions from the Hub #213 Session lists -> Surface interrupted sessions in session lists #101, It would be nice to be able to rename session names, do it if it's not too hard #120, Make the recently opened and recently active list, much longer than five items each, and make them scrollable #44.
Give design artifacts a home in the app #214 Design artifacts -> Add a Notion, HTML, and Markdown section for design documents #151, create a design system components page #150, Idea: Put excalidraw embedded on the right sidebar, especially useful for frontend changes and system design #158.

Post-mutation verification refetched every child parent URL, all ten parent trees, adjusted labels, and the repository-wide parent set. Top-level open issue count: 25.

Exact rollback

GitHub cannot delete created issues. The commands below detach every added edge, restore adjusted labels, and close the eight newly-created empty parents.

gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/132/sub_issue -F sub_issue_id=5252115854
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/110/sub_issue -F sub_issue_id=5219225531
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/207/sub_issue -F sub_issue_id=5252247399
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/207/sub_issue -F sub_issue_id=5251617276
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/207/sub_issue -F sub_issue_id=5224038116
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/207/sub_issue -F sub_issue_id=5241931597
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/207/sub_issue -F sub_issue_id=5235978226
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/207/sub_issue -F sub_issue_id=5224023873
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/208/sub_issue -F sub_issue_id=5251652312
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/208/sub_issue -F sub_issue_id=5223345807
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/209/sub_issue -F sub_issue_id=5221982083
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/209/sub_issue -F sub_issue_id=5228665992
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/209/sub_issue -F sub_issue_id=5249538674
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/209/sub_issue -F sub_issue_id=5219011152
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/210/sub_issue -F sub_issue_id=5220612919
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/210/sub_issue -F sub_issue_id=5220505573
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/211/sub_issue -F sub_issue_id=5225369943
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/211/sub_issue -F sub_issue_id=5247279334
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/211/sub_issue -F sub_issue_id=5225453098
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/211/sub_issue -F sub_issue_id=5249542217
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/211/sub_issue -F sub_issue_id=5225453093
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/211/sub_issue -F sub_issue_id=5252278947
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/212/sub_issue -F sub_issue_id=5227326258
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/212/sub_issue -F sub_issue_id=5248550957
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/212/sub_issue -F sub_issue_id=5251627861
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/213/sub_issue -F sub_issue_id=5224887925
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/213/sub_issue -F sub_issue_id=5230632891
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/213/sub_issue -F sub_issue_id=5219076121
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/214/sub_issue -F sub_issue_id=5248101251
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/214/sub_issue -F sub_issue_id=5248062323
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/214/sub_issue -F sub_issue_id=5248975639
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/132/labels
gh api --method PATCH repos/leoncheng57/custom-dca-opencode/issues/110 -f "labels[]=priority:medium"
gh api --method DELETE repos/leoncheng57/custom-dca-opencode/issues/181/labels
gh issue close 207 --repo leoncheng57/custom-dca-opencode
gh issue close 208 --repo leoncheng57/custom-dca-opencode
gh issue close 209 --repo leoncheng57/custom-dca-opencode
gh issue close 210 --repo leoncheng57/custom-dca-opencode
gh issue close 211 --repo leoncheng57/custom-dca-opencode
gh issue close 212 --repo leoncheng57/custom-dca-opencode
gh issue close 213 --repo leoncheng57/custom-dca-opencode
gh issue close 214 --repo leoncheng57/custom-dca-opencode

leoncheng57 added 2 commits August 26, 2026 00:55

Finish planning epic hierarchy UI

5ccc5f9

github-actions Bot temporarily deployed to pr-preview-206 August 26, 2026 04:58 Destroyed

github-actions Bot added a commit that referenced this pull request Aug 26, 2026

Publish screenshots for PR #206 at 5ccc5f9

b85c229

leoncheng57 marked this pull request as ready for review August 26, 2026 05:03

leoncheng57 merged commit ae6d23d into main Aug 26, 2026
6 checks passed

github-actions Bot added a commit that referenced this pull request Aug 26, 2026

Remove published artifacts for closed PR #206

e66287b

Navigation Menu

Add epic hierarchy to Project Planning - #206

Add epic hierarchy to Project Planning#206
leoncheng57 merged 2 commits into
mainfrom
feat/planning-epic-hierarchy-finish

leoncheng57 commented Aug 26, 2026

Uh oh!

leoncheng57 commented Aug 26, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

leoncheng57 commented Aug 26, 2026

Summary

Verification

Human verification

Remote hierarchy mutations

Uh oh!

leoncheng57 commented Aug 26, 2026

GitHub epic grouping mutation log

Applied

Exact rollback

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant