Add route handler graph parity slice

Author: skooch

docs/gap-analysis.md

@@ -117,19 +117,19 @@ Complete slices:
 
 Deferred or optional future slices:
 - Public surface expansion:
-  - trace breadth now covers modes, risk labels, and multi-edge-type filtering (Plan 03 complete); `HTTP_CALLS` and `ASYNC_CALLS` edges are now produced via service-pattern call reclassification; remaining gap is `DATA_FLOWS` edges
+  - trace breadth now covers modes, risk labels, and multi-edge-type filtering (Plan 03 complete); `HTTP_CALLS` and `ASYNC_CALLS` edges are now produced via service-pattern call reclassification, and decorator-backed `HANDLES` edges are verified on the graph-model route fixture; remaining gap is route-linked `DATA_FLOWS` edges
 - Query/runtime expansion:
   - full Cypher lexer/parser/executor parity beyond the verified shared read-only floor
   - broader traversal and query-analysis parity beyond the current shared `detect_changes` contract
 - Indexing/runtime expansion:
   - deeper usage/type-ref extraction parity beyond the current daily-use slice
 - Metadata and enrichment:
   - git-history coupling — now implemented (subprocess `git log`, `FILE_CHANGES_WITH` edges)
-  - long-tail edges — now implemented: `THROWS`/`RAISES` (JS/TS/TSX throw statements); remaining or out-of-scope gaps: `OVERRIDE` (Go-only), `WRITES`/`READS` (not proven original-overlap by the current C reference fixture), `HANDLES`/`DATA_FLOWS` (deferred route-graph)
-  - route nodes — partially implemented (stub `Route` nodes from `HTTP_CALLS`/`ASYNC_CALLS` edges; no `HANDLES` or `DATA_FLOWS` yet)
+  - long-tail edges — now implemented: `THROWS`/`RAISES` (JS/TS/TSX throw statements) and decorator-backed `HANDLES`; remaining or out-of-scope gaps: `OVERRIDE` (Go-only), `WRITES`/`READS` (not proven original-overlap by the current C reference fixture), route-linked `DATA_FLOWS` (deferred route-graph)
+  - route nodes — partially implemented (stub `Route` nodes from `HTTP_CALLS`/`ASYNC_CALLS` edges plus verified decorator-backed `Route`/`HANDLES`; no route-linked `DATA_FLOWS` yet)
   - config-linking — partially implemented (Strategy 1 key-symbol + Strategy 2 dependency-import; full config normalization surface not yet ported)
   - richer decorator/enrichment promotion
-  - current entrypoint: [graph-model-parity-plan.md](/Users/skooch/projects/codebase-memory-zig/docs/plans/new/graph-model-parity-plan.md)
+  - current entrypoint: [graph-model-parity-plan.md](/Users/skooch/projects/codebase-memory-zig/docs/plans/in-progress/graph-model-parity-plan.md)
 - Productization beyond the current contract:
   - broader installer/self-update behavior
   - broader agent integration coverage and installer diagnostics
@@ -428,7 +428,7 @@ The Zig store has the schema (tables + indexes + pragmas) and opens in-memory DB
 | `pass_parallel` | 1,427 | MISSING | Thread pool orchestration |
 | `pass_similarity` | 505 (minhash.c) | MISSING | MinHash near-clone detection |
 | `pass_gitdiff` | ~200 | MISSING | Git diff → changed files/hunks |
-| `pass_route_nodes` | 742 | PARTIAL (stub Route nodes from `HTTP_CALLS`/`ASYNC_CALLS` edges; no `HANDLES` or `DATA_FLOWS`) | HTTP route node creation |
+| `pass_route_nodes` | 742 | PARTIAL (stub Route nodes from `HTTP_CALLS`/`ASYNC_CALLS` edges plus verified decorator-backed `Route`/`HANDLES`; no route-linked `DATA_FLOWS`) | HTTP route node creation and first handler association slice |
 | `pass_tests` | 285 | WORKS for the shared Python `TESTS` / `TESTS_FILE` slice | Test file/function tagging now verified on the local parity fixture; broader language breadth stays follow-on work |
 | `pass_enrichment` | ~200 | MISSING (deferred) | Decorator tag enrichment |
 | `pass_configlink` | ~200 | PARTIAL (Strategy 1 key-symbol + Strategy 2 dependency-import) | Config-code linking |

