Tighten config deps interop fixture

Author: skooch

docs/gap-analysis.md

@@ -127,7 +127,7 @@ Deferred or optional future slices:
   - git-history coupling — now implemented (subprocess `git log`, `FILE_CHANGES_WITH` edges)
   - long-tail edges — now implemented: `THROWS`/`RAISES` (JS/TS/TSX throw statements), decorator-backed `HANDLES`, and route-linked `DATA_FLOWS`; remaining or out-of-scope gaps: `OVERRIDE` (Go-only), `WRITES`/`READS` (not proven original-overlap by the current C reference fixture)
   - route nodes — partially implemented (stub and concrete URL/path/topic `Route` nodes, verified decorator-backed `Route`/`HANDLES`, strict shared route-linked `DATA_FLOWS`, and strict shared `ASYNC_CALLS`; broader framework coverage still open)
-  - config-linking — partially implemented (Strategy 1 key-symbol + Strategy 2 dependency-import; the first strict shared key-symbol normalization fixture now proves raw-key preservation and `CONFIGURES` query visibility, while dependency-import closure remains open)
+  - config-linking — partially implemented (Strategy 1 key-symbol + Strategy 2 dependency-import; the first strict shared key-symbol normalization fixture now proves raw-key preservation and `CONFIGURES` query visibility, while dependency-import fixture coverage remains open)
   - richer decorator/enrichment promotion
   - 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:

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

@@ -46,12 +46,12 @@ short one-token config key.
   the raw config key in query-visible output.
 - Still missing for graph-model parity: broader framework route coverage and
   broader config-link coverage beyond the first strict key-symbol fixture,
-  especially dependency-import mismatch closure.
+  especially dependency-import fixture coverage.
 - Current full Zig-vs-C harness baseline after this config slice:
-  `172` comparisons, `95` strict matches, `22` 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.
+  `172` comparisons, `97` strict matches, `22` diagnostic-only comparisons,
+  `9` mismatches, and `cli_progress: match`. The remaining
+  graph-model-related mismatch is the existing `graph-enrichment-http-calls`
+  query row.
 
 ## Superseded Plans
 - `docs/plans/paused/ready-to-go/04-graph-enrichment-parity-plan.md`

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

@@ -54,7 +54,7 @@
 - `python3 -m json.tool testdata/interop/manifest.json >/dev/null` -> passed
 - `bash scripts/run_interop_alignment.sh --update-golden` -> passed, 22/22 golden snapshots updated
 - `bash scripts/run_interop_alignment.sh --zig-only` -> passed, 22/22 golden comparison
-- `bash scripts/run_interop_alignment.sh` -> passed with 22 fixtures, 172 comparisons, 95 strict matches, 22 diagnostic-only comparisons, 10 known mismatches, and `cli_progress: match`
+- `bash scripts/run_interop_alignment.sh` -> passed with 22 fixtures, 172 comparisons, 97 strict matches, 22 diagnostic-only comparisons, 9 known mismatches, and `cli_progress: match`
 - `git diff --check` -> passed
 - `command -v zlint` -> blocked; `zlint` is not installed in this environment
 
@@ -69,3 +69,4 @@
 | 2026-04-16 | Adding a strict manifest assertion for the new `DATA_FLOWS` row increased the full C/Zig mismatch count because the current C binary did not emit that row for the public fixture. | Ran full interop and inspected per-implementation `graph-model-routes` query rows. | Removed the `DATA_FLOWS` row from the strict shared manifest while keeping Zig unit/focused coverage and documenting the shared-fixture blocker. |
 | 2026-04-16 | The first strict `DATA_FLOWS` fixture attempt used `@app.route`, which creates an `ANY` handler route in C while `requests.get` creates a `GET` caller route, so the bridge could not form. | Queried C route qualified names and saw separate `__route__ANY__/api/users` and `__route__GET__/api/users` nodes. | Switched the fixture to `@app.get`, kept the assertion filtered to `fetch_users`, and patched Zig resolved-call service classification so both implementations share the `GET` route row. |
 | 2026-04-16 | Zig classified `celery.delay` as async but only treated URL-like arguments as service route targets, so a topic argument produced an `ASYNC delay` route instead of a topic route. | Ran a focused temp fixture with `celery.delay("users.refresh")` against both binaries. | Accepted non-URL topics for `ASYNC_CALLS`, preserved broker names, and added the strict `graph-model-async` fixture. |
+| 2026-04-16 | `graph-enrichment-config-deps` used a Zig project name that did not match the indexed directory basename and queried every `Variable`, which mixed a project-name issue with a broad local-binding difference. | Ran a focused temp manifest and compared C/Zig rows for the fixture. | Changed the fixture project to `config-deps` and tightened the query to the shared `express` require-binding row, removing this mismatch from the full harness without claiming full dependency-import coverage. |

docs/port-comparison.md

