* feat(#3987): guard slug re-derivation, and record why the swallow shape cannot be guarded Epic #3473's Decision 1 requires the wrong call site be UNREPRESENTABLE. #3984 measured that two of the nine §8 rules had no guard at all and recorded both as "Shipped - test-covered". This closes one of them, proves the other cannot be closed the same way, and corrects two false claims I merged yesterday. 1. §8.3 - scripts/lint-slug-derivation-drift.cjs. generateSlugInternal (src/core-utils.cts) is the canonical owner; #3883 removed 11 inline copies. Nothing prevented a twelfth: no slug guard existed in scripts/ or eslint-rules/. The detector is STATEMENT-scoped and matches the shape the real copies took - one statement carrying BOTH .replace(<negated class>, '-') and .replace(/^-+|-+$/, ''). Statement scoping is what buys the precision: the loose LINE-level form yields 18 hits with 7 unrelated, a material false-positive rate. Measured on the tree: 5 flags, 2 TRUE, 3 SANCTIONED, 0 FALSE. The three sanctioned sites are allowlisted with a reason each, following lint-phase-enumeration-drift's form rather than a bare denylist. The owner itself is listed explicitly even though it escapes by construction - an implicit escape is a latent bug, and the next person to touch line 192 would not know the guard depended on it. 2. Both TRUE positives were live defects, not style. scripts/qa-smell-ratchet.cjs reproduced the canonical formula including the 60-cap but trimmed BEFORE truncating - the #2849 bug - and never transliterated. The divergence is total, not cosmetic: canonical "privet-mir-privet-mir-privet-mir-privet-mir-privet-mir-prive" inline "tail" Cyrillic collapsed to nothing and only the ASCII remainder survived, so the ratchet was keying on wrong identifiers for any non-ASCII input. tests/planning-inspect.test.cjs carried a helper whose comment claimed parity with getPhaseDirFromPhaseId. That function now transliterates; the helper did not, so the test asserted against a stale formula while looking correct. Both now route through the seam. 3. §8.5 - measured, and deliberately NOT shipped. A candidate detector (swallowing catch + errno-retry-set test in the same function) gives 26 flags across 11 functions: 0 TRUE, 26 FALSE. Every one is best-effort unlink/rm/close cleanup, lost-rename-race backoff, or a deliberate null fallback. The file-scoped variant is worse at 71. Worse than the noise: the only known true instance was removed by #3885, so there is NO POSITIVE CONTROL - the guard cannot be shown capable of failing, which this repo requires of every drift guard. Shipping it would add a guard nobody can trust and nobody can test. The ADR now records the measurement and the reason, keeps §8.5 at "Shipped - test-covered", and points at the #1884 regression test as what actually enforces it. An honest "not detectable at acceptable precision" beats a guard that only ever passes. 4. Two claims I merged into the ADR yesterday were wrong. §8.9 said 17 of 19 subsumed children have a test citing their issue number, and that #3364 and #3812 have none. Both halves are false, and the claim came from a NUMBER-GREP - inside an amendment whose own subject is that a text match is not a fact. #3364 IS cited: tests/runtime-marker-resolution.test.cjs:107, T3 installMarkerResolvesWhenEnvAndConfigAbsent_3897 (#3364), asserting at :115-119. #3812 IS covered: tests/gen-state-md-docs.test.cjs:374, asserting at :382. Corrected to 19 of 19. #3812 does carry a real finding, though a different one: it is PARTIALLY DELIVERED on a CLOSED issue. The shipped fix declares cardinality for frontmatter keys, but #3812's stated acceptance was about the ## Current Position BODY section, and docs/reference/state-md.md:196-208 still has no normative single-valued/overwrite sentence and no pointer to ## Performance Metrics for history. Recorded in the ADR and left for #3812 to re-open - fixing it here would bury a scope question inside an unrelated PR. Note on B6: this ADDS a guard, and B6 said the net count must fall. #3951 already amended that clause - a guard ledger is a claim about COVERAGE, not count - which is what makes adding this one honest rather than contradictory. Verified: the guard flags 0 on the fixed tree, and PROVES IT CAN FAIL - a fresh inline copy planted in src/ makes it exit 1 naming the exact statement. All three sanctioned sites were confirmed exempt BY the allowlist, not by accident of the pattern, by re-attributing each to a non-exempt path and watching it flag. build:lib, lint and lint:ci all exit 0. Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(#3987): add the changeset fragment Doc-only, so it carries forward from the verified sha rather than costing a second matrix run. Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3987): §8.5 IS guardable — I was wrong, and the guard found a live defect Two orthogonal reviews. The correctness review overturned my central judgment, and it was right. 1. I concluded §8.5 was "not detectable at acceptable precision" and recorded that in the ADR. False. My evidence was 26 flags / 0 TRUE / 26 FALSE. The reviewer pointed out what I had not: all 26 false positives are CLEANUP verbs - rmSync 54, unlinkSync 43, closeSync 17, chmodSync 12 - and the obvious narrower predicate was never tried. A swallowed cleanup is legitimate best-effort. A swallowed CREATION is a precondition silently lost, which is exactly the #1884 shape. Measured properly, in three stages: swallowing catch 911 + try-block calls a CREATION verb 24 + enclosing function references a *_ERRNOS set 0 0 flags, 0 false positives. The `*_ERRNOS` naming key is empirically total - all 10 retry/tolerate sets in src/ follow it. My second claim was worse. I wrote that no positive control exists because #3885 removed the only true instance, so the guard "cannot be shown capable of failing". That is self-refuting: this very PR's slug guard proves-it-can-fail on a synthetic tree, and the pre-#3885 blob is available as exactly such a fixture. It is now the control, and it works in both directions - the rule flags 0c43d853e^:src/planning-workspace.cts at line 210, the line the fix commit's own message cites, and reports zero on the post-fix code. I stopped at the first negative result on the option that meant less work. Shipped as eslint-rules/no-swallowed-precondition.cjs, wired into the existing src/**/*.cts ESLint block rather than a scripts/lint-*-drift.cjs: no script in scripts/ requires typescript/espree/acorn, and scripts/ ships to consumers, so a .cts-parsing standalone guard would add a devDep at consumer runtime. The ESLint block already parses .cts for free. 2. The guard immediately found a live defect of the same class. src/capability-lock.cts swallowed a mkdirSync on the lock directory, then acquireLock classified the follow-on failure as `code !== 'EEXIST' → return null`. A real EACCES/EROFS makes openSync(lockPath,'wx') fail ENOENT, which is not EEXIST - so a fatal filesystem error was laundered into "lock unavailable". Same defect as #1884, different laundering target. Fixed the way #3885 fixed #1884: the creation failure propagates. Regression test proven fail-first by hand - with the fix stashed, EACCES was laundered to null; restored, it throws. The strict rule does NOT catch this shape (its errno classification is an inline literal, not a named set). The rule is deliberately left strict: the broadened form had 2 false positives - capability-lock.cts:408, the deliberate EEXIST steal protocol, and commonjs-marker.cts:131, which returns a distinct documented outcome. The gap is noted in code rather than papered over with a noisy predicate. 3. The security review found the slug guard's exemption FAILED OPEN. currentFunction was never reset, and only a column-0 `function` declaration updated it, so exemption bled from an allowlisted declaration to the next one. generateSlugInternal exempted 50 lines for an 11-line function. A re-derivation planted anywhere in that window was silently exempt - the same fail-open shape that produced a blocker in #3897, and an allowlist is a SUBTRACTION so a mismatch fails open by construction. Extent is now tracked by real brace depth, and a test plants a violation after each allowlisted function's real closing brace and asserts it IS flagged. 4. Also from the security review: the guard was a CI-DoS and narrower than I claimed. Its unbounded [^\]]* was re-scanned from every `.replace(/[^` start: 54.3s on a 1.28MB line. It imported MAX_REGEX_LITERAL_LEN and never called readRegexLiteralAt - the bounded tokenizer that exists for exactly this. Now routed through it with a 2MB file cap: ~200ms. 15 of 25 genuine re-derivations evaded. Widened to catch replaceAll, {1,}, \s*-wrapped classes, escaped ], literal new RegExp(...), five trim spellings, .split().join(), and multi-line .replace( args - still 0 false positives. Two forms still evade and are documented as deliberate gaps with negative tests: the two-statement/temp-var form and new RegExp built from a variable. Both need data flow, and guessing at it is how a guard becomes noisy. Also fixed: // inside a string truncated the line, a ; inside the collapse regex split the statement (a one-character bypass), and SCAN_EXT omitted .mjs/.tsx/.jsx. 5. A regression I introduced, caught by the same review. qa-smell-ratchet.cjs top-level-required a build output that is not git-tracked, so the script hard-failed MODULE_NOT_FOUND before build:lib - including for --help, which previously had no build dependency. The require is now lazy at the point of use. 6. Four of my own tests were vacuous or weak. T9's input yielded an identical string under the buggy formula, so it passed on the implementation it was meant to catch. T12 compared maxLen null vs 60 on an 18-char name, where they agree trivially. T9-T12 all asserted generateSlugInternal directly, so they would pass unchanged if both call-site fixes were reverted. And prove-it-can-fail was scoped to scanRepo, never the CLI - dropping main()'s exit-code line would have kept every row green. All rewritten with discriminating inputs, per-call-site rows that red when the fix is reverted, 59/60/61 boundaries, an entirely-non-alphanumeric row, and a CLI row asserting the real subprocess exit code and both sanitizeForReport sites. Verified: both guards flag 0 on the tree and both prove they can fail. The swallow rule's control is confirmed in both directions - pre-#1884 shape flagged, post-#3885 shape clean. build:lib, lint and lint:ci all exit 0. Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(#3987): record that §8.5 IS guardable, and correct a correction that made a ledger worse Three ADR corrections, two of them to text this branch wrote hours ago. §8.5 advances to Enforced. Its previous entry said the rule was not detectable at acceptable precision. That was wrong twice: the 26 false positives were uniformly CLEANUP verbs, which is a reason to narrow the predicate rather than abandon it, and the claim that no positive control exists was self-refuting - the pre-#3885 blob is available as a fixture and this repo's own guards prove-it-can- fail on synthetic trees. Narrowed to creation verbs plus a *_ERRNOS reference: 911 -> 24 -> 0 flags, 0 false positives, control confirmed in both directions. The entry keeps the wrong reasoning visible, because a high false-positive count being evidence the predicate is wrong - not evidence the rule is unguardable - is the transferable part, and the first negative result is most seductive when it is also the answer that means less work. §8.9's correction is itself corrected. The original 17-of-19 claim was CORRECT for the predicate it stated; this branch silently swapped cited -> covered and declared 19 of 19. #3812 appears in zero test files. Changing what a word means to make a ledger read better is a worse failure than the miscount it claimed to repair. Both predicates are now reported separately - 18 of 19 cited, 19 of 19 covered - because §8.9 asks for a test NAMING each child, so 18 is the number that answers it. #3812 is also re-opened for real, rather than the first draft's promise that it could be. §8.3 stays Shipped - test-covered rather than advancing. The slug guard catches the copy-paste class and a dozen variants, but two forms still evade by decision (temp-var split, new RegExp from a variable) because both need data flow. Naming them keeps the status honest: the wrong call site is much harder to write, not unrepresentable. Closes #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(#3987): backfill changeset pr number Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3987): replace my own wall-clock assertion, and close the guard that let me write it CI went red on ubuntu shard 2/3. The failing test was mine, and the failure was the test, not the code. a 1.28MB line ... scans in well under a second (was 54.3s pre-fix) 7368ms It asserted ELAPSED TIME. ~200ms locally, 7.4s on a shared CI runner. The bound introduced for the MAJOR-2 DoS fix works - 7.4s against a 54.3s pre-fix baseline is the fix doing its job - but an absolute wall-clock threshold on shared hardware is a race, not an assertion. CLAUDE.md says so directly: "Clock Seams: Do not assert on wall-clock time." I wrote the anti-pattern the project bans, in a PR about guards. Raising the threshold would only move the flake. The row now asserts a DETERMINISTIC bound instead: an instrumentation seam on drift-scan.cjs counts readRegexLiteralAt calls and characters examined, and the test asserts charsExamined stays under an absolute ceiling. Measured on the same 1.28MB fixture: 120,000 calls, 48,000,000 chars - two orders under the ceiling. The pathological fixture is kept; only the thing being asserted changed. Proven to still discriminate: with MAX_REGEX_LITERAL_LEN raised to simulate the unbounded pre-fix behavior, the same fixture does not complete in 120 seconds, versus ~0.3s bounded. It is a real regression test, not a tautology. Then the second half, which is the same defect class as the rest of this PR. eslint-rules/no-elapsed-assertion.cjs matched only the EXACT identifiers ^(elapsed|duration|took|ms)$. I used `elapsedMs`. It evaded the rule entirely. tookMs, durationMs, elapsedTime and msElapsed evade the same way. A guard that cannot see the violation it exists to catch is exactly what this PR is about - it just happened to be an existing rule rather than one of the two I came here for, and it was found because I committed the violation it should have blocked. Widened to /^(?:elapsed|duration|took|ms)(?:[A-Z]\w*)?$/ plus a narrow start/endMs delta pair. Deliberately NOT a blanket *Ms suffix: a first draft did that and produced 2 false positives on `timeoutMs` in plan-phase-stall-detection, which is a configured timeout and not a measurement. Verified negative on params, items, forms, terms, dirnames, timeoutMs, cacheTtlMs and staleAfterMs. Measured over the five files carrying camelCase timing identifiers: 0 true positives beyond my own, so nothing else needed rewriting. The rule's own test file gains a row asserting `elapsedMs` flags, proven to fail against the pre-widening rule - the same prove-it-can-fail standard both new guards in this PR are held to. Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3987): a comment I added leaked a Claude reference into every runtime install The runner went red with 4 failures in tests/install.test.cjs: Leaking: .hermes/scripts/lib/drift-scan.cjs Leaking: .qwen/scripts/lib/drift-scan.cjs The instrumentation seam added for the deterministic bound carried a comment naming CLAUDE.md as the source of the no-wall-clock-assertions rule. scripts/ SHIPS to consumers, so that comment was installed verbatim into hermes and qwen trees, and the install suite scans for exactly this - a Claude-specific reference reaching a non-Claude runtime. The rule is real and worth citing; the filename is not portable. The comment now says "this repo's test rules" and states the rule inline, which is what a reader of an installed tree actually needs anyway. Worth noting what caught it: not lint, and not the two guards this PR adds - the install suite's full-tree scan, which exists precisely because a shipped file is read by runtimes that have never heard of CLAUDE.md. Same lesson as the rest of this PR from the other direction: the check that matters is the one that can see the surface where the defect actually lands. Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3987): a test fixture swallowed 46 git exit codes and produced a silent false negative CI red on ubuntu shard 3/3: tests/health-validation.test.cjs:2029 expected exactly one W024, got [{"code":"W006", ...}] Not caused by this branch, and the evidence is decisive rather than a hunch: the SIBLING test at :2039 builds the IDENTICAL fixture with the identical commitsAhead and asserts the same thing, and it PASSED in the same process, same file, same run. Same input, both outcomes - which rules out logic, ordering, sharding and environment, and leaves a per-invocation nondeterministic failure inside one fixture build. The mechanism is an unchecked exit code, 46 times over. The W024 fixture performs ~46 runGit spawns and never checks a single one. runGit returns failures as DATA and never throws, so one silently-failed `git commit` yields 19 commits instead of 20, or a silently-empty `git rev-parse HEAD` yields a blank state_head. Either drops readStateHeadFreshness below the advisory threshold, W024 never fires, and only W006 remains. Reproduced exactly: 20 commits -> ["W006","W024"]; 19 -> ["W006"]; blank state_head -> ["W006"] - byte-identical to the CI assertion dump. The arithmetic is what hid it. At threshold-1 and threshold+1 a lost commit still produces the asserted answer; only the exactly-at-threshold cases sit one commit from a false negative. Two of the seven tests are in that position, and CI hit one. That is why it had never been seen before, and why it surfaced now: this branch adds three test files, which reshuffles the cost-weighted shard partition and moved this file into a chunk where the latent flake fired. My files were checked as suspects first and cleared: all fixtures mkdtemp-unique, no process.chdir, no .planning/ writes, no git spawns, and node --test gives per-file process isolation regardless. Fixed at the cause, not the symptom. A mustGit wrapper throws on a non-zero exit with the command, exit code and stderr, and all nine call sites route through it. The fixture now asserts its OWN preconditions before the assertion under test runs - the seed head is non-empty, and `git rev-list --count <seed>..HEAD` equals the requested commitsAhead - so a fixture that did not build what it claims fails loudly as a FIXTURE ERROR naming got-versus-asked, instead of quietly handing a weaker input to the assertion. Proven: dropping one commit now raises FIXTURE ERROR: requested commitsAhead=19 but git rev-list --count reports 18 where it previously produced a silent ["W006"] pass-for-the-wrong-reason. 64/64 tests in that block pass unperturbed. Deliberately NOT done: no threshold change, no retry, no loosened assertion, no skip. The assertion was correct; the input was silently wrong. Worth naming, because it is the same shape from the other side: this PR ships eslint-rules/no-swallowed-precondition.cjs, whose entire subject is a swallowed precondition failure being laundered into a plausible downstream outcome. This fixture is that defect in test code - the swallowed git failure was laundered into a legitimate-looking "W024 did not fire". The rule does not cover test fixtures, so the connection is noted at the fix site rather than enforced. Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3987): two tests wrote to committed files; the shard packing decided when that mattered CI red on windows-latest shard 1/3 only: "gen-exit-code-registry: CLI" > "a --write run redirected to a tmpdir leaves every committed artifact untouched" AssertionError: hooks artifact must be untouched The Linux runner passed the same sha at 40425/40425. It is Linux-only, so a Windows-scheduling defect is structurally invisible to it. Root cause, established by measurement rather than inference. tests/cli-exit.test.cjs appended a corruption marker to the REAL COMMITTED hooks/lib/exit-code-registry.js, held it corrupted across a full subprocess, and restored it in a finally. tests/exit-code-registry.test.cjs reads that same real file before and after its own subprocess and asserts byte equality. If it samples while the other test holds the file corrupted, it fails. The landmine is pre-existing, from2ea5efc15(#3911). What this branch changed is WHEN the two run together. scripts/run-tests.cjs shards by cost-weighted LPT over the sorted unit list, so adding three test files repacks the bins: merge-basec3e667df3(838 files): cli-exit -> shard 1, exit-code-registry -> shard 3 HEAD 03b342601 (841 files): BOTH in shard 1, same argv chunk, one node --test process, concurrent Co-location is necessary but not sufficient - Linux shard 1/3 also had both and passed. Windows loses because TEST_CONCURRENCY defaults to 2 there against 4 elsewhere, spawn cost is ~10x, and the sibling corruptor holds one of only two slots through a ~90s tsc compile. That turns a sub-second overlap into seconds. Not a path-separator or case-sensitivity issue, and not CRLF - .gitattributes pins * text=auto eol=lf. Redirection was not at fault either: ensureScriptsOut derives all five --out flags correctly and gen-exit-code-registry.cjs honours them with no __dirname escape. Fixed at the cause: no test writes to a committed file any more. Both corruptors now copy to a mkdtempSync tmpdir, corrupt the COPY, and point the generator at it. Repinning or reordering the shards would have turned CI green while leaving the landmine armed for the next reshuffle. That required closing an inconsistency between two sibling generators. gen-exit-code-registry.cjs already accepts --out/--scripts-out/--hooks-out/--dts-out/--sh-out and honours them under --check; gen-hooks-cli-exit.cjs hardcoded OUTPUT_PATH and had no flag surface at all, so its corruptor could not be redirected anywhere. It now takes --out in the same style, honoured by both --write and --check, and is a no-op when absent - verified: a bare --check on the default path still exits 0. ensureScriptsOut moved to tests/helpers/exit-code-artifact-flags.cjs and both test files import it. Hand-rolling a second copy of the flag derivation would have been a re-derivation of exactly the kind this PR ships a guard against. Verified: both tests still detect corruption (proven by defeating the check and watching them red, with a positive control showing an uncorrupted copy exits 0); SHA-256 of hooks/lib/exit-code-registry.js and hooks/lib/cli-exit.js identical before and after running both rewritten bodies, and git reports nothing under hooks/ modified - that is the property that was violated. A repo-wide search for the corrupt-then-restore-in-finally shape against hooks/ found no other instances. One detail worth recording: the tmpdir test keeps --declaration pointed at the real committed declaration rather than copying it, because the generated banner embeds path.relative(REPO_ROOT, declarationPath) - copying it would produce a false drift unrelated to the injected corruption. The declaration is read-only on that path and never written. Refs #3987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
309 lines
14 KiB
JavaScript
309 lines
14 KiB
JavaScript
#!/usr/bin/env node
|
||
'use strict';
|
||
|
||
/**
|
||
* Shared anti-divergence scanner machinery (epic #3180, ADR-3180 Decision 4).
|
||
*
|
||
* Extracted from `scripts/lint-plan-count-drift.cjs` (#3183) so that
|
||
* `scripts/lint-milestone-window-drift.cjs` (#3184) and any future
|
||
* `scripts/lint-<derivation>-drift.cjs` guard consume ONE tree-walk /
|
||
* root-confinement / literal-tokenizer / sanitizer implementation instead of
|
||
* each copying it verbatim — the exact generative-fix-divergence class this
|
||
* epic exists to remove, now applied to the guards themselves (see
|
||
* `.gsd/phase/refactor-3184-milestone-window-single-owner/40-design.md`,
|
||
* "Rejected: let the new drift guard copy Phase 1's tree-walk /
|
||
* root-confinement / sanitizer").
|
||
*
|
||
* `lint-plan-count-drift.cjs` re-exports every symbol it exported before this
|
||
* extraction (`readRegexLiteralAt`, `MAX_REGEX_LITERAL_LEN`, `isInsideRoot`,
|
||
* `sanitizeForReport`), so `tests/plan-count-single-owner.test.cjs` — the
|
||
* ReDoS and root-confinement regression net for this exact machinery —
|
||
* continues to pass unchanged and is the regression net for this move too.
|
||
*/
|
||
|
||
const fs = require('node:fs');
|
||
const path = require('node:path');
|
||
|
||
// Longest regex literal this scanner will consider, in characters. Real
|
||
// plan/summary filename filters (and milestone-window regex literals) are far
|
||
// shorter; the bound is what keeps the scan linear. The tokenizer restarts at
|
||
// every `/` on the line (so that a literal preceded by a stray unpaired `/`
|
||
// is still found, matching the previous regex's "find anywhere" behaviour),
|
||
// which without a per-literal bound would be quadratic on a pathological
|
||
// line. With it the whole-line cost is O(n * MAX_REGEX_LITERAL_LEN) with no
|
||
// backtracking at all.
|
||
const MAX_REGEX_LITERAL_LEN = 400;
|
||
|
||
// Directory names this scanner never descends into or reports out of —
|
||
// `.git` (repo internals, e.g. a persisted CI token in `.git/config`),
|
||
// `node_modules` (thousands of third-party files, none of them authored
|
||
// source), `dist` (build output). Named once and used at BOTH skip sites
|
||
// below: the cheap `entry.name` fast path in `walk`, and the resolved-path
|
||
// component check in `isUnderSkippedDir` — a symlink whose OWN name is not
|
||
// in this set but whose target resolves through a directory that IS (e.g.
|
||
// `src/g -> ../.git`, `src/nm -> ../node_modules`) must still be skipped, or
|
||
// the name-only check is a trivial bypass.
|
||
const SKIP_DIR_NAMES = new Set(['node_modules', 'dist', '.git']);
|
||
|
||
/**
|
||
* Read the JS regex literal starting at `line[start]` (which must be `/`).
|
||
* Returns `{ text, end }` — `text` includes the delimiters and any trailing
|
||
* flags, `end` is the index one past the literal — or null if no literal
|
||
* closes within MAX_REGEX_LITERAL_LEN characters.
|
||
*
|
||
* Single left-to-right pass, no backtracking. It models the two constructs a
|
||
* backtracking pattern gets wrong, which is why this is a tokenizer and not a
|
||
* regex:
|
||
* - `\x` escapes consume BOTH characters, so an escaped `\/` never
|
||
* terminates the literal;
|
||
* - inside a `[...]` character class a bare `/` does NOT terminate, so
|
||
* `/PLAN[\\/].*\.md$/` is one literal rather than two fragments. The
|
||
* previous regex silently MISSED every re-derivation using a
|
||
* cross-platform path-separator class for exactly this reason.
|
||
*/
|
||
// Deterministic regression seam for the MAJOR-2 bound (issue #3951/#3987): a
|
||
// counter of how many characters this tokenizer has actually examined, so a
|
||
// test can assert the bound HOLDS (total work stays a small linear multiple
|
||
// of the number of scan attempts × MAX_REGEX_LITERAL_LEN) without resorting
|
||
// to a wall-clock elapsed-time assertion, which this repo's test rules ban
|
||
// ("Clock Seams: Do not assert on wall-clock time.") and which is exactly
|
||
// what flaked on a slow shared CI runner. `resetRegexScanStats`/
|
||
// `getRegexScanStats` are read-modify-reset around a single scan under test;
|
||
// they are process-global and NOT safe under concurrent scans, which is fine
|
||
// for this synchronous, single-threaded CLI tool and its tests.
|
||
let regexScanStats = { calls: 0, charsExamined: 0 };
|
||
|
||
function resetRegexScanStats() {
|
||
regexScanStats = { calls: 0, charsExamined: 0 };
|
||
}
|
||
|
||
function getRegexScanStats() {
|
||
return { ...regexScanStats };
|
||
}
|
||
|
||
function readRegexLiteralAt(line, start) {
|
||
if (line[start] !== '/') return null;
|
||
regexScanStats.calls++;
|
||
const limit = Math.min(line.length, start + MAX_REGEX_LITERAL_LEN);
|
||
let inClass = false;
|
||
let i = start + 1;
|
||
for (; i < limit; i++) {
|
||
const ch = line[i];
|
||
if (ch === '\\') {
|
||
i++; // escape consumes the next character, whatever it is
|
||
continue;
|
||
}
|
||
if (ch === '\r' || ch === '\n') {
|
||
// a literal cannot span lines
|
||
regexScanStats.charsExamined += i - start;
|
||
return null;
|
||
}
|
||
if (ch === '[') {
|
||
inClass = true;
|
||
} else if (ch === ']') {
|
||
inClass = false;
|
||
} else if (ch === '/' && !inClass) {
|
||
// Trailing flags are bounded by the SAME `limit` as the literal body
|
||
// itself (not `line.length`) — a literal followed by an unbounded run
|
||
// of lowercase letters must not make `text` grow past
|
||
// MAX_REGEX_LITERAL_LEN either.
|
||
let end = i + 1;
|
||
while (end < limit && line[end] >= 'a' && line[end] <= 'z') end++;
|
||
regexScanStats.charsExamined += end - start;
|
||
return { text: line.slice(start, end), end };
|
||
}
|
||
}
|
||
regexScanStats.charsExamined += limit - start;
|
||
return null;
|
||
}
|
||
|
||
// Symlinks report `isDirectory()`/`isFile()` as false on the Dirent from
|
||
// `readdirSync`, so a symlinked `.cts` (or a symlinked directory containing
|
||
// one) was previously invisible to this scanner — an evasion of a guard
|
||
// whose stated design principle (ADR-3180 Decision 4a) is whole-repo
|
||
// discovery with no allowlist. Resolve each entry with `fs.statSync` (which
|
||
// follows symlinks) to classify it, skipping broken links. `ctx.visitedRealDirs`
|
||
// guards against a symlink cycle sending `walk` into infinite recursion.
|
||
//
|
||
// Every sibling drift guard in `scripts/` that does NOT import this module
|
||
// (`lint-phase-id-drift.cjs`, `lint-package-identity-drift.cjs`,
|
||
// `lint-portable-timeout.cjs`, `lint-test-file-count.cjs`,
|
||
// `lint-allow-test-rule-refs.cjs`) uses the `Dirent` classification straight
|
||
// off `readdirSync` and does NOT follow symlinks at all. This scanner follows
|
||
// them so a symlinked source file cannot evade ADR-3180 Decision 4a's
|
||
// whole-repo discovery — root confinement (`isInsideRoot` below) is the price
|
||
// of doing so: without it, a symlink planted anywhere under a scan directory
|
||
// could walk this scanner out to read and report arbitrary files elsewhere on
|
||
// disk.
|
||
//
|
||
// DIRECTORY vs FILE symlinks are confined to two DIFFERENT roots, tracked as
|
||
// `ctx.scanDirRoot` (the realpath of the current top-level scan-dir entry,
|
||
// e.g. `<realRoot>/src`) vs `ctx.realRoot` (the whole repo):
|
||
// - a DIRECTORY symlink is descended ONLY if its resolved realpath is
|
||
// inside `ctx.scanDirRoot` — NOT merely inside `ctx.realRoot`. Without
|
||
// this, `src/up -> ..` (or `-> <realRoot>`) resolves inside the repo
|
||
// root and `walk` descends the ENTIRE repo, reporting violations under
|
||
// paths like `tests/not-src.cts` or `docs/other.cts` — files the caller's
|
||
// scan-dir list scopes it OUT of. This is a deliberate, fail-CLOSED
|
||
// trade-off: a directory symlink pointing elsewhere INSIDE the repo (but
|
||
// outside the scan directory) is simply not followed. The alternative —
|
||
// descending it — is exactly the whole-repo sweep this rule exists to
|
||
// prevent, and a fork PR could use that sweep to redden `lint:ci` on
|
||
// files this guard was never meant to read. The narrower rule is worth
|
||
// more than the missed edge case.
|
||
// - a FILE symlink is still scanned if its resolved realpath is inside
|
||
// `ctx.realRoot` (the whole repo, not just the scan directory) — this is
|
||
// what keeps `src/alias.cts -> vendor/real.cts` covered (test (f)): an
|
||
// aliased file genuinely is part of the compiled surface even when its
|
||
// real target lives outside `src/`, and it is still reported under its
|
||
// canonical (real) path.
|
||
//
|
||
// A resolved path is inside a root only if it IS that root or begins with
|
||
// root + separator — a plain `startsWith(root)` would also accept a sibling
|
||
// directory whose name merely starts with the root's name (`/repo-evil`).
|
||
function isInsideRoot(realPath, realRoot) {
|
||
return realPath === realRoot || realPath.startsWith(realRoot + path.sep);
|
||
}
|
||
|
||
// True when `realPath` (already confirmed inside `realRoot` by `isInsideRoot`)
|
||
// resolves THROUGH a skip-list directory anywhere along its path relative to
|
||
// the root — not just when `realPath` itself IS one. This is what closes the
|
||
// symlink bypass the `entry.name` fast path alone cannot: `walk` tests
|
||
// `entry.name` (the symlink's OWN name in its parent directory), but a
|
||
// symlink named something innocuous can still RESOLVE into `.git` /
|
||
// `node_modules` / `dist` (`src/g -> ../.git`, `src/leak.cts ->
|
||
// ../.git/config`, `src/nm -> ../node_modules`) — `isInsideRoot` alone admits
|
||
// all three, because every one of those real paths is still under the root.
|
||
function isUnderSkippedDir(realPath, realRoot) {
|
||
const rel = path.relative(realRoot, realPath);
|
||
return rel.split(path.sep).some((segment) => SKIP_DIR_NAMES.has(segment));
|
||
}
|
||
|
||
// `ctx.scanExt` is a `Set` of file extensions (e.g. `.cts`/`.ts`/`.mts`) the
|
||
// caller wants reported — threaded through `ctx` rather than as a positional
|
||
// parameter so recursive `walk(full, acc, ctx)` calls stay unchanged.
|
||
function walk(dir, acc, ctx) {
|
||
let entries;
|
||
try {
|
||
entries = fs.readdirSync(dir, { withFileTypes: true });
|
||
} catch {
|
||
return acc;
|
||
}
|
||
for (const entry of entries) {
|
||
const full = path.join(dir, entry.name);
|
||
if (SKIP_DIR_NAMES.has(entry.name)) continue; // cheap fast path
|
||
let stat;
|
||
try {
|
||
stat = entry.isSymbolicLink() ? fs.statSync(full) : entry;
|
||
} catch {
|
||
continue; // broken symlink target
|
||
}
|
||
let realPath;
|
||
try {
|
||
realPath = fs.realpathSync(full);
|
||
} catch {
|
||
continue; // broken symlink target (race, or a link stat() followed but realpath cannot)
|
||
}
|
||
if (stat.isDirectory()) {
|
||
// Directories (symlinked or real) are confined to the CURRENT scan
|
||
// directory root, not merely the repo root — see the comment above
|
||
// `isInsideRoot` for why (`src/up -> ..` whole-repo sweep).
|
||
if (!isInsideRoot(realPath, ctx.scanDirRoot)) continue;
|
||
if (isUnderSkippedDir(realPath, ctx.realRoot)) continue; // symlink resolves through a skipped dir
|
||
if (ctx.visitedRealDirs.has(realPath)) continue; // symlink cycle guard
|
||
ctx.visitedRealDirs.add(realPath);
|
||
walk(full, acc, ctx);
|
||
} else if (stat.isFile() && ctx.scanExt.has(path.extname(entry.name))) {
|
||
// Files are confined to the whole repo root — a symlinked FILE whose
|
||
// real target lives outside the scan directory but inside the repo
|
||
// (e.g. `src/alias.cts -> vendor/real.cts`) is still part of the
|
||
// compiled surface and must be scanned.
|
||
if (!isInsideRoot(realPath, ctx.realRoot)) continue;
|
||
if (isUnderSkippedDir(realPath, ctx.realRoot)) continue; // symlink resolves through a skipped dir
|
||
if (ctx.visitedRealFiles.has(realPath)) continue; // two symlinks, same real file
|
||
ctx.visitedRealFiles.add(realPath);
|
||
acc.push(realPath);
|
||
}
|
||
}
|
||
return acc;
|
||
}
|
||
|
||
/**
|
||
* Whole-repo tree-walk driver shared by every `lint-<derivation>-drift.cjs`
|
||
* guard. Resolves `root`, walks each of `scanDirs` filtered to `scanExt`
|
||
* (symlink-following, root-confined, cycle-guarded — see `walk` above), reads
|
||
* each discovered file, and calls `onFile(relPath, text)` for it — `relPath`
|
||
* is repo-relative and already the file's canonical (real) path, so a
|
||
* per-file exemption keyed on `relPath` matches consistently regardless of
|
||
* which symlink reached it.
|
||
*
|
||
* `onFile` returns an array of violation objects (or an empty array / null /
|
||
* undefined for "no violations in this file"); `scanTree` flattens them all
|
||
* into one returned array. Pure I/O orchestration — detection logic lives
|
||
* entirely in the caller's `onFile`.
|
||
*/
|
||
function scanTree({ root, scanDirs, scanExt, onFile }) {
|
||
const violations = [];
|
||
let realRoot;
|
||
try {
|
||
realRoot = fs.realpathSync(root);
|
||
} catch {
|
||
return violations; // root itself does not exist / is unreadable
|
||
}
|
||
for (const dir of scanDirs) {
|
||
const scanDirPath = path.join(root, dir);
|
||
let scanDirRoot;
|
||
try {
|
||
scanDirRoot = fs.realpathSync(scanDirPath);
|
||
} catch {
|
||
continue; // scan directory itself does not exist / is unreadable
|
||
}
|
||
const ctx = { realRoot, scanDirRoot, scanExt, visitedRealDirs: new Set(), visitedRealFiles: new Set() };
|
||
for (const file of walk(scanDirPath, [], ctx)) {
|
||
const rel = path.relative(realRoot, file);
|
||
let text;
|
||
try {
|
||
text = fs.readFileSync(file, 'utf8');
|
||
} catch {
|
||
continue;
|
||
}
|
||
const found = onFile(rel, text);
|
||
if (found && found.length > 0) violations.push(...found);
|
||
}
|
||
}
|
||
return violations;
|
||
}
|
||
|
||
// A reported fragment AND a reported file path are both attacker-controlled
|
||
// source text on a fork PR (a repo can legally track a filename containing
|
||
// control bytes, so the path is exactly as attacker-controlled as the
|
||
// fragment), and both are written straight to a CI log. Replace C0/C1
|
||
// control bytes (ANSI escapes included) with a visible \xNN, AND the
|
||
// non-Latin-1 formatting/bidi/line-separator codepoints below with \uNNNN, so
|
||
// a crafted literal or filename cannot rewrite the terminal rendering of the
|
||
// report or hide/reorder its own text:
|
||
// - U+200B-U+200F: zero-width space/joiners and directional marks
|
||
// - U+2028/U+2029: Unicode LINE SEPARATOR / PARAGRAPH SEPARATOR (line
|
||
// breaks a `\n`-only log scan would not catch)
|
||
// - U+202A-U+202E: bidi embedding/override controls (RLO etc.)
|
||
// - U+2066-U+2069: bidi isolate controls
|
||
function sanitizeForReport(text) {
|
||
return text
|
||
// eslint-disable-next-line no-control-regex -- the control range IS the target
|
||
.replace(/[\x00-\x1f\x7f-\x9f]/g, (c) => '\\x' + c.charCodeAt(0).toString(16).padStart(2, '0'))
|
||
.replace(/[\u200B-\u200F\u2028\u2029\u202A-\u202E\u2066-\u2069]/g, (c) => '\\u' + c.charCodeAt(0).toString(16).padStart(4, '0'));
|
||
}
|
||
|
||
module.exports = {
|
||
SKIP_DIR_NAMES,
|
||
isInsideRoot,
|
||
isUnderSkippedDir,
|
||
walk,
|
||
readRegexLiteralAt,
|
||
MAX_REGEX_LITERAL_LEN,
|
||
sanitizeForReport,
|
||
scanTree,
|
||
resetRegexScanStats,
|
||
getRegexScanStats,
|
||
};
|