docs(test): align substrate matrix with coverage map

Add calls/coverage to SUBSTRATE_SCENARIO_BY_TABLE; fix glossary
architecture anchor; clarify CONTRIBUTING guard scope.

Author: SutuSebastian

.github/CONTRIBUTING.md

@@ -39,7 +39,7 @@ Then open a PR on GitHub into **`main`**.
 - **Public API** — Anything exported from the package entry (`src/index.ts` → `src/api.ts`, `config.ts`, shared types) should have **JSDoc** that reads well in hovers and in published typings.
 - **Layers** — Keep boundaries clear: [architecture.md](../docs/architecture.md) (`cli` → `application` → infrastructure). Don’t let CLI concerns leak into parsers or the DB layer.
 - **Before you open / update a PR** — `bun run check` (or at least `bun run test` + `bun run typecheck` while iterating).
-- **Golden queries (Tier A)** — If you change `fixtures/minimal/` or schema/query behavior expected by [fixtures/golden/](../fixtures/golden/), run `bun scripts/query-golden.ts --update`, review diffs, and commit updated JSON under `fixtures/golden/minimal/`. Prefer **fixing the indexer** when output changes for the wrong reason; only refresh goldens when the new rows are correct. See [docs/golden-queries.md](../docs/golden-queries.md) and the coverage map [docs/testing-coverage.md](../docs/testing-coverage.md). New tables should add a substrate scenario (or extend `index-table-stats`); `bun run test:scripts` enforces recipe + table coverage.
+- **Golden queries (Tier A)** — If you change `fixtures/minimal/` or schema/query behavior expected by [fixtures/golden/](../fixtures/golden/), run `bun scripts/query-golden.ts --update`, review diffs, and commit updated JSON under `fixtures/golden/minimal/`. Prefer **fixing the indexer** when output changes for the wrong reason; only refresh goldens when the new rows are correct. See [docs/golden-queries.md](../docs/golden-queries.md) and the coverage map [docs/testing-coverage.md](../docs/testing-coverage.md). New tables should add a substrate scenario (or extend `index-table-stats`); `bun run test:scripts` runs `query-golden-coverage-matrix.test.mjs` (every bundled recipe + `SUBSTRATE_SCENARIO_BY_TABLE` pin-downs).
 - **Golden queries (Tier B)** — Against a **local** clone, use `bun run test:golden:external` with `CODEMAP_ROOT` / `--root`. Copy [fixtures/golden/scenarios.external.example.json](../fixtures/golden/scenarios.external.example.json) to `scenarios.external.json` if you need custom scenarios; goldens under `fixtures/golden/external/` are gitignored — do not commit snapshots from proprietary trees.
 - **Style** — Match Oxfmt/Oxlint; prefer **straight-line code** and extracted helpers over long nested blocks.
 

docs/glossary.md

@@ -604,7 +604,7 @@ TS shape for one row of the `type_members` table.
 
 ### `unresolved_calls` (table)
 
-Staging queue for call sites that **`resolveCalls`** could not bind after the bindings pass. Rows carry `file_path`, `caller_scope`, `callee_name`, and call-site position; deleted when resolved or when the call row is removed. Bundled recipes: `unresolved-call-sites`, `call-resolution-stats`. See [architecture § Call resolution](./architecture.md#schema).
+Staging queue for call sites that **`resolveCalls`** could not bind after the bindings pass. Rows carry `file_path`, `caller_scope`, `callee_name`, and call-site position; deleted when resolved or when the call row is removed. Bundled recipes: `unresolved-call-sites`, `call-resolution-stats`. See [architecture § `calls` / `unresolved_calls`](./architecture.md#calls--function-scoped-call-edges-deduped-per-file-strict).
 
 ### `unresolved_calls_residual`
 

docs/testing-coverage.md

@@ -34,7 +34,7 @@ Every `templates/recipes/<id>.sql` has **≥1** scenario in `fixtures/golden/sce
 
 ## Substrate tables — SQL pin-down scenarios
 
-Recipe goldens prove query _behavior_; these scenarios pin **persisted rows** on the minimal corpus:
+Recipe goldens prove query _behavior_; these scenarios pin **persisted rows** on the minimal corpus. Pin-down ids enforced in CI: `SUBSTRATE_SCENARIO_BY_TABLE` in `scripts/query-golden-coverage-matrix.test.mjs` (plus every bundled recipe id). `index-table-stats` and `call-resolution-stats` are additional aggregate/residual scenarios on the same corpus.
 
 | Table                                 | Scenario id                                             |
 | ------------------------------------- | ------------------------------------------------------- |

scripts/query-golden-coverage-matrix.test.mjs

@@ -28,6 +28,8 @@ const SUBSTRATE_SCENARIO_BY_TABLE = {
   function_params: "function-params-createClient",
   boundary_rules: "boundary-rules-ui-no-api",
   unresolved_calls: "unresolved-call-sites",
+  calls: "calls-createClient-resolved",
+  coverage: "coverage-rows-after-ingest",
   jsx_elements: "index-table-stats",
   jsx_attributes: "index-table-stats",
   try_catch: "try-catch-rethrow-heuristics",