* enhance(#4223): default-off interaction capture for gsd-ui-auditor via the chrome-devtools CLI gsd-ui-auditor is chartered to audit interaction and handed a capture driver with no interaction verb: `npx playwright screenshot` cannot click, fill, hover, press or snapshot, so a hover state, an open menu, a focus ring or a form's validation state never appears in its evidence and every Experience Design finding degrades to code reading. Implements the shape approved at triage, not a new capability: - capabilities/ui/capability.json declares `workflow.ui_interaction_capture` (boolean, default false) on the capability that already owns the auditor (ADR-894 one-owner invariant); capability-registry.cjs regenerated. - gsd-core/workflows/ui-review.md reads the key through gsd_run and hands it to the auditor as `interaction_capture:` in the spawn <config> block — the auditor carries no gsd_run resolver, so the key travels by value. - agents/gsd-ui-auditor.md gains an anchored interaction-capture section AFTER the static block. With the key on and a Chrome binary resolved it starts the `chrome-devtools` CLI (chrome-devtools-mcp, floor ^1.8.0) on an --isolated profile, opens the dev URL the static block reached, takes the a11y snapshot for element uids, captures the baseline and a Tab focus-ring state, drives the UI-SPEC's interactive components, saves console output, and stops the daemon unconditionally. Key off, no dev server, or no Chrome: one status line, and the Playwright-only static path runs exactly as before — the static fence is untouched. Needs only Bash: no MCP server, no tools: change. Chromium-only by nature; Firefox/WebKit stay on Playwright. `wait_for` is MCP-only, so readiness is polled through evaluate_script. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * test(#4223): bind the interaction-capture shape and containment - manifest, generated registry, config schema and config-set/loadConfig all know workflow.ui_interaction_capture as a default-off boolean, and hand-written non-booleans fall to the slice default - the orchestrator reads the key and hands it down; the auditor never grows a gsd_run dependency - the static fence stays Playwright-only and the interaction fence chrome-devtools-only, so key-off is today's path - the interaction fence runs under bash with a stub driver on PATH: key off / absent / no dev server / no Chrome invoke nothing; the happy path starts first and stops last on the [selected] pageId with the documented flags; a failed capture is removed and not counted; new_page and start failures still honour the stop-only-if-started rule; CHROME_BIN and CHROME_DEVTOOLS_MCP_VERSION overrides flow through - docs/CONFIGURATION.md row shape; registered in the docs-guard lane Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * docs(#4223): document workflow.ui_interaction_capture and its how-to - docs/CONFIGURATION.md: one row in the workflow.* table, default-off - docs/AGENTS.md: the gsd-ui-auditor entry names the key and what the interaction-capture section adds, skips and never claims - docs/how-to/enable-ui-interaction-capture.md: turn it on, read the `**Interaction captures:**` outcomes, what it does not do, turn it off - docs/README.md: index the how-to beside live-DOM verification Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * chore(#4223): add changeset Added-type fragment; pr: carries the issue number until the PR exists. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * enhance(#4223): use the /gsd:ui-review namespace form in the auditor's prose Claude-facing source (agents/, workflows/) uses the /gsd:<cmd> namespace; the hyphen form is retired there and the slash-command-namespace guard rejects it. docs/ keep the hyphen form by convention. Emitted-Drift-Ack-Growth: gsd-ui-auditor.md — #4223: the anchored default-off interaction-capture section (prose + one bash fence) appended after the static Playwright block inside <screenshot_approach>, plus one `**Interaction captures:**` line in each of the two report templates, one completion-checklist line and one Step-3 sentence. The static fence is byte-identical to next; nothing was removed or reordered. Emitted-Drift-Ack-Growth: ui-review.md — #4223: a two-line config-get read + true/false normalisation in step 0 and one `interaction_capture:` line in the spawn <config> block with a three-line note on why the value travels by prompt. No step, gate, or dispatch shape changed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * enhance(#4223): per-run daemon session, bounded navigation, and step failures that count Three findings from the pre-file adversarial review of the interaction fence, folded in: - `--sessionId <epoch>-<pid>` on every driver call. `start` restarts whatever daemon shares its session and --isolated isolates only the browser profile, so two concurrent audits — or an audit beside the operator's own CLI daemon — would otherwise stop each other. The CLI accepts hex and dashes only; the id is validated by the test stub. - `new_page --timeout 30000`: the one verb that takes a bound, placed before every verb that does not, so a hung page is caught first. - a failed take_snapshot or press_key now increments the failure count and is named on stdout; two clean screenshots can no longer read as `0 failed` after the step that gives the interactions their uids failed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * enhance(#4223): subshell-unique session id, CRLF-safe page-id parse, stale-snapshot removal Second review round, both reviewers: - session id is `<epoch>-<BASHPID>-<RANDOM>`: `$$` is inherited by a subshell, so two audits forked from one parent in the same second shared an id and could stop each other's daemon (driven by the reviewer) - `tr -d '\r'` before the `[selected]` parse so a CRLF-emitting driver under Git Bash still matches the `$` anchor, and `|| true` on the assignment so a failed new_page cannot abort the block under `set -e -o pipefail` before the unconditional stop - a failed take_snapshot removes any snapshot.txt it left or inherited from a reused directory, so stale uids never drive the interactions - `<config>` placeholder is `{interaction_capture}`, lowercase like its `{phase_dir}` / `{padded_phase}` siblings — the block is a prompt template, not a bash heredoc - how-to: the `not captured` row no longer claims the daemon started Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * enhance(#4223): check new_page's exit status before parsing its output; regression cases for the edges Third review round: - a new_page that prints a page line and then exits non-zero is a failed navigation, not a page id: the exit status is checked in an `if` before the output is parsed (driven by the reviewer against the previous `|| true`, which masked exactly that) - regression cases for what the last two rounds added: CRLF driver output, a stale snapshot removed on failure, partial-output new_page failure, and the whole fence under `set -e -o pipefail` (both the failed-navigation path and the happy path) - the harness whitelist gains `date`; the session-id assertion now requires all three parts, so a silently empty epoch cannot hide again Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * enhance(#4223): keep gsd-ui-auditor under the DEFAULT-tier size cap; changeset pr placeholder - the three review folds pushed agents/gsd-ui-auditor.md to 25179 bytes, over the 24576-byte hard cap tests/agent-size-budget.test.cjs enforces; the interaction section's comments are tightened to the same content in fewer bytes (23559 now). No bash changed — the fence's own tests and the real-browser run are unchanged. - .changeset/vivid-yaks-fly.md carries the policy placeholder `pr: 0`, which the post-create backfill rewrites to the PR's own number. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * chore(#4223): set changeset fragment pr to 4477 * test(#4223): compare the fence's status path with the separator the fence uses On the windows-latest lane the happy-path case failed on `\interaction` vs `/interaction` alone: the fence joins "$SCREENSHOT_DIR/interaction" with a literal slash, and the assertion built its expectation with path.join. Every other case in the file passed on that lane, including the CRLF and errexit/pipefail ones. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PanfY8KaLb4RVVubcUoGP6 * test(#4223): drop the inert file-header allow-test-rule marker Review round 1 on #4477: the `source-text-is-the-product` marker sat at line 2, outside no-source-grep's 8-line lookahead of every readFileSync site (the first is ~60 lines down), so it suppressed nothing. It was also unnecessary: every read in this file is a .md/.json path, which the rule does not trigger on. Deleted rather than relocated — there is no site to relocate it to. Negative control: `eslint` on the file is clean without it. * chore(#4223): regenerate the platform-conformance-tier lists for the new test Review round 3 on #4477. `next` gained chore(#4591)'s platform-conformance-tier gate after this branch opened; its two committed lists must name every file under tests/, and this PR's tests/ui-interaction-capture.test.cjs had never been in them. Once the branch was updated against next the lists were stale and three jobs went red on head 575667dd: lint-tests (gen-platform-conformance-tier --check), conformance test (macos-latest) at 546 !== 547, and shard 1/3's fragment-single-edit-propagation, which sees the same staleness as regen:derived touching files beyond the fragment edit under test. Regenerated with the repo's own generators, no hand-editing. The general tier goes 546 -> 547 and the macOS tier 196 -> 197, each by exactly this one entry; both --check arms are clean. Verified the red is this PR's own file and not base drift: at upstream/next both generators report "list matches" (546 / 196), and our committed copies were byte-identical to next's before this commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015CBQTeGX1JYHF5DRWp4wvZ * fix(#4223): bound, confine and trap the chrome-devtools driver fence Round 4 — three findings in one fence, interleaved on the same lines, so one commit: - Every driver call is time-bounded. `cdt <ceiling> <verb>` runs the client as a background job in its own process group (`set -m`) under a watchdog that kills the whole group at the ceiling — TERM, then KILL two seconds later. One pid is not enough: npm forwards SIGTERM only to its direct child, so killing `npx` alone leaves the client holding the fence's stdout and a `$(cdt … new_page)` capture blocked past the ceiling (driven against a real npx tree by the round's adversarial review; the pid-only first cut of this commit had exactly that hole). The watchdog is an exec'd bash (`"$BASH" -c`), never a `( … )` subshell: a subshell inherits bash's saved copies of the caller's stdio (the fds ≥10 a function-level `>/dev/null` redirect leaves behind) and holds them open, so a runner waiting for EOF waited out the whole 60 s ceiling whenever a watchdog outlived its kill — measured as the intermittent 30 s test run the review flagged; 0/60 after. It polls the job's process GROUP (`kill -0 -- -pgid`, every 0.1 s) and stands down by itself once the group is empty; nothing ever signals it. The group, not the leader pid: a child can outlive the leader while holding the `$(cdt … new_page)` pipe, and a leader-pid poll stood down at once and left the substitution open-ended (driven by the round's adversarial review at 6× the ceiling; a pgid cannot be reused while any member lives, which a bare pid can). The daemon `start` launches is spawned detached (its own session) and never in that group. Two platforms forced the never-signalled shape. Under bash 3.2.57 the earlier `trap … TERM; sleep & wait $!` form ignored its TERM in 3 of 300 fast calls and slept out the whole ceiling — CI's macos job hanging 30 s right after `start`. On Git Bash a signal to a watchdog still starting up hung the fence's `wait` for it: 18 of 20 fence tests at the harness's 30 s cap in 3 of 3 full-file runs, while a fence slowed by xtrace, or three tests run alone, never hit it (a startup race; the mechanism is not pinned further). Polling: 0/300 slow calls and 0 orphaned sleeps under 3.2.57 and 5.2, the fence suite 20/20 in 3 of 3 full-file runs on Git Bash 5.2.37 (fractional `sleep 0.1`: driven on GNU, msys and busybox sleep; BSD sleep documents it). A clock that cannot launch (`sleep … || exit 0`) stands the watchdog down rather than firing at once and killing a healthy call — by design that leaves a hung call unbounded, the pre-round-4 behaviour, instead of failing a healthy one. A hung call returns once its group is gone: at the ceiling, plus up to the 2 s TERM-to-KILL grace. The KILL after the grace is sent only to a group that is still alive: a pgid freed during the grace can be reused, and an unconditional KILL could hit an unrelated group (the round's review). `start` (npx fetch + Chrome launch) gets CHROME_DEVTOOLS_START_TIMEOUT (180 s), every verb CHROME_DEVTOOLS_STEP_TIMEOUT (60 s). timeout(1) is absent on macOS and this agent carries no gsd-tools resolver, hence a bash watchdog rather than either. - --allowUnrestrictedPaths -> --workspace "$INTERACTION_DIR": the driver may write under the run's interaction/ directory and nowhere else. Relative, like every --filePath (unchanged from rounds 1-3): the daemon resolves both against one cwd (chrome-devtools-mcp 1.9.0 spawns it with cwd: process.cwd() and path.resolve()s both), and a relative path needs no dialect translation — an absolute `pwd -P` path is an msys path on Git Bash, which a Windows-native daemon cannot resolve (CI's windows conformance shard caught the first cut). --workspace is a 1.9.0 flag (absent from 1.8.0's `start --help`, verified), so the documented floor moves from ^1.8.0 to ^1.9.0, where --allowUnrestrictedPaths is deprecated. - `stop` is owed by an EXIT trap after a successful `start`, not by position (it replaces any earlier EXIT trap — none exists in this file); the explicit call keeps it in order, a flag makes the trap a no-op afterwards, and only the shell that installed the trap may act: a subshell copy of the fence state carries CDT_STARTED=1 and, under a timing race CI's ubuntu job hit (reproduced locally at 3/40 under load: the second `stop` came from a subshell pid, never main), issued a second `stop`. The identity is `$(exec /bin/sh -c 'echo "$PPID"')`, not $BASHPID — macOS ships bash 3.2, where BASHPID does not exist and CI's macos conformance job showed the guard comparing empty to empty. The fence was driven under bash 3.2.57 for the injected-subshell, errexit failed-new_page, errexit failed-resize, hung-start, hung-new_page and happy paths. A failed resize_page is a counted failed step now, not the one bare command an errexit runner could abort on. Prose in the section is tightened to pay for the mechanism: 23559 -> 24517 bytes against the 24576 DEFAULT-tier cap. Tests: the stub driver hangs as a real child tree (sh waiting on a child that holds stdout — never an exec), so a pid-only kill fails the new aHungNewPageWhoseChildHoldsStdoutIsStillCutOffAtTheCeiling test (negative- controlled: it blocks for the harness's whole cap on the old wrapper). A hung start and a hung capture are cut off within ceiling + grace + slack and still reach stop; an injected bare failure under errexit reaches stop through the trap, exactly once; an injected subshell call of cdt_stop issues nothing; the happy path issues exactly one stop; every driver call site names a ceiling and the only bare $CDT is the wrapper's own spawn; the start line carries --workspace with the capture directory, every --filePath lies under it, and no code line carries --allowUnrestrictedPaths. A driver whose leader exits at once while a child keeps holding the capture pipe is still cut off at the ceiling (negative-controlled: a leader-pid poll blocks for the harness's whole cap). A watchdog whose clock cannot launch leaves a 300 ms driver call alone (negative-controlled: the trap form kills `start` in under 20 ms). The harness EXPORTS its stub-only PATH — unexported, the exec'd watchdog fell through to bash's compiled-in default PATH and never saw the stub dir — and ships `sleep` there as an exec-wrapper script (portable to Git Bash, pid-preserving). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LgNMb2G67rAJfFQRHEBTAj * fix(#4223): gitignore gate covers the capture directory, and upgrades an existing file Round 4 Blocker. The gate enumerated image extensions, so snapshot.txt (the accessibility tree, with entered form values) and console.txt (which can carry tokens) were committable by `git add .`. The gate now ignores `interaction/` as a directory — the next artifact type is covered by construction — and it appends whatever an existing .gitignore lacks instead of writing once. The write-once form was the same defect one step later: every project that had already run an audit would never have received the new pattern at all. Tests run the gate fence under bash: a fresh file carries every pattern; an image-only file from an earlier audit gains interaction/ and keeps its own header without duplicating present lines; a second run appends nothing. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LgNMb2G67rAJfFQRHEBTAj * test(#4223): declare the interaction-capture anchor as a comment marker The #4324 colon-token gate (slash-command-namespace) landed on next after this branch was opened and reads `<!-- gsd:ui-interaction-capture -->` as an unconvertible /gsd: command token. It is a section anchor of the same family as gsd:live-dom-families and gsd:write-continue, so it is declared in COMMENT_MARKER_TOKENS rather than renamed. Found by running the base-added gates against the merged tree; CI at ca8d2508 predates the gate. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LgNMb2G67rAJfFQRHEBTAj --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Co-authored-by: Tom Boucher <trekkie@nomorestars.com> Co-authored-by: CI Rebase Check <ci@gsd-redux>
439 lines
20 KiB
JavaScript
439 lines
20 KiB
JavaScript
#!/usr/bin/env node
|
|
'use strict';
|
|
|
|
/**
|
|
* docs-guard-registry.cjs — the sole source of truth for which doc-reading
|
|
* test files the docs-guard lane must run.
|
|
*
|
|
* ## Why this is its own module, not a `scripts/ci-test-scope.cjs` RULE
|
|
*
|
|
* A prior version of this PR added a `docs guards` RULE to `RULES` in
|
|
* scripts/ci-test-scope.cjs, on the theory that classify()'s `!codeChanged`
|
|
* normalization (which at the time zeroed fullMatrix/targeted_tests/
|
|
* windows_tests for docs-only diffs) made the RULE inert to classify()'s
|
|
* scope decision. (#4641 later removed `windows_tests` from classify()'s
|
|
* output entirely; the normalization today only zeroes fullMatrix and
|
|
* targeted_tests. This paragraph is historical narration of a rejected
|
|
* design, not a description of current behaviour.)
|
|
*
|
|
* That is true for docs-ONLY diffs and FALSE for MIXED docs+code diffs:
|
|
* `codeChanged` is true whenever ANY changed file is product/pipeline code,
|
|
* so the normalization never runs, and every one of this registry's test
|
|
* files joined `targeted_tests` for every mixed PR. Probed on that version:
|
|
* `node scripts/ci-test-scope.cjs --files "docs/a.md src/semver.cts"`
|
|
* returned 25 targeted_tests, vs. 3 on `origin/next` — an unstated blowup
|
|
* of the scoped/targeted lane on every mixed docs+code PR.
|
|
*
|
|
* Root cause: `RULES` answers "given these changed files, what should
|
|
* test.yml run" for the MAIN scoped-lane pipeline. The docs-guard registry
|
|
* is a LANE MANIFEST for a completely different consumer (the `docs-lint`
|
|
* job in .github/workflows/docs-required.yml, gated on a `docs_changed`
|
|
* step output). Putting a lane manifest inside a scope-classification rule
|
|
* set was the defect; extracting it here removes any path by which it can
|
|
* influence classify() at all.
|
|
*
|
|
* ## Who reads this
|
|
*
|
|
* - .github/workflows/docs-required.yml (`docs-lint` job) — derives the
|
|
* PER-PR-SELECTED subset of this registry from scripts/select-docs-guards.cjs,
|
|
* which is itself driven by this module's DOCS_GUARD_TESTS map. This job has
|
|
* no `paths:` filter, so it always reports a status and can supply the
|
|
* already-required `docs-lint` context; a dedicated `paths:`-filtered
|
|
* workflow cannot be made required without hanging non-docs PRs forever.
|
|
* - scripts/lint-docs-guard-registration.cjs — derives its registration
|
|
* lint's comparison set from this module (so a docs-reading test file
|
|
* that is neither registered here nor exempted fails the lint).
|
|
* - scripts/select-docs-guards.cjs — the pure selector that maps a PR's
|
|
* changed docs/ paths to the subset of this registry that actually needs
|
|
* to run (#3753 follow-up: a flat "run everything" list is disproportionate
|
|
* for a single-file docs typo fix).
|
|
*
|
|
* ## Registry shape (#3753 follow-up)
|
|
*
|
|
* `DOCS_GUARD_TESTS` is a MAP from test file path to the array of docs/
|
|
* paths it actually reads, so a changed-docs-file can be resolved to the
|
|
* narrow subset of guards that read it, instead of always running the
|
|
* entire registry. Each value is a non-empty array of PATTERNS:
|
|
*
|
|
* - a plain path (e.g. `'docs/AGENTS.md'`) matches that exact file only;
|
|
* - a trailing-slash path (e.g. `'docs/adr/'`) matches any changed path
|
|
* under that directory prefix — use this for a test that walks or
|
|
* `readdirSync`s a whole docs/ subdirectory;
|
|
* - the sentinel `'*'` means "run on ANY docs/ change" — reserved for a
|
|
* test that cannot be resolved to a narrower set of paths (the path is
|
|
* computed, looped over an unresolvable variable, or the test walks
|
|
* docs/ generally). Conservative fallback: when in doubt, use `'*'`,
|
|
* never a guessed-narrow path — a false negative here (a guard that
|
|
* silently stops running) is exactly the #3753 defect class this
|
|
* registry exists to prevent.
|
|
*
|
|
* `DOCS_GUARD_TEST_FILES` (derived: `Object.keys(DOCS_GUARD_TESTS)`) is kept
|
|
* as a flat array export so the registration lint and its parity test
|
|
* continue to consume a plain file list without needing to know about the
|
|
* map shape.
|
|
*
|
|
* ## Adding a docs guard
|
|
*
|
|
* Add the test file's path (relative to the repo root, `tests/<file>`) as a
|
|
* key in DOCS_GUARD_TESTS below, with the docs/ paths it reads as the value
|
|
* (or `['*']` if that cannot be resolved narrowly). Do not duplicate this
|
|
* list anywhere else — a second, independently maintained list is exactly
|
|
* the #3753 defect class (10 registered-but-not-run guards, silently
|
|
* drifted) this registry exists to prevent from recurring.
|
|
*
|
|
* Sorted alphabetically by basename for unambiguous diffs.
|
|
*/
|
|
|
|
/**
|
|
* Duplicate of scripts/run-tests.cjs:50's `SUITES` array. That array is not
|
|
* exported by run-tests.cjs (module.exports there is deliberately narrow;
|
|
* run-tests.cjs's own behavior is intentional and out of scope for this
|
|
* registry to alter), so it cannot be imported directly without changing a
|
|
* shared, behavior-locked file.
|
|
*
|
|
* Why this must exist at all: `run-tests.cjs`'s `selectExplicitFiles`
|
|
* (scripts/run-tests.cjs:651) treats any registry entry that EQUALS a
|
|
* SUITES member (e.g. `all`, `unit`) as a suite selector, not a filename —
|
|
* so a typo in DOCS_GUARD_TESTS matching a suite name would silently run
|
|
* the ENTIRE suite inside the required `docs-lint` job instead of erroring.
|
|
* `assertNoSuiteCollision` below rejects that at the registry boundary
|
|
* instead.
|
|
*
|
|
* Divergence risk: if run-tests.cjs's real SUITES list ever changes and this
|
|
* copy is not updated, this check could under- or over-reject. That risk is
|
|
* covered by a parity test (tests/ci-docs-guard-registry.test.cjs) that
|
|
* drives run-tests.cjs's own exported `selectExplicitFiles` behaviorally —
|
|
* for every token here it asserts run-tests.cjs treats it as a suite
|
|
* selector (never "file not found"), and for a control non-member it
|
|
* asserts the opposite — so a real divergence fails that test rather than
|
|
* silently drifting.
|
|
*/
|
|
const RUN_TESTS_SUITES = ['all', 'unit', 'integration', 'install', 'security', 'slow', 'qa'];
|
|
|
|
/**
|
|
* Normalize a registry entry EXACTLY the way scripts/run-tests.cjs's
|
|
* `splitFileList` (:617-625) normalizes a requested token before its SUITES
|
|
* check (:651): strip a leading `tests/` and normalize `\`->`/`. Without this,
|
|
* comparing RAW registry keys (which all carry the `tests/` prefix by
|
|
* convention) against RUN_TESTS_SUITES misses the realistic typo `'tests/all'`
|
|
* entirely — proven by probe: `assertNoSuiteCollision(['tests/all'])` did not
|
|
* throw, and `selectExplicitFiles(allFiles, 'tests/all')` selected all 824
|
|
* files (the whole suite) inside the required docs-lint job.
|
|
*
|
|
* @param {string} t
|
|
* @returns {string}
|
|
*/
|
|
function normalizeForSuiteCheck(t) {
|
|
return t.replace(/\\/g, '/').replace(/^tests\//, '');
|
|
}
|
|
|
|
/**
|
|
* Reject any docs-guard registry entry that collides with a run-tests.cjs
|
|
* suite token (see RUN_TESTS_SUITES doc comment above). Throws with every
|
|
* offending entry named, rather than failing on only the first. Compares
|
|
* entries AFTER normalizeForSuiteCheck, mirroring run-tests.cjs's own
|
|
* splitFileList normalization, so a `tests/`-prefixed or backslash-spelled
|
|
* entry that would collide post-normalization is caught here too.
|
|
*
|
|
* @param {string[]} tests
|
|
*/
|
|
function assertNoSuiteCollision(tests) {
|
|
const collisions = tests.filter((t) => RUN_TESTS_SUITES.includes(normalizeForSuiteCheck(t)));
|
|
if (collisions.length > 0) {
|
|
throw new Error(
|
|
'docs-guard-registry: DOCS_GUARD_TESTS entry collides with a run-tests.cjs SUITES token ' +
|
|
`(${collisions.join(', ')}) — scripts/run-tests.cjs:651's selectExplicitFiles treats a ` +
|
|
'registry entry that equals a suite name as a suite selector, not a filename, so this ' +
|
|
'would silently run the entire suite instead of the intended file(s). Fix the registry entry.',
|
|
);
|
|
}
|
|
}
|
|
|
|
/**
|
|
* Map from docs-guard test file to the docs/ path patterns it reads. See
|
|
* this module's header comment for pattern semantics (exact / trailing-slash
|
|
* dir-prefix / `'*'` sentinel). Every value here was derived by reading the
|
|
* test file's actual read call(s) — not guessed — per #3753's own lesson: an
|
|
* unresolvable read is recorded as `'*'`, never a narrowed guess.
|
|
*/
|
|
const DOCS_GUARD_TESTS = {
|
|
'tests/adr-15-progress-converge.test.cjs': [
|
|
'docs/COMMANDS.md',
|
|
'docs/how-to/run-phases-autonomously.md',
|
|
],
|
|
// Walks docs/adr/ as a directory (builds/reads docs/adr/README.md and
|
|
// fixture ADRs throughout) and separately reads docs/contributor-standards.md.
|
|
'tests/adr-index-gate.test.cjs': ['docs/adr/', 'docs/contributor-standards.md'],
|
|
|
|
// Walks docs/features/ as a directory (the fragment corpus) and asserts the
|
|
// committed docs/FEATURES.md equals the generated projection of it (#3840).
|
|
'tests/features-index-gate.test.cjs': ['docs/features/', 'docs/FEATURES.md'],
|
|
'tests/agent-classification-parity.test.cjs': ['docs/AGENTS.md', 'docs/INVENTORY.md'],
|
|
// #3683: pins the learnings feature section's agreement with the canonical
|
|
// artifact registry (reads docs/FEATURES.md around the extract-learnings
|
|
// entry).
|
|
'tests/learnings.test.cjs': ['docs/FEATURES.md'],
|
|
'tests/analyze-dependencies.test.cjs': ['docs/COMMANDS.md'],
|
|
'tests/autonomous-converge.test.cjs': [
|
|
'docs/COMMANDS.md',
|
|
'docs/how-to/run-phases-autonomously.md',
|
|
],
|
|
'tests/capability-matrix-sync.test.cjs': ['docs/reference/capability-matrix.md'],
|
|
'tests/capability-registry.test.cjs': [
|
|
'docs/tutorials/build-your-first-capability.md',
|
|
'docs/tutorials/install-your-first-capability.md',
|
|
'docs/reference/capability-manifest.md',
|
|
],
|
|
'tests/claude-md.test.cjs': ['docs/COMMANDS.md'],
|
|
'tests/claude-orchestration.test.cjs': ['docs/explanation/claude-orchestration-capability.md'],
|
|
'tests/command-contract.test.cjs': [
|
|
'docs/INVENTORY.md',
|
|
'docs/ja-JP/INVENTORY.md',
|
|
'docs/ko-KR/INVENTORY.md',
|
|
'docs/zh-CN/INVENTORY.md',
|
|
'docs/pt-BR/INVENTORY.md',
|
|
],
|
|
// uncoveredFiles(...) scans 'docs' as a generic coverage-scan root
|
|
// (commit-files-pathspec.test.cjs:1618) — cannot be resolved to specific
|
|
// files without re-deriving the scan's own file-discovery logic.
|
|
'tests/commit-files-pathspec.test.cjs': ['*'],
|
|
'tests/compact-content-4139.test.cjs': ['docs/CONFIGURATION.md'],
|
|
'tests/config-field-docs.test.cjs': ['docs/CONFIGURATION.md'],
|
|
'tests/config.test.cjs': ['docs/CONFIGURATION.md'],
|
|
'tests/context-index-sync.test.cjs': ['docs/CONTEXT-INDEX.json'],
|
|
'tests/context-predicates-query.test.cjs': ['docs/contributor-standards.md'],
|
|
// SCAN_DIRS includes 'docs' and recursively walks every .md file under it
|
|
// (context7-tool-name-parity.test.cjs:31-38) — a generic tree walk, not a
|
|
// fixed file set.
|
|
'tests/context7-tool-name-parity.test.cjs': ['*'],
|
|
'tests/contributor-standards.test.cjs': ['docs/contributor-standards.md'],
|
|
'tests/cursor-reviewer.test.cjs': [
|
|
'docs/COMMANDS.md',
|
|
'docs/FEATURES.md',
|
|
'docs/ja-JP/COMMANDS.md',
|
|
'docs/ja-JP/FEATURES.md',
|
|
'docs/ko-KR/COMMANDS.md',
|
|
'docs/ko-KR/FEATURES.md',
|
|
],
|
|
'tests/discuss-all-flag.test.cjs': ['docs/COMMANDS.md'],
|
|
'tests/discuss-mode.test.cjs': ['docs/workflow-discuss-mode.md'],
|
|
// Walks docs/*.md and every docs/<locale>/*.md dir dynamically
|
|
// (docs-parity-live-registry.test.cjs:42, 428) — deliberately generic.
|
|
'tests/docs-parity-live-registry.test.cjs': ['*'],
|
|
// #3839: pins every hook-table Event cell in the five locales' ARCHITECTURE
|
|
// and INVENTORY files against src/runtime-hooks-surface.cts registrations.
|
|
'tests/docs-hooks-table-parity.test.cjs': [
|
|
'docs/ARCHITECTURE.md',
|
|
'docs/INVENTORY.md',
|
|
'docs/ja-JP/ARCHITECTURE.md',
|
|
'docs/ja-JP/INVENTORY.md',
|
|
'docs/zh-CN/ARCHITECTURE.md',
|
|
'docs/zh-CN/INVENTORY.md',
|
|
'docs/ko-KR/ARCHITECTURE.md',
|
|
'docs/ko-KR/INVENTORY.md',
|
|
'docs/pt-BR/ARCHITECTURE.md',
|
|
'docs/pt-BR/INVENTORY.md',
|
|
],
|
|
'tests/docs-state-md-locale-parity.test.cjs': [
|
|
'docs/reference/state-md.md',
|
|
'docs/ja-JP/reference/state-md.md',
|
|
'docs/zh-CN/reference/state-md.md',
|
|
'docs/ko-KR/reference/state-md.md',
|
|
'docs/pt-BR/reference/state-md.md',
|
|
],
|
|
'tests/drift-detection.test.cjs': ['docs/CONFIGURATION.md', 'docs/AGENTS.md'],
|
|
'tests/edge-probe-docs-fixtures.test.cjs': ['docs/adr/550-spec-phase-probe-contract.md'],
|
|
'tests/edit-phase.test.cjs': [
|
|
'docs/INVENTORY.md',
|
|
'docs/INVENTORY-MANIFEST.json',
|
|
'docs/COMMANDS.md',
|
|
],
|
|
'tests/effort-surface-axis.test.cjs': ['docs/reference/host-integration-capability-matrix.md'],
|
|
'tests/execute-phase-active-flags.test.cjs': [
|
|
'docs/reference/host-integration-capability-matrix.md',
|
|
],
|
|
'tests/execute-phase-wave.test.cjs': ['docs/COMMANDS.md'],
|
|
// #3913 (ADR-3889 terminal phase): reads the generated docs/reference/exit-codes.md
|
|
// (content invariants, F1/F3) and docs/README.md (F4, the index link).
|
|
'tests/exit-code-registry.test.cjs': ['docs/reference/exit-codes.md', 'docs/README.md'],
|
|
'tests/external-job-waiting.test.cjs': ['docs/reference/planning-artifacts.md'],
|
|
// Rows 8/9 (negative controls) read real docs/registries/eos.json and
|
|
// docs/adr/0001-dispatch-policy-module.md and assert on their EXACT
|
|
// committed content (an entry's name field, ADR-0001's H1 title) as a
|
|
// sanity check before mutating an overlay fixture — a content edit to
|
|
// either file changes the string this test asserts on.
|
|
'tests/fragment-single-edit-propagation.install.test.cjs': [
|
|
'docs/registries/eos.json',
|
|
'docs/adr/0001-dispatch-policy-module.md',
|
|
],
|
|
// Seeds a temp fixture copy of these five files (never mutates the real
|
|
// tree) to exercise scripts/gen-state-md-docs.cjs's marked-region splicing
|
|
// against them — #3873 (ADR-3473 §8.8), rows 10-22/27. Read for fixture
|
|
// seeding, so a content edit to any of them (e.g. renaming a landmark
|
|
// heading/string a hostile-input test targets) can change this test's
|
|
// fixture assumptions.
|
|
// #4728: pins the retirement of Gemini CLI prose from every localized
|
|
// how-to/ARCHITECTURE/USER-GUIDE/CONFIGURATION/context-monitor mirror, plus
|
|
// the PRESERVE (Antigravity) and MODEL-AXIS (Gemini 2.5 Pro) negative-space
|
|
// checks in the same locales.
|
|
'tests/gemini-runtime-removed.test.cjs': [
|
|
'docs/ja-JP/how-to/install-on-your-runtime.md',
|
|
'docs/ko-KR/how-to/install-on-your-runtime.md',
|
|
'docs/pt-BR/how-to/install-on-your-runtime.md',
|
|
'docs/zh-CN/how-to/install-on-your-runtime.md',
|
|
'docs/ja-JP/ARCHITECTURE.md',
|
|
'docs/ko-KR/ARCHITECTURE.md',
|
|
'docs/pt-BR/ARCHITECTURE.md',
|
|
'docs/zh-CN/ARCHITECTURE.md',
|
|
'docs/ja-JP/USER-GUIDE.md',
|
|
'docs/ko-KR/USER-GUIDE.md',
|
|
'docs/pt-BR/USER-GUIDE.md',
|
|
'docs/zh-CN/USER-GUIDE.md',
|
|
'docs/ja-JP/CONFIGURATION.md',
|
|
'docs/ko-KR/CONFIGURATION.md',
|
|
'docs/pt-BR/CONFIGURATION.md',
|
|
'docs/zh-CN/CONFIGURATION.md',
|
|
'docs/ja-JP/context-monitor.md',
|
|
'docs/ko-KR/context-monitor.md',
|
|
'docs/pt-BR/context-monitor.md',
|
|
'docs/zh-CN/context-monitor.md',
|
|
],
|
|
'tests/gen-state-md-docs.test.cjs': [
|
|
'docs/reference/state-md.md',
|
|
'docs/ja-JP/reference/state-md.md',
|
|
'docs/zh-CN/reference/state-md.md',
|
|
'docs/ko-KR/reference/state-md.md',
|
|
'docs/pt-BR/reference/state-md.md',
|
|
],
|
|
'tests/gsd-write-guard.test.cjs': ['docs/USER-GUIDE.md'],
|
|
'tests/host-integration-descriptors.test.cjs': [
|
|
'docs/reference/host-integration-capability-matrix.md',
|
|
],
|
|
'tests/install.test.cjs': ['docs/AGENTS.md', 'docs/INVENTORY.md', 'docs/INVENTORY-MANIFEST.json'],
|
|
// SOURCE_DIRS includes 'docs' and walks it recursively for every .md file
|
|
// (intel.test.cjs:1223-1228) — a generic tree walk.
|
|
'tests/intel.test.cjs': ['*'],
|
|
'tests/inventory-headings-countfree.test.cjs': ['docs/INVENTORY.md'],
|
|
'tests/inventory-manifest-sync.test.cjs': ['docs/INVENTORY.md', 'docs/INVENTORY-MANIFEST.json'],
|
|
'tests/kilo-upgrades.test.cjs': ['docs/how-to/connect-gsd-mcp-server.md'],
|
|
'tests/live-config-guard.test.cjs': ['docs/TESTING-SUITES.md'],
|
|
// #3726: pins the `milestone complete` synopsis (English + four localized
|
|
// mirrors), the `--confirm` flag row and the guard-override instructions —
|
|
// `type: Fixed` exempts that PR from the docs-required lint, so this is the
|
|
// only gate on that prose.
|
|
'tests/milestone.test.cjs': [
|
|
'docs/CLI-TOOLS.md',
|
|
'docs/COMMANDS.md',
|
|
'docs/ja-JP/CLI-TOOLS.md',
|
|
'docs/ko-KR/CLI-TOOLS.md',
|
|
'docs/pt-BR/CLI-TOOLS.md',
|
|
'docs/zh-CN/CLI-TOOLS.md',
|
|
],
|
|
'tests/model-catalog-runtime-defaults.test.cjs': ['docs/CONFIGURATION.md'],
|
|
// Scans every git-tracked file in the whole repo via `git ls-files`
|
|
// (no-pending-3212-markers.test.cjs:37-46), which includes all of docs/ —
|
|
// cannot be resolved to a fixed docs/ path set.
|
|
'tests/no-pending-3212-markers.test.cjs': ['*'],
|
|
'tests/phase6-capability-docs.test.cjs': ['docs/how-to/develop-a-capability.md', 'docs/README.md'],
|
|
'tests/phase6-review-capabilities.test.cjs': [
|
|
'docs/reference/review-verification-capabilities.md',
|
|
'docs/how-to/develop-a-capability.md',
|
|
'docs/README.md',
|
|
],
|
|
'tests/plan-checker-coupling.test.cjs': ['docs/AGENTS.md'],
|
|
'tests/plan-phase-drift-guard.test.cjs': [
|
|
'docs/CONFIGURATION.md',
|
|
'docs/COMMANDS.md',
|
|
'docs/USER-GUIDE.md',
|
|
'docs/ARCHITECTURE.md',
|
|
'docs/INVENTORY.md',
|
|
'docs/INVENTORY-MANIFEST.json',
|
|
],
|
|
'tests/plan-phase-stall-detection.test.cjs': ['docs/CONFIGURATION.md'],
|
|
'tests/plan-review-convergence.test.cjs': [
|
|
'docs/CONFIGURATION.md',
|
|
'docs/USER-GUIDE.md',
|
|
'docs/ARCHITECTURE.md',
|
|
],
|
|
'tests/planner-estimate-emission.test.cjs': ['docs/reference/plan-md.md', 'docs/CONFIGURATION.md'],
|
|
'tests/precondition-element.test.cjs': ['docs/reference/plan-md.md'],
|
|
'tests/product-name-purity.test.cjs': [
|
|
'docs/README.md',
|
|
'docs/zh-CN/README.md',
|
|
'docs/ko-KR/README.md',
|
|
'docs/ja-JP/README.md',
|
|
'docs/pt-BR/README.md',
|
|
],
|
|
'tests/progress-forensic.test.cjs': ['docs/COMMANDS.md'],
|
|
'tests/repo-layout.test.cjs': ['docs/contributing/bootstrap.md'],
|
|
// Reads REQ-LANG-04 and runs every form it offers an author through the
|
|
// matcher that enforces it, so a reword of the requirement alone is exactly
|
|
// the change this guard must run on (#2529). Both paths are named because
|
|
// #3840 made docs/FEATURES.md a generated projection: the requirement's
|
|
// source is the fragment, and an edit there that is not regenerated would
|
|
// otherwise reach this guard through neither path.
|
|
'tests/response-language-coverage.test.cjs': [
|
|
'docs/FEATURES.md',
|
|
'docs/features/response-language-config.md',
|
|
],
|
|
'tests/reversibility-tagging.test.cjs': ['docs/reference/plan-md.md'],
|
|
'tests/reviewer-docs-parity.test.cjs': [
|
|
'docs/COMMANDS.md',
|
|
'docs/ja-JP/COMMANDS.md',
|
|
'docs/ko-KR/COMMANDS.md',
|
|
'docs/pt-BR/COMMANDS.md',
|
|
'docs/zh-CN/COMMANDS.md',
|
|
'docs/FEATURES.md',
|
|
'docs/ja-JP/FEATURES.md',
|
|
'docs/ko-KR/FEATURES.md',
|
|
'docs/pt-BR/FEATURES.md',
|
|
'docs/zh-CN/FEATURES.md',
|
|
],
|
|
'tests/runtime-converters.test.cjs': ['docs/CONFIGURATION.md'],
|
|
'tests/secure-phase.test.cjs': ['docs/CONFIGURATION.md'],
|
|
'tests/security-dead-exports.regression.test.cjs': ['docs/FEATURES.md'],
|
|
'tests/security.test.cjs': ['docs/INVENTORY-MANIFEST.json'],
|
|
// Walks docs/ recursively (todos-done-rename-guard.test.cjs:19-22
|
|
// SCAN_DIRS) looking for stale references — a generic tree walk.
|
|
'tests/todos-done-rename-guard.test.cjs': ['*'],
|
|
'tests/tracer-bullet.test.cjs': [
|
|
'docs/COMMANDS.md',
|
|
'docs/reference/plan-md.md',
|
|
'docs/how-to/plan-a-phase.md',
|
|
'docs/AGENTS.md',
|
|
],
|
|
'tests/ui-interaction-capture.test.cjs': ['docs/CONFIGURATION.md'],
|
|
'tests/ui-spec-inventory-provenance.test.cjs': [
|
|
'docs/FEATURES.md',
|
|
'docs/how-to/design-a-ui-phase.md',
|
|
'docs/ja-JP/FEATURES.md',
|
|
'docs/ja-JP/how-to/design-a-ui-phase.md',
|
|
'docs/zh-CN/FEATURES.md',
|
|
'docs/zh-CN/how-to/design-a-ui-phase.md',
|
|
'docs/ko-KR/FEATURES.md',
|
|
'docs/ko-KR/how-to/design-a-ui-phase.md',
|
|
'docs/pt-BR/how-to/design-a-ui-phase.md',
|
|
],
|
|
'tests/verifier-behavior-unverified.test.cjs': ['docs/reference/planning-artifacts.md'],
|
|
'tests/verifier-coincidental-reliance.test.cjs': ['docs/AGENTS.md'],
|
|
'tests/verify.test.cjs': ['docs/reference/plan-md.md'],
|
|
'tests/workflow-fragments.test.cjs': ['docs/reference/workflow-fragments.md'],
|
|
};
|
|
|
|
/**
|
|
* Flat file-list view of DOCS_GUARD_TESTS, kept for consumers (the
|
|
* registration lint and its parity test) that only need "which test files
|
|
* are registered", not their per-file docs path patterns.
|
|
*/
|
|
const DOCS_GUARD_TEST_FILES = Object.keys(DOCS_GUARD_TESTS);
|
|
|
|
assertNoSuiteCollision(DOCS_GUARD_TEST_FILES);
|
|
|
|
module.exports = {
|
|
DOCS_GUARD_TESTS,
|
|
DOCS_GUARD_TEST_FILES,
|
|
RUN_TESTS_SUITES,
|
|
assertNoSuiteCollision,
|
|
normalizeForSuiteCheck,
|
|
};
|