docs/plans/new/graph-model-parity-plan.md …s/in-progress/graph-model-parity-plan.mddocs/plans/new/graph-model-parity-plan.md renamed to docs/plans/in-progress/graph-model-parity-plan.md docs/plans/new/graph-model-parity-plan.md renamed to docs/plans/in-progress/graph-model-parity-plan.md

@@ -7,8 +7,10 @@ route-linked data flow, decorator route detection, and the broader config-link
 normalization surface.
 
 ## Current Phase
-Awaiting approval to execute. Move this plan to `docs/plans/in-progress/`
-before implementation starts.
+Phase 2 route handler modeling is in progress. The first slice has landed:
+decorator route extraction now creates `Route` nodes and `HANDLES` edges, and
+route-registration calls preserve enough call metadata to emit `HANDLES` when
+the handler reference resolves.
 
 ## Current Codebase State
 - Complete and verified: advanced trace modes, risk labels, include-tests
@@ -18,14 +20,19 @@ before implementation starts.
   `src/route_nodes.zig` creates deterministic `Route` nodes from `HTTP_CALLS`
   and `ASYNC_CALLS`, `src/pipeline.zig` emits service-pattern call edges, and
   `src/query_router.zig` can expose route summaries.
-- Still missing for graph-model parity: route handler association, `HANDLES`
-  edges, route-linked `DATA_FLOWS`, decorator/framework route extraction, and
-  the full config normalization/linking surface beyond the current key-symbol
-  and dependency-import strategies.
-- Current full Zig-vs-C harness baseline after plan reconciliation:
-  `151` comparisons, `86` strict matches, `19` diagnostic-only comparisons,
-  `10` mismatches. The graph-model-related mismatches include the existing
-  `graph-enrichment-config-deps` and `graph-enrichment-http-calls` query rows.
+- Newly implemented in this session: Python decorator route extraction emits
+  `Route` nodes and `HANDLES` edges; framework route-registration calls such as
+  `app.get("/path", handler)` now carry route metadata and emit `Route`,
+  `CALLS`, and `HANDLES` facts when the handler resolves.
+- Still missing for graph-model parity: route-linked `DATA_FLOWS`, broader
+  framework route coverage, HTTP/async calls routed through concrete URL route
+  nodes, and the full config normalization/linking surface beyond the current
+  key-symbol and dependency-import strategies.
+- Current full Zig-vs-C harness baseline after this route slice:
+  `158` comparisons, `89` strict matches, `20` diagnostic-only comparisons,
+  `10` mismatches, and `cli_progress: match`. The graph-model-related
+  mismatches still include the existing `graph-enrichment-config-deps` and
+  `graph-enrichment-http-calls` query rows.
 
 ## Superseded Plans
 - `docs/plans/paused/ready-to-go/04-graph-enrichment-parity-plan.md`
@@ -54,16 +61,20 @@ before implementation starts.
 ## Phases
 
 ### Phase 1: Lock the Remaining Graph Contract
-- [ ] Re-read the original route, config-linking, and semantic-edge passes and record only the overlapping behavior still missing from the Zig port.
-- [ ] Define fixture-backed acceptance rules for `Route`, `HANDLES`, `HTTP_CALLS`, `ASYNC_CALLS`, route-linked `DATA_FLOWS`, decorator route extraction, and config normalization/linking.
-- [ ] Add minimal JavaScript/TypeScript and Python fixtures under `testdata/interop/graph-model/` before changing extractor behavior.
-- **Status:** pending approval
+- [x] Re-read the original route, config-linking, and semantic-edge passes and record only the overlapping behavior still missing from the Zig port.
+- [x] Define fixture-backed acceptance rules for decorator-backed `Route` and `HANDLES` facts.
+- [ ] Define fixture-backed acceptance rules for `HTTP_CALLS`, `ASYNC_CALLS`, route-linked `DATA_FLOWS`, and config normalization/linking.
+- [x] Add a minimal Python route fixture under `testdata/interop/graph-model/routes/`.
+- [ ] Add minimal JavaScript/TypeScript route fixtures once the shared C/Zig public behavior is established for those registrations.
+- **Status:** partially complete
 
 ### Phase 2: Complete Route Handler Modeling
