NF-5: Parallel dry-run + divergence detection #326
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#326
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 every webhook delivery to run BOTH the legacy handler AND the default flow (with flow side effects suppressed) so that the new engine's correctness can be audited before cutover.
Acceptance criteria
Feature flag
agents.json→node_flows.mode: "off" | "dry-run" | "live"(default"off")."dry-run"mode, matching flows run for every event but every mutating node short-circuits; its intended call is recorded inflow_node_runs.intentas JSON.Divergence API
GET /flows/divergences?since=returns, per event, the legacy handler's actual side effects vs the flow's intended side effects, diff'd.Dogfood
"dry-run"; soak at least one week.Out of scope
References
specs/node-flows.md§ Migration path, phase 1.code-lead referenced this issue2026-04-24 13:46:51 +00:00