M21 Tracking — Node Flows #340
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks#340
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tracking issue for the Node Flows architecture — a successor to the MF-1..10 multi-forge work. Lifts the hidden dispatch DAG in
webhook-handlers.ts/webhook-ci.ts/review-loop.ts/deps.ts/slash-commands.tsinto explicit data: typed triggers, a closed node registry, a JSON graph DSL, an executor with topo-order dispatch, SQLite persistence, and a ComfyUI-style graph editor + trace viewer on top.Status (refreshed 2026-04-26)
Engine track: 7/9 shipped. UI track: 8/9 shipped. Three stories remain.
Specs
specs/node-flows.md— engine + data model + execution semantics.specs/node-flows-ui.md— operator-facing graph editor + trace viewer.Engine stories (NF-1 .. NF-9)
UI stories (NF-UI-1 .. NF-UI-9)
Suggested implementation order
Engine: NF-1 → NF-2 → NF-3 → NF-4 → NF-5 → NF-6 → NF-7 → NF-8 → NF-9.
UI: NF-UI-1 → NF-UI-2 → NF-UI-3 → NF-UI-4 → NF-UI-5 → NF-UI-6 → NF-UI-7 → NF-UI-8 → NF-UI-9 — each independently mergeable once its dependencies land.
The two tracks overlap: UI stories NF-UI-1 and NF-UI-2 start once NF-4 is done; NF-UI-7 and later wait for the runs drawer + replay backing on NF-4. NF-UI-8 needs NF-7.
Closing — all listed sub-stories merged: NF-1..7 (#322-#328), NF-8 #329, NF-9 #330; NF-UI-1..8 (#331-#338), NF-UI-9 #339. Verified 2026-04-28.