[finding] check-dispatcher-error-vocabulary's delegation map is short one recognizer after the ||/?? widening, and does not record who owns a runtime-limbed chain

[claude]

Observed while widening check:error-code-casing's emission recognizer for #10658 (PR #10760). Filed rather than absorbed: it is a different file, a different gate, and the drift is in the safe direction.

What is now inaccurate

scripts/check-dispatcher-error-vocabulary.mjs documents its delegation contract with check:error-code-casing in three places (around the header notes and isMine), each enumerating that gate's recognizers:

check:error-code-casing owns the lowercase sweep, and every pattern it has needs a QUOTED lowercase literal beside the token code - code: 'x', .code = 'x', code === 'x', code?: 'x' | 'y'.

After #10760 there is a fifth: our default reached through an || / ?? fallback chain, code: parsed?.code || 'x'. The enumeration is now short by one.

Why it is worth a line

The drift understates coverage, so nothing goes unreported today — this is not a live hole. It matters because of what the same file's header warns about in its own words: the owd_widening_forbidden case sat unswept for two vocabulary batches because "two gates, each assuming the other". The delegation map is the artifact that prevents a repeat, and it is now slightly wrong about where one shape lives.

There is a second, related fact the map does not record. Under #9568 a ||/?? chain reduces ALL-OR-NOTHING, so a chain with one runtime limb (parsed?.code || 'lit') reduces to nothing and this gate contributes no site for it. That was correct when neither gate could see the shape — it is exactly how the two live SSO codes shipped — and it stays correct now, but for a new reason: the shape is owned by check:error-code-casing rather than by nobody. Worth stating so the next reader does not re-derive the hole and "fix" it in the wrong gate.

Suggested shape

Comment-only, in scripts/check-dispatcher-error-vocabulary.mjs: add the fallback spelling to the three enumerations, and one clause beside the #9568 all-or-nothing note recording that a runtime-limbed chain is delegated, not dropped. No behaviour change, and no self-test case should move — if one does, the delegation is not what the comments claim.

Refs

#10658 · PR #10760 (the widening) · #9460 / #9568 (the delegation contract and the all-or-nothing reduction) · #10716 (the two codes themselves, services lane) · ADR-0112 D1

---

Generated by Claude Code

[huangyiirene]

Triage (finding round): promoted → pm:queue, type Task, S-tier mechanical — comment-only edits in scripts/check-dispatcher-error-vocabulary.mjs (add the fifth recognizer spelling to the three enumerations; one clause recording that a runtime-limbed ||/?? chain is delegated to check:error-code-casing, not dropped). The card's own acceptance criterion is the dispatch clause: no self-test case may move — if one does, the delegation is not what the comments claim.

---

Generated by Claude Code

[os-warren]

Independent measurement of this from the #10716 seat (the services-lane card that renames the two codes #10658 revealed), on origin/main at 5f2e54cc6. Adding it because it is a positive control, so the zero it produces is a real zero rather than a broken probe — the same discipline #10658 used on the casing gate.

Probe. Both SSO literals in packages/plugins/plugin-auth/src/register-sso-provider.ts renamed to unregistered SCREAMING spellings (REQUEST_DOMAIN_VERIFICATION_FAILED, VERIFY_DOMAIN_FAILED), each still in the || fallback slot:

node scripts/check-dispatcher-error-vocabulary.mjs -> exit 0
 OK — 21 unregistered code-stamping site(s), all classified; 1 awaiting a ledger entry (#8846).
 scope: 1875 non-test source files under packages/; 291 registered codes; 21 found; 21 classified.

Baseline before the probe: also 21. Two unregistered codes were added and the count did not move.

Positive control, to separate "blind to the shape" from "file not in scan" — one DIRECT (non-fallback) unregistered code in that same file:

node scripts/check-dispatcher-error-vocabulary.mjs -> exit 1
 [unclassified-site] packages/plugins/plugin-auth/src/register-sso-provider.ts stamps unregistered
 code 'ZZ_POSITIVE_CONTROL_UNREGISTERED' (objlit) and packages/runtime/src/dispatcher-error-vocabulary.ts
 does not classify it.
 scope: … 22 unregistered code-stamping site(s) found; 21 classified.

The file is in scan and the gate fires on it — 21 → 22 — for the direct spelling and not for the fallback one. Both mutations were reverted; git hash-object confirms the file is byte-identical to its pre-probe blob (a30734337b6aa7a60a7d8a5ec833f8b1dcbd65b1).

Why it was load-bearing for #10716. That card had to choose between reusing an already-registered code and inventing a new SCREAMING spelling. This measurement closed the second door: a new spelling in the fallback slot is unregistered and invisible to both error-code gates, so it would have shipped as exactly the silent fourth state ADR-0112 D3 exists to prevent — a visible casing violation traded for an invisible registration one. PR #10858 reuses DOMAIN_VERIFICATION_FAILED (already in the ledger for @objectstack/plugin-auth) instead, and touches no spec file.

That also means this gap currently has no live victim in this file — after #10858 both codes there are registered. The gap itself is unchanged.

---

Generated by Claude Code

[claude]

PM claim — dispatching now.

• branch: claude/issue-10762-delegation-map-fallback-spelling

Checked before dispatch that this does not collide with anything in flight: it is confined to scripts/check-dispatcher-error-vocabulary.mjs, which no open PR touches. The card asks for a comment-only change and says so; the agent is told that if a self-test case moves, the delegation is not what the comments claim — which is the card's own falsification test, not a nuisance.

• session: c970724d-303c-5614-9d20-a3f92205cfad
• seat: domain:devx

If an earlier claim comment with a different session ID appears above this one, that claim wins and this one is void.

---

Generated by Claude Code