NF-4: Persistence + default graph #325
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks#325
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?
As the platform, I want flows, runs, and per-node traces persisted in SQLite with a default graph seeded on first boot so that the engine survives restarts and reproduces today's dispatch unchanged.
Acceptance criteria
Schema
flows,flow_runs,flow_node_runs— columns per spec § Persistence.defaultflow row with the baked default-graph body on first boot; reseeds whensource=default+versiondiffers from the shipped constant.Default graph
apps/server/src/domain/flows/default-graph.json— canonical baked graph; loader validates it against the NF-2 schema at test time.webhook-handlers.ts,webhook-ci.ts,slash-commands.ts,deps.ts.Read endpoints
GET /flows,GET /flows/:id,GET /flows/runs,GET /flows/runs/:id(auth-gated mutations deferred to NF-7).Retention
flow_runs+flow_node_runs, swept by the existing sweeper.Out of scope
References
specs/node-flows.md§ Persistence.🤖 Auto-assigned to boss (heuristic: default → boss (no specific label match; safer than dev)). Reply
/unassignto reroute.