feat: action effects — handler bodies → navigate/fetch/dispatch/setState (B3)

[officialCodeWork]

Step 3.2 — Action effects (TRACKER phase 3)

Failure modes B3 and B2 (dispatch half). Mines resolved handler bodies (from step 2.3) for effects, each a typed edge from the EventNode.

Effects

• navigate()/router.push/history.push → navigates-to a RouteNode. Target folded to :param form (reusing endpoint resolution) and joined to a route by exact path, then param-agnostic shape — so navigate(`/users/${id}`) reaches /users/:userId. A target resolving to a shape with no declared route flags unresolved-nav (visible, never silent).
• fetch/axios/wrapper call in a handler → triggers a data source.
• dispatch(thunk()) / dispatch(action()) → writes-state on the slice, via new action/thunk→slice maps in the store registry.
• setState setter (setOpen(…)) → writes-state on the local useState slot.

Handler resolution is unified: prop-drilled (B1), local references, and inline arrows all flow through the same machine, now emitting every effect kind. Handler expressions are captured per event during body extraction; detectRoutes runs before the effect pass so navigate targets can join to routes.

Schema

• New navigates-to edge kind (event → route); JSON schema regenerated (drift gate green).

Eval

• New effects golden check: event → effect edge → target (route path / endpoint / state name).
• New fixture b3-programmatic-nav covering all four effect kinds + shape-matched navigation + the unresolved-nav flag.

Verification

• pnpm -r build / typecheck / test: 84 parser-react tests pass (8 new in effects.test.ts), core schema-drift gate green.
• pnpm eval: 176 pass · 0 fail, lineage precision/recall 1.000, match accuracy 1.000.

🤖 Generated with Claude Code