Repository navigation
docs(gates): delete the spec-docblock gate's stale "symbol is ZERO" reason - #19786
Merged
Merged
Conversation
…eason The header section headed "`counts.symbol` is ZERO on this corpus", the case-4 note and the case-5 sentence said the whole spec tree holds exactly one symbol-anchor-shaped span and that it does not resolve, and used that as the reason the live-corpus self-test does not assert `symbol > 0`. Re-derived with this gate's own corpus and resolver: true at the census tree 08e38c6 (symbol 0, one shaped span, unresolved); false at fa29803 and at 4b23e4f (symbol 6, all 6 declaration, 7 shaped spans, the websocket.zod.ts one still unresolved and still pinned). The false reason is deleted, not replaced. No sentence is added; no code, assertion or case changes. Claude-Session: https://claude.ai/code/session_01UDXER3sdqfeVYpEWZs5mZx Co-authored-by: Claude <noreply@anthropic.com>
os-warren
marked this pull request as ready for review
September 23, 2026 05:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #17242
Clause-②: no
Round 6: one file,
scripts/check-spec-docblock-symbol-anchors.mjs, comments only.What was stale
The header section headed "
counts.symbolis ZERO on this corpus", the case-4 note and one sentence of the case-5 note said the spec tree holds exactly one symbol-anchor-shaped span and that it does not resolve. They gave that as the reason the live-corpus self-test does not assertsymbol > 0.Re-derived
Instrument: this gate's
CORPUSandscripts/symbol-anchors.mjsat4b23e4fab5, swept over a checkout of each tree.websocket.zod.tsspan08e38c6377(census)fa29803417(re-census)4b23e4fab5(base)Controls: each older tree's own instrument gives the same counts. The gate at
fa29803417prints 3437 / 6 (6) / 467.08e38c6377has no gate, so its ownsymbol-anchors.mjswas run with the same corpus spec and read 0 / 2639 / 183. The six resolving spans are 2 indata/analytics.zod.ts, 3 inkernel/functional-completeness.tsand 1 inui/action-params.zod.ts.⇒ The text was true at the census tree and false at
fa29803417and at base.Change: deleted only
websocket.zod.tspart was still true, and itsCENSUS_RESIDUALrow still carries the doc, the citation and the repair.No reason replaces them. Claim audit: 0 sentences added or changed in the file. The self-test still asserts
fileLeveland does not assertsymbol > 0. The ratchet recommendation recorded by #19733 is unchanged and not restated here.Verification, at
d23edb4eef--list-unresolvableand--self-test: exit 0 at base and head, stdout byte-identical (cmp0; sha25644a6a984…,af5d0039…,1dcc0b91…), stderr empty.8865ec39…). Lit control: a one-character code mutation makes it differ. The self-test floor stays 124.check-scripts-symbol-anchors(sweeps this file): exit 0. Anchors 3694 → 3691 and file-level 3642 → 3639; symbol 52 and declined 14 unchanged. The −3 are the three code spans in the deleted text. Its self-test exits 0.dispatch-gates: 31 derived, 31 run, all exit 0;--ranreads 0 NOT-MEASURED, 0 UNRUN. Outside that total: the 2 workflow-valued families and the Test Core steps run in CI only. The 14 changeset-pending families do not apply (no changeset: a repo-root script in the private root package).Acceptance notes
symbol > 0live control is proposed. Case 1 already assertsdeclaration >= 1andliteral >= 1through the sameCORPUSon its fixture. A live floor would add a constraint on authors and no new detection. Noted, not filed; carrier: none.Generated by Claude Code