-- [ ] Extend route extraction so supported framework registrations and decorators resolve to handler symbols instead of only creating route rendezvous nodes from outbound calls.
-- [ ] Emit `HANDLES` edges from handler functions/methods to `Route` nodes, preserving method/path metadata and duplicate-route suppression.
-- [ ] Add store, extractor, pipeline, and Cypher regression coverage for route node creation, handler association, and route summary exposure.
-- **Status:** pending approval
+- [x] Extend Python decorator route extraction so handlers create route rendezvous nodes.
+- [x] Preserve route-registration call metadata and emit `HANDLES` when handler references resolve.
+- [x] Emit `HANDLES` edges from handler functions/methods to `Route` nodes for the first supported decorator and registration slices.
+- [x] Add extractor, pipeline, and interop regression coverage for route node creation and handler association.
+- [ ] Broaden framework coverage and add route summary exposure coverage.
+- **Status:** in progress
 
 ### Phase 3: Add Route-Linked Data Flow
 - [ ] Define the first accepted `DATA_FLOWS` route-link contract from request entry points through handler calls without pretending to solve full local data-flow analysis.
@@ -78,11 +89,11 @@ before implementation starts.
 - **Status:** pending approval
 
 ### Phase 5: Verify and Reclassify
-- [ ] Run `zig build`, `zig build test`, `bash scripts/run_interop_alignment.sh --zig-only`, and focused graph-model fixture queries.
-- [ ] Run the full Zig-vs-C interop harness if the C reference binary is available locally.
-- [ ] Update `docs/port-comparison.md`, `docs/gap-analysis.md`, and `docs/zig-port-plan.md` only for rows backed by the new fixtures.
+- [x] Run `zig build`, `zig build test`, `bash scripts/run_interop_alignment.sh --zig-only`, and focused graph-model fixture queries.
+- [x] Run the full Zig-vs-C interop harness if the C reference binary is available locally.
+- [x] Update `docs/port-comparison.md`, `docs/gap-analysis.md`, and `docs/zig-port-plan.md` only for rows backed by the new fixtures.
 - [ ] Move this plan and its progress log to `docs/plans/implemented/` only after all required verification passes.
-- **Status:** pending approval
+- **Status:** in progress
 
 ## Decisions
 | Decision | Rationale |

docs/plans/in-progress/graph-model-parity-progress.md

