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

Round 9 (0f400d3..a10018f, WARN: 0 BLOCKER, 12 MAJOR): seven findings and
three brief notes, by operator choice. Each finding began with a test that
failed on a10018f on its assertion; suite 2230 (2228/0/2).

- A check refused for its comment (a quote, $, backtick or backslash) keeps
  its command and its reason, and every reader refuses it out loud: a nested
  ## Verification bullet stays a criterion (PLAN_VERIFICATION_NOT_RUNNABLE)
  and a brief SC warns (BRIEF_SC_NOT_RUNNABLE). It was folded into a
  sub-point or read as prose, a regression from a10018f. Readers that took a
  command as runnable (the end-to-end lists) skip a refused one.
- The verdict gate reads the last fenced block's info string and body from
  one reading, and exits 2 unless the info string is exactly json: a last
  block opened as ```json {x} held a BLOCKER the gate passed with exit 0
  (also in 6.3.0). A last block never closed is exit 2 too.
- One fence reader (findings-schema fencedBlocks) for the gate and every
  trailing-json reader: a fence closes only on a run at least as long as its
  opener, as in Markdown, so a four-backtick example of a json block is one
  block; CRLF and an indented fence read alike in the gate and the readers.
- Files: a description runs on past a comma and onto the next line until a
  new entry starts (a list item on a new line, or a backticked path), and a
  plain path followed by a colon starts its description. Measured over all
  939 Files: fields in the .md files under the marketplace and the test repo
  (560 of them in the 48 plan.md files outside worktrees): 0 read
  differently, tests-only changed in 0.
- The test lock compares --cmd by its words, so other blanks between the
  same words are the step's command.
- release-check decides "two files" on real paths: one review.md reached
  through a symlinked --repo is one file.
- Brief notes: red proof's stopped control run has its own test (green at
  once, red with the branch deleted); the two tests that assumed jest is not
  installed run with a PATH that finds only git (red on a10018f with a jest
  on PATH, green now); the Files: reader's doc states the measured counts
  (520 fields in 48 plan files at rounds 7-8, not "182 plans"; 560 now).

Not in this round (operator 2026-10-11): a144e9ce, 1dc2e785, dc3a467e,
2fa88853, 26873fa5.

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

tests/hooks/test-lock-green.test.mjs

@@ -17,6 +17,7 @@ import { writeFileSync, mkdirSync, readFileSync } from 'node:fs';
 import { join } from 'node:path';
 import { runHook } from '../helpers/hook-helper.mjs';
 import { ROOT, makeRepo, parseJsonOut } from './guard-helpers.mjs';
+import { pathWith } from '../helpers/bin-path.mjs';
 
 const CLI = join(ROOT, 'lib', 'util', 'test-lock.mjs');
 const STOP = join(ROOT, 'hooks', 'scripts', 'stop-test-lock.mjs');
@@ -24,8 +25,8 @@ const PRE_WRITE = join(ROOT, 'hooks', 'scripts', 'pre-write-executor.mjs');
 const SESS = `sess-green-${process.pid}-${Date.now()}`;
 const CMD = 'node --test tests/step.test.mjs';
 
-function cli(repo, args) {
-  const r = spawnSync(process.execPath, [CLI, ...args], { cwd: repo, encoding: 'utf8', env: { ...process.env, CLAUDE_CODE_SESSION_ID: SESS } });
+function cli(repo, args, env = {}) {
+  const r = spawnSync(process.execPath, [CLI, ...args], { cwd: repo, encoding: 'utf8', env: { ...process.env, CLAUDE_CODE_SESSION_ID: SESS, ...env } });
   return { code: r.status, stdout: r.stdout, stderr: r.stderr };
 }
 
@@ -123,9 +124,28 @@ test('green (release review of 6.3.0, round 8): a test program that is not insta
   const repo = makeRepo('main');
   mkdirSync(join(repo, 'tests'), { recursive: true });
   writeFileSync(join(repo, 'tests', 'step.test.mjs'), 'x\n');
-  // `jest` is on the allowlist and not installed where this suite runs.
+  // `jest` is on the allowlist; the PATH finds only git, so it cannot start on
+  // any machine, one with jest installed too (round 9).
   assert.equal(cli(repo, ['lock', '--files', 'tests/step.test.mjs', '--step', '3', '--cmd', 'jest tests/step.test.mjs']).code, 0);
-  const g = cli(repo, ['green', '--cmd', 'jest tests/step.test.mjs']);
-  assert.equal(g.code, 2, g.stderr);
-  assert.match(g.stderr, /could not start/, g.stderr);
+  const bin = pathWith(['git']);
+  try {
+    const g = cli(repo, ['green', '--cmd', 'jest tests/step.test.mjs'], { PATH: bin.path });
+    assert.equal(g.code, 2, g.stderr);
+    assert.match(g.stderr, /could not start/, g.stderr);
+  } finally { bin.cleanup(); }
+});
+
+test('green (release review of 6.3.0, round 9 / e36a533e): the same words with other blanks between them are the step\'s command', () => {
+  // runCommand splits a command on any blank, so a double space or a tab from
+  // the plan span runs the very same words; the --cmd check compared strings.
+  for (const greenCmd of ['node  --test tests/step.test.mjs', 'node\t--test tests/step.test.mjs', ` ${CMD}\t`]) {
+    const repo = lockedRepo('assert.equal(1, 1);');
+    const g = cli(repo, ['green', '--cmd', greenCmd]);
+    assert.equal(g.code, 0, `green ${JSON.stringify(greenCmd)}: ${g.stderr}`);
+  }
+  // The control: other words are still refused.
+  const repo = lockedRepo('assert.equal(1, 1);');
+  const g = cli(repo, ['green', '--cmd', 'node --test tests/other.test.mjs']);
+  assert.equal(g.code, 2, g.stderr);
+  assert.match(g.stderr, /not the step's test command/, g.stderr);
 });