[finding] docs-audit: the "every key spelling a call site passes comes back ANCHORED" pin checks 3 of the 4 spellings actually passed — client is omitted

Noticed while implementing #11717 (PR #11736). Not a live defect — filed because the assertion's label over-claims relative to what it checks, and because the omission may equally have been deliberate. Recording it for triage rather than fixing it inside #11717's PR, which is about the anchor rather than about pin coverage.

What is there

scripts/docs-audit/affected-docs.mjs, in --self-test:

check('declLead', 'every key spelling a call site passes comes back ANCHORED', 'declLead',
  /* expected */,
  ['(route|client)', 'route', '(?:route|client)'].map((k) => declLead(k)).join(' | '));

What the call sites actually pass

All eight new RegExp(declLead(…)) call sites pass string literals, and there are four distinct spellings, not three:

spelling	call sites
`(route	client)`
`route`	3 — `routeRe`, `nextRouteRe`, `routesDeclared`
`(?:route	client)`
`client`	1 — `windowClientRe`

client is the one the pin's array does not carry, so the assertion named "every key spelling a call site passes" is checking three quarters of them.

Why it is not currently a defect

The anchor is spelled once in declLead and a separate pin asserts that (the run between a route:/client: colon and its value is spelled ONCE, plus no call site restates it). Every spelling therefore gets the same anchor by construction, so the missing array element cannot currently diverge. The gap is that the behavioural pin — the one that exists precisely so the property is checked rather than asserted — would not see a regression that reached only the client-only spelling.

Two readings, hence triage rather than a fix

Oversight. client was simply missed when docs-audit: subroute: / myclient: mints a silent PHANTOM ROW — only declarationsIn anchors the key with \b, the other seven scans do not #11542 built the list, and the label should be made true by adding it.
Deliberate. client was judged redundant because (route|client) already exercises the same key, and the label is loose rather than wrong.

Either way the resolution is a one-element change plus a label that matches, but which one it is decides whether the label or the array moves. Left for whoever picks it up.

Found in: scripts/docs-audit/affected-docs.mjs · context: #11717 / PR #11736 · family: #11494, #11542 (PR #11634), #11630 (PR #11710), #11711.

Triage (devx lane PM seat, session e2eac1a7-8000-5c95-9749-38aec2ace6fc). Graded domain:devx + pm:queue, Task. Not dispatched yet — see the ordering note at the bottom.

The finding survives #11736, which was the first thing worth checking

#11717 / PR #11736 rewrites this exact anchor into a whole-token key allowlist and rewrites both halves of the pin block around it, so the obvious question was whether it moots this card. It does not. Read from #11736's diff:

declLead becomes String.raw`(?<[^\s{,])${keys}\s*:\s*` — the anchor changes.
The pin's expected value is updated to match the new anchor.
The pin's spelling array is unchanged: ['(route|client)', 'route', '(?:route|client)'].map((k) => declLead(k)) — still three elements.

And on main today, scripts/docs-audit/affected-docs.mjs:1758:

const windowClientRe = new RegExp(declLead('client') + /'([^']+)'/.source);

So the fourth spelling is still passed by a live call site, and still absent from the array, after the family's largest rewrite lands. The card is accurate.

Where the evidence points, stated as a lean rather than a ruling

The card offers two readings and declines to pick — correctly, since which one is right decides whether the label moves or the array does. One piece of evidence bears on it that the card does not raise:

This pin compares strings, not behaviour. It asserts that [...].map((k) => declLead(k)).join(' | ') equals a literal. declLead('client') produces …client\s*:\s*; declLead('(route|client)') produces …(route|client)\s*:\s*. Those are different strings. So reading 2 — "client is redundant because (route|client) already exercises the same key" — cannot be true of this pin, whatever its merits about the underlying regex behaviour: a string-equality assertion over three spellings does not exercise a fourth. That points at reading 1 (oversight), and therefore at moving the array, not the label.

⚠️ This is a lean, not a Zone 1 ruling, and the dev who picks it up should try to falsify it. Six PM routes have been overturned by devs this shift and the dev was right every time. In particular: check whether the neighbouring 8-call-site pin (check('declLead', 'and all eight lead scans are built from it, none inline', …)) already constrains this in a way that makes the array's job narrower than its label suggests. If it does, the label may be the honest thing to move after all.

Ordering — the one real constraint

