Close the If-Match gap on delete/restore/associations/permissions; make total:null explicit

[cuibonobo]

Summary

This started as a sweep of five open "records" issues (#32, #34, #35, #36, #57). Reading each one against the current code (post-#51/#65) showed most of the batch had already landed:

• Core sync: adopt the shared conformance fixtures; fix the PATCH body shape; add the intent-split endpoints (core #52) #32 — closed already, via Run the core#52 conformance fixtures in CI; bump dependencies #65.
• Core sync: ID authority — accept client-minted record IDs, validate always, 409 on duplicates (core #55) #34 (client-minted IDs) — already fully implemented: POST /records accepts and validates body.id (charset/length/reserved-prefix → 400, duplicate → 409, timestamp-skew check), with tests (records.test.ts:748-785) and docs (docs/api.md) already in place.
• Core sync: undelete endpoint — POST /records/:id/undelete (core #60) #36 (undelete endpoint) — already fully implemented: route, idempotency, 403/404 cases, and docs all present.

That left one real gap and one piece of defensive hardening, both fixed here:

• Core sync: If-Match optimistic concurrency + the one-versioning-rule wire surface (core #48, #61, #62) #35 (If-Match / optimistic concurrency) — PATCH, undelete, and migrate already honored If-Match, but the spec's endpoint list is longer: DELETE /records/:id, POST /records/:id/restore/:version, POST /records/:id/associations, POST /records/:id/associations/delete, and PUT /records/:id/permissions didn't read the header at all, even though ScopedStack (@haverstack/core 0.10.0) has accepted an ifVersion option on every one of those methods since the dependency bump. The conformance-fixtures package (v0.2.0) only ships an If-Match fixture for PATCH so far, so nothing in CI was catching this. Wired If-Match → ifVersion through all five remaining handlers.
• Query response envelope: total must be null over the wire, and cursor is the only end-of-results signal #57 (total envelope) — ScopedStack.query() already guarantees total: null, and it was already forwarded correctly, but the route trusted result.total rather than asserting the wire guarantee explicitly. Hardcoded total: null in both query handlers (GET /records, POST /records/query) so the guarantee holds independent of which query path produced the result. The versions/types bare-array envelope question this issue also raised was already answered correctly — no change needed there.

Changes

• src/routes/records.ts: thread If-Match through DELETE, restore/:version, associations (POST + delete), and PUT /permissions; hardcode total: null in both query handlers.
• tests/routes/records.test.ts, tests/routes/associations.test.ts, tests/routes/versions.test.ts: match/mismatch (412 version_conflict) tests for each newly-wired endpoint.
• docs/api.md: document the full If-Match endpoint list and the total/empty-page envelope rules.

No code changes were needed for #34 or #36 — they're already done.

Test plan

• npm run typecheck
• npm run lint
• npm run format:check
• npm test — 225/225 passing (10 new tests, no regressions)

---

Generated by Claude Code