@@ -0,0 +1,33 @@
+# Graph Model Parity Progress
+
+## Session: 2026-04-16
+
+### Phase 1: Lock the Remaining Graph Contract
+- **Status:** partially complete
+- Actions:
+  - Moved `docs/plans/new/graph-model-parity-plan.md` to `docs/plans/in-progress/graph-model-parity-plan.md` before implementation.
+  - Starting from current main baseline: full Zig-vs-C harness reports 151 comparisons, 86 strict matches, 19 diagnostic-only comparisons, and 10 known mismatches.
+  - Re-read the original route-node and service-pattern route registration paths and selected the first shared public contract: decorator-backed routes create `Route` nodes and `HANDLES` edges, with query-visible handler and route rows.
+  - Added `testdata/interop/graph-model/routes/app.py` and manifest assertions for `Route` and `HANDLES` query rows.
+
+### Phase 2: Complete Route Handler Modeling
+- **Status:** in progress
+- Actions:
+  - Extended extractor state so route decorators create `Route` nodes plus `HANDLES` edges during extraction.
+  - Added route-registration call metadata for framework calls such as `app.get("/path", handler)` and pipeline emission for `Route`, `CALLS`, and `HANDLES` when the handler resolves.
+  - Added focused unit coverage in `src/extractor.zig`, `src/pipeline.zig`, and `src/service_patterns.zig`.
+  - Updated Zig golden snapshots; new `graph-model-routes` golden locks `/users` and `list_users -> /users`.
+
+### Verification
+- `zig build` -> passed
+- `zig build test` -> passed
+- `bash scripts/run_interop_alignment.sh --update-golden` -> passed, 20/20 golden snapshots updated
+- `bash scripts/run_interop_alignment.sh --zig-only` -> passed, 20/20 golden comparison
+- `bash scripts/run_interop_alignment.sh` -> passed with 20 fixtures, 158 comparisons, 89 strict matches, 20 diagnostic-only comparisons, 10 known mismatches, and `cli_progress: match`
+
+## Errors
+| Timestamp | Error | Attempt | Resolution |
+|-----------|-------|---------|------------|
+| 2026-04-16 | Initial `graph-model-routes` manifest used a Zig project name that did not match the indexed directory basename, so query assertions read an empty project. | Ran `--update-golden` and inspected the generated `graph-model-routes` snapshot. | Changed the fixture project to `routes`, regenerated golden snapshots, and verified query rows were populated. |
+| 2026-04-16 | JavaScript route-registration fixture improved Zig but was not emitted by the current C binary, adding a new full-harness mismatch. | Ran the full Zig-vs-C harness and inspected per-fixture route outputs. | Switched the strict shared fixture to a Python decorator route that both implementations expose publicly, while keeping Zig registration support covered by unit tests. |
+| 2026-04-16 | The redirected harness rerun wrapper used `status`, which is read-only in zsh. | Tried to capture the exit code with `status=$?`. | Re-ran with `rc=$?`; both `--zig-only` and full interop passed. |

docs/plans/new/improvements/README.md

@@ -15,7 +15,7 @@ This directory turns the upstream `codebase-memory-mcp` issue and PR review into
 
 These plans are upstream-improvement backlog, not the current parity execution
 entrypoint. The active graph-model parity planning entrypoint is
-[graph-model-parity-plan.md](/Users/skooch/projects/codebase-memory-zig/docs/plans/new/graph-model-parity-plan.md).
+[graph-model-parity-plan.md](/Users/skooch/projects/codebase-memory-zig/docs/plans/in-progress/graph-model-parity-plan.md).
 
 ## Plan Index
 

docs/plans/new/improvements/semantic-graph-expansion-feature-cluster-plan.md

@@ -2,7 +2,7 @@
 
 ## Status
 Backlog improvement cluster. For the current original-project graph-model parity
-work, use `docs/plans/new/graph-model-parity-plan.md`; this plan remains as
+work, use `docs/plans/in-progress/graph-model-parity-plan.md`; this plan remains as
 the broader upstream feature-pressure inventory for later semantic expansion.
 
 ## Goal

docs/plans/paused/ready-to-go/04-graph-enrichment-parity-plan.md

@@ -2,7 +2,7 @@
 
 ## Status
 Paused on 2026-04-15. This bundled enrichment plan is superseded by
-`docs/plans/new/graph-model-parity-plan.md`. Its git-history slice is already
+`docs/plans/in-progress/graph-model-parity-plan.md`. Its git-history slice is already
 implemented; the remaining route/config/semantic graph work is now tracked in
 the graph-model parity plan with narrower acceptance gates.
 

docs/plans/paused/superseded/config-linking-and-edge-expansion-plan.md

@@ -2,7 +2,7 @@
 
 ## Status
 Paused on 2026-04-15. This narrower config/edge plan is superseded by
-`docs/plans/new/graph-model-parity-plan.md`, which keeps config normalization,
+`docs/plans/in-progress/graph-model-parity-plan.md`, which keeps config normalization,
 route graph completion, and remaining graph-model edge families in one
 fixture-backed execution order.
 

docs/plans/paused/superseded/route-graph-parity-plan.md

@@ -2,7 +2,7 @@
 
 ## Status
 Paused on 2026-04-15. This narrower route-only plan is superseded by
-`docs/plans/new/graph-model-parity-plan.md`, which combines the remaining
+`docs/plans/in-progress/graph-model-parity-plan.md`, which combines the remaining
 route, config-linking, route-linked data-flow, and semantic-edge work into one
 dependency-ordered graph-model parity tranche.