@@ -132,7 +132,7 @@ It is intentionally not a wish list. It describes:
 | LSP hybrid type resolution | Present for Go/C/C++ in original | Not implemented | `Deferred` | No | The original README explicitly calls out LSP-style hybrid type resolution; Zig does not ship that layer. |
 | Test tagging pass | Yes | Yes for the verified shared Python fixture slice | `Near parity` | Yes | Zig now derives `TESTS` and `TESTS_FILE` from shared filename and call-edge rules on the parity fixture without reopening broader language-specific enrichment work. |
 | Git history coupling | Yes | Implemented | `Near parity` | Yes | Zig pass uses subprocess `git log` (no libgit2); creates `FILE_CHANGES_WITH` edges with `co_changes` and `coupling_score` properties. |
-| Config linking / config normalization | Yes | Partial | `Partial` | No | Zig now implements Strategy 1 (key-symbol) and Strategy 2 (dependency-import matching); the first strict shared key-symbol normalization fixture locks raw-key query visibility and `maxConnections -> max-connections`, but dependency-import mismatch closure and broader normalization coverage remain open. |
+| Config linking / config normalization | Yes | Partial | `Partial` | No | Zig now implements Strategy 1 (key-symbol) and Strategy 2 (dependency-import matching); the first strict shared key-symbol normalization fixture locks raw-key query visibility and `maxConnections -> max-connections`, but dependency-import fixture coverage and broader normalization coverage remain open. |
 | Route-node creation / cross-service graph | Yes | Partial | `Partial` | No | Zig now classifies call edges as `HTTP_CALLS`/`ASYNC_CALLS`, creates stub and concrete URL/path/topic `Route` nodes, emits verified decorator-backed `HANDLES`, and has strict shared route-linked `DATA_FLOWS` plus async topic fixtures. Broader framework coverage remains open. |
 | Infra scanning (`Docker`, `K8s`, Terraform, etc.) | Yes in the original codebase | Not ported | `Cut` | No | Zig intentionally excludes the infra-scan family from the current port target. |
 | OTLP traces | Stubbed | Not ported | `N/A` | No | Not a meaningful implemented-vs-implemented gap. |
@@ -226,7 +226,7 @@ If someone asks “what still separates the Zig port from the original?”, the
 | No full Cypher parity | Some advanced graph query patterns remain C-only. |
 | Partial route / cross-service graph stack | Zig now emits verified decorator-backed `HANDLES`, strict shared route-linked `DATA_FLOWS`, and strict shared async topic caller rows, but broader framework coverage remains open. |
 | No LSP-assisted hybrid resolution | Some higher-fidelity call/type resolution paths remain original-only. |
-| No full config normalization | Git-history coupling is implemented, config linking has dependency-import matching and a strict shared key-symbol normalization fixture, decorator-backed `HANDLES` is verified, strict shared route-linked `DATA_FLOWS` is covered, and the first async topic route fixture is covered. The remaining graph-model gap is broader framework route coverage plus dependency-import and broader config-normalization closure. |
+| No full config normalization | Git-history coupling is implemented, config linking has dependency-import matching and a strict shared key-symbol normalization fixture, decorator-backed `HANDLES` is verified, strict shared route-linked `DATA_FLOWS` is covered, and the first async topic route fixture is covered. The remaining graph-model gap is broader framework route coverage plus dependency-import fixture coverage and broader config-normalization closure. |
 | No UI subsystem | The original can run a graph visualization UI; the Zig port intentionally cannot. |
 | Much narrower installer ecosystem | The original configures 10 agents plus hooks/instructions; Zig currently configures 2 agents and only MCP entries. |
 

testdata/interop/golden/graph-enrichment-config-deps.json

@@ -21,7 +21,11 @@
       "columns": [
         "n.name"
       ],
-      "rows": []
+      "rows": [
+        [
+          "express"
+        ]
+      ]
     }
   ],
   "search_code": [],

testdata/interop/manifest.json

@@ -1965,7 +1965,7 @@
     {
       "id": "graph-enrichment-config-deps",
       "path": "testdata/interop/graph-enrichment/config-deps",
-      "project": "graph-enrichment-config-deps",
+      "project": "config-deps",
       "language": "javascript",
       "scope_tools": ["index_repository", "query_graph", "list_projects"],
       "assertions": {
@@ -1975,13 +1975,13 @@
         "query_graph": [
           {
             "args": {
-              "query": "MATCH (n) WHERE n.label = 'Variable' RETURN n.name ORDER BY n.name ASC",
-              "project": "graph-enrichment-config-deps",
+              "query": "MATCH (n) WHERE n.name = 'express' RETURN n.name ORDER BY n.name ASC",
+              "project": "config-deps",
               "max_rows": 20
             },
             "expect": {
               "columns": ["n.name"],
-              "required_rows_min": 1
+              "required_rows": [["express"]]
             }
           }
         ]