fix: round 7 of the release review of 6.3.0, for 6.3.1

Round 7 (516dffa..45aa9e1, WARN: 12 MAJOR, 0 BLOCKER) and the fence defect
found while writing its review.md. Each fix began with a test that failed on
0f400d3 (v6.3.0); suite 2208 (2206/0/2), 14 tests more.

- Tests-only (operator 2026-10-11): the plan's Files: alone decides, and the
  text says so (red-proof, trekexecute Sub-step B, step-implementer,
  HANDOVER-CONTRACTS). red-proof no longer reads the step's diff, so a change
  already in the tree when the step began no longer counts against it, and a
  plan placed outside .claude/ reads the same. The round-6 test that had the
  diff overrule the plan is rewritten to the new rule.
- The Files: reader keeps a plain file beside a backticked path
  (", Dockerfile", "the CLI entry src/cli.mjs", "and Makefile"). Measured on
  the 520 Files: fields in 182 plans: no field reads differently.
- Red proof reports a command its timeout killed as killed after the timeout,
  not "could not start"; the release check tells a timeout from output past
  its buffer and from another signal. One reading of a stop
  (criteria-runner stoppedBy) for red proof, the criteria runner and the
  release check.
- A trailing `# comment` is dropped in a backticked check too, and in a
  command passed as written, so the words screened are the words run.
- The release check reads a relative --review in --repo.
- The 15-minute timeout is defined once (criteria-runner.mjs).
- The findings check reads each cited file once per validation.
- One isMain helper (lib/util/is-main.mjs) for every CLI: the 31 copies of
  the realpath guard and the 20 modules still on the file:// guard, which
  exited 0 having done nothing under a symlink or a path with a space.
- The Bash guard writes its no-one-to-ask refusal once, on a direct condition.
- The findings check ends a ```json block only at a fence on its own line, so
  three backticks inside a JSON string no longer end it (also in 6.2.0).
- Brief-conformance notes: a test for test-lock green on exit 127 (it
  passed at once; it fails when 127 is read as could-not-run); the prose now
  names the git revision `@~1` as the one leading-@ exception.

Not changed: the example plan's steps 1-2 keep their tests-only warning
(operator decision 2026-10-09; the r5 test records it). Brief note 4 (a
Regression: whose runner is not installed goes to the fix rounds) is a
routing question for the operator.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

agents/brief-reviewer.md

@@ -62,8 +62,9 @@ is one test-runner invocation with no pipe, redirect or `&&`: `npm test`,
 `python -m pytest`, `uv run pytest`, `cargo test`, `go test`, `make test`,
 `bash tests/<script>.sh` (or `/bin/bash tests/<script>.sh`), or `git status|log|diff|show|ls-files`.
 It runs with no shell, as plain words: no quote, `$`, brace, leading `~` or
-`@`, no glob outside `node --test` (Node 21+), no `..` or absolute path, and
-only the runner's read-only options.
+`@` (a git revision such as `@~1` is the one exception), no glob outside
+`node --test` (Node 21+), no `..` or absolute path, and only the runner's
+read-only options.
 Anything else — the product's own binary (`node bin/x.mjs …`), `jq`, `grep`,
 `git grep`, a pipe — is reported NOT RUN. Never PROPOSE such a command as a
 criterion. When a criterion needs one, propose wrapping it in a script under

agents/step-implementer.md

@@ -43,8 +43,9 @@ and never touch a file the step does not list.
    already passes at the start point, so it proves nothing: rewrite the test
    until it fails for the reason the step exists, and run the check again.
    But when the answer carries `tests_only: true` (it prints that line),
-   every file in the step's `Files:` is a test: the behaviour already exists
-   at the start point, and no test can be red here. Do not rewrite the test and do not build; say so in
+   every file in the step's `Files:` is a test. The plan's
+   `Files:` alone decides this, not what you have changed: the behaviour
+   already exists at the start point, and no test can be red here. Do not rewrite the test and do not build; say so in
    the report and stop. The executor sends the step up to the plan.
    Exit 2 = it could not run (the Verify command is not one test-runner
    invocation, or a file is missing): on `plan_version` ≥ 1.8 do not build;