feat(db): extract flows aggregate to Drizzle (#843) #865
No reviewers
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!865
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "code-lead/843"
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?
Splits flows / flow_runs / flow_node_runs / flow_audit / legacy_forge_calls out of db.ts into per-table Drizzle modules.
Test plan
Closes #843
All acceptance criteria from issue #843 met: all 21 functions extracted across 4 cohesive modules (flows.ts, flow-runs.ts, flow-audit.ts, legacy-forge-calls.ts), 4 Drizzle schema files added, withFlowTransaction keeps the same signature with correct connection-scoped semantics, and the cross-aggregate rollback test proves Drizzle + raw SQL writes revert together.
Nit (non-blocking):
listFlowNodeIntentsSincetest is placed inside thelegacy_forge_callsdescribe block rather than its own — no functional issue, just slightly surprising grouping.