fix: round 3 of the release review of 6.3.0

Round 3 (v6.2.0..96cb977, BLOCK: 1 BLOCKER, 8 MAJOR, 2 MINOR), each fixed
behind a test that failed first.

- Every allowlisted runner, not only git, takes plain words and a short list
  of options that only read: an option that writes a file or loads code
  (--test-reporter-destination, --outputFile, --junitxml, --basetemp,
  --import, --config, -p, -o, -exec, a reporter path) is on no list; after
  `npm test --` only paths follow; `make test` takes no VAR=value. A built-in
  node test reporter (tap, spec, dot, junit, lcov) stays allowed.
- /trekexecute: a restore the guard refuses (destructive git, in the mode
  that shows no prompts) or the operator declines is never recorded as
  reverted: simplify = "revert-refused" and the run stops before review; a
  refused step revert is reported with its paths.
- stepTestsOnly: a fixture document under tests/ is a test file, "e.g." is
  not a path, ./ is dropped; the plan-file sweep reads Files: with the same
  reader (fieldPaths); the validator hands its parsed fields over.
- plan-validator --steps-from asks for Verify: on a 1.8 plan too.
- skill frontmatter: a value starting with # is a hazard; a quote after an
  escaped backslash closes the value. Routing reads kind tags with hasOwn.
- release-check reads scope_sha_end as written (an all-digit sha keeps its
  leading zero), and Voyage's own artifacts under .claude/projects/ and
  .claude/voyage/ committed after the review do not count as unreviewed.

Suite 2170 (2168/0/2).

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

docs/release-runbook.md

@@ -81,8 +81,9 @@ do. `scripts/release-check.mjs` refuses a release whose section has no
    It checks, in order: the working tree is clean (otherwise the suite would
    not measure HEAD), `npm test` exits 0 at HEAD, the review verdict is not
    BLOCK, the review covers HEAD (its `scope_sha_end` is HEAD or an ancestor,
-   and the commits after it touch only the release bookkeeping above), and the
-   door type is set. 0 = ready, 1 = not ready (each failure listed), 2 = could
+   and the commits after it touch only the release bookkeeping above and
+   Voyage's own artifacts under `.claude/projects/` and `.claude/voyage/`, such
+   as the review itself and the approval log), and the door type is set. 0 = ready, 1 = not ready (each failure listed), 2 = could
    not run — never green.
 6. **The operator's yes, logged.** The operator reads the release section and
    says yes (an answer like "sounds good" is not a yes). The check prints the