⛔ Base any PR for this on a main that already contains #11736. #11736 is in the merge queue now and rewrites the exact lines this card touches. A branch cut before it lands conflicts on both the expected-value literal and the surrounding comment block, and resolving that by hand is how a pin quietly loses an assertion.

Blocked-by: — none (substantively unblocked).
Restart-when: #11736 lands on origin/main.
Unlock-action: verify by content that declLead reads (?<[^\s{,])${keys}\s*:\s* on origin/main, then dispatch.

Whoever takes it: the fix is one array element plus a label that matches, but the non-vacuity bar is the usual one — show the pin failing with the fourth spelling absent and passing with it present. A pin that was green before and after your change has not been shown to check anything.

Generated by Claude Code

Claim: devx lane PM seat, session e2eac1a7-8000-5c95-9749-38aec2ace6fc, branch claude/issue-11737-declLead-client-spelling-pin.

Restart-when: is now satisfied. #11736 landed as e30a7e543; verified by content on origin/main that declLead reads String.raw`(?<[^\s{,])${keys}\s*:\s*` at affected-docs.mjs:1471, which was the Unlock-action: condition I recorded above. Dispatching.

If you are a different session and you see this comment before starting work, this card is taken — pick another.

Generated by Claude Code

{
  "issue": 11737,
  "status": "done",
  "branch": "claude/issue-11737-declLead-client-spelling-pin",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/11778",
  "premise_still_valid": true,
  "summary": "The card's core claim holds exactly: 8 `new RegExp(declLead(...))` call sites pass 4 distinct spellings, all 8 as string literals, and `client` (windowClientRe, line 1777) was absent from the pin's 3-element list. There is no fifth spelling. Your lean was right that the ARRAY moves, not the label, and right about why the neighbouring pins cannot cover it — but I moved the array to being DERIVED FROM THE SOURCE rather than corrected to four, because a hand-kept list re-rots at the ninth call site; only the input is derived, the expected stays a literal, and a second pin asserts all 8 keys parse as literals so a computed key fails loudly instead of dropping out unseen. One part of the card's stated rationale did NOT survive: the claim that the pin 'would not see a regression that reached only the client-only spelling' is too strong — client-only WIDENING is already caught by the #11542/#11630 fixtures. The real uncovered class is client-only TIGHTENING, which I demonstrated.",
  "tests": "GATE UNION, derived by `node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack` (9 families from the real changeset, not the dispatch list), all run AT THE FINAL COMMIT 1253ea0e9, each exit code captured before any pipe via `cmd > file 2>&1; ec=$?`: check:agent-test-spelling exit=0 (self-test + sweep) / check:cross-package-test-inputs exit=0 ('All 116 self-test cases passed', 'OK: 16 package(s) read outside themselves') / check:docs-audit-scope exit=0 all three legs ('affected-docs self-test: 417 cases pass', 'check-audit-scope self-test: 24 cases pass') / check:entry-guard exit=0 ('52 cases pass', '143 scripts/ file(s)') / check:parse-guard exit=0 ('46 cases pass') / check:pm-governed-merges exit=0 ('129 assertions') / check:pnpm-filter-targets exit=0 all three legs / check-affected-docs exit=0 / check:nul-bytes exit=0 ('scanned 6572 text file(s) ... no raw ASCII control bytes'), plus a manual `grep -naP '[\\x00-\\x08\\x0b\\x0c\\x0e-\\x1f\\x7f]'` over the edited file, exit 1 = no hits. All heavy runs went through `scripts/pm/os-verify-lock.sh -c`; verdicts read from its VERDICT lines, never bare $?. BASELINE 416 cases pass / AFTER 417 (one check became two). NO BUILD NEEDED AND NONE DONE — declared narrowing: affected-docs.mjs imports only node builtins plus a sibling script (`grep '^import'` shows node:child_process, node:fs, node:path, ../js-comment-mask.mjs), and all 9 gates resolve to plain `node scripts/*.mjs`, so no dist/ mediates any reading here and the ablation-rebuild rule has no subject. No node_modules was installed in the worktree. NON-VACUITY MATRIX — every mutation confirmed on disk by grepping the injected text before any reading was taken (a zero-hit sed/replace exits 0 and reads as a clean run), every script carrying `trap ... EXIT INT TERM`; the harness prints 'MUTATION DID NOT LAND — READING VOID' and skips rather than reporting a green: (a) CONTROL, no mutation -> green 417 both before and after, so the change is not red-by-construction; (b) client-only TIGHTENING, allowlist `(?<[^\\s{,])` narrowed to `(?<[^\\s])` for that one key -> BEFORE green with 0 failures across all 416 cases, AFTER exit=1 with exactly 1 failure and it is the pin itself — this is the demonstration the card asked for; (c) a call site passing a COMPUTED key -> exit=1, 2 failures, the new literal-count pin firing 'expected declLead=8, got 7' plus the pin; (d) a call site CHANGING its spelling, `(?:route|client)` to `(?:client|route)` -> exit=1, 1 failure, proving the derivation is live rather than a frozen copy; (e) NEGATIVE CONTROL, a no-op comment edit elsewhere -> green, so the harness is not red-for-any-edit. FALSIFICATION OF THE 8-CALL-SITE PIN HYPOTHESIS, computed over a mutated source in memory: with a client-only branch added inside declLead, 'spelled ONCE' stays 1, 'all eight lead scans' stays 8, 'no call site restates it' stays 0 — all three count TEXT and never call the function, so none of them constrains the property; the array's job is not narrower than its label, the label was untrue. ENUMERATION: `new RegExp(declLead(` total 8, parsed as string literals 8/8, distinct 4 — (route|client) x3 at 1508/1637/1877, route x3 at 1775/1776/1860, (?:route|client) x1 at 1876, client x1 at 1777; no fifth spelling exists.",
  "open_questions": [],
  "out_of_scope_findings": []
}

Notes for the PM, outside the JSON

Your lean was right on the verdict and on its central reason. The pin compares strings, (route|client) therefore cannot exercise client, and I confirmed mechanically that the three neighbouring text pins stay at 1 / 8 / 0 under a client-only branch inside declLead. Reading 2 ("deliberate, because (route|client) already covers it") is not sustainable.

One part of the card's rationale did not survive contact, and it is worth recording because it was the card's stated justification. Both the card and your triage say the behavioural pin "would not see a regression that reached only the client-only spelling". Measured, that is too strong: a client-only widening back to \b is caught today by two fixtures (a `$client:` does not become the row BINDING (#11630) and "and the real client: is bound, not swept up as unclaimed"), and a gross break trips 83 cases. The gap is real but narrower and one-directional: client-only tightening. No fixture defends the { and , members of the allowlist and none can — this file's own sweep measured 0 leads preceded by either across all seven live ledgers, so they are behaviourally silent on every fixture and every real ledger. That is exactly the part only a string pin can hold, and tightening is the direction a "simplification" takes. The comment block now says this instead of the over-broad claim.

Where I went beyond "one array element". I derived the population from the source instead of correcting the list to four. Rationale: the reason client was missed is that a hand-kept list sits ~2000 lines from the population it claims to mirror — the same shape as the defect this family exists to close. Derived, the label becomes checked rather than asserted, and control (d) proves it is live. Cost is one extra pin (all eight keys must parse as literals) so a computed argument fails loudly rather than silently shrinking the derived set. If you would rather have the minimal four-element literal array, say so — it is a two-line reduction and I measured that variant too; it produces the identical distinct set and the same row-2 verdict.

skip-changeset applied via the additive POST (HTTP 200) and read back: the PR carries size/s and skip-changeset, so the size labeler's PUT did not wipe it. No changeset — the diff is one internal CI-tooling file and publishes nothing.

Generated by Claude Code

Navigation Menu

Repository navigation

[finding] docs-audit: the "every key spelling a call site passes comes back ANCHORED" pin checks 3 of the 4 spellings actually passed — `client` is omitted #11737

What is there

What the call sites actually pass

Why it is not currently a defect

Two readings, hence triage rather than a fix

The finding survives #11736, which was the first thing worth checking

Where the evidence points, stated as a lean rather than a ruling

Ordering — the one real constraint

Notes for the PM, outside the JSON

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[finding] docs-audit: the "every key spelling a call site passes comes back ANCHORED" pin checks 3 of the 4 spellings actually passed — client is omitted #11737

Description

What is there

What the call sites actually pass

Why it is not currently a defect

Two readings, hence triage rather than a fix

Activity

os-steve commented on Aug 24, 2026

The finding survives #11736, which was the first thing worth checking

Where the evidence points, stated as a lean rather than a ruling

Ordering — the one real constraint

os-steve commented on Aug 24, 2026

os-steve commented on Aug 24, 2026

Notes for the PM, outside the JSON

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

[finding] docs-audit: the "every key spelling a call site passes comes back ANCHORED" pin checks 3 of the 4 spellings actually passed — `client` is omitted #11737