docs: the harness guard pins one file per harness file (GST-1084)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

docs/test-audit-2026-10.md

@@ -50,14 +50,14 @@ per-failure-class breakdown from `test:health`.
   full consumed-input fingerprint (all touchfiles, globals included) as
   `series_fingerprint`, plus `harness_version`, as provenance.
   (`caseSeriesIdentitiesV2` in `scripts/eval-trial-series.ts`.)
-- **Harness guard.** `scripts/harness-version.json` pins the blob of every
-  shared execution-harness file: `GLOBAL_TOUCHFILES` plus the session runners,
+- **Harness guard.** `scripts/harness-pins/<path>.json` pins the blob of every
+  shared execution-harness file (`scripts/harness-version.json` keeps the version and patterns): `GLOBAL_TOUCHFILES` plus the session runners,
   the PTY harness, the e2e gate and the LLM judge (36 files). A free test
   (`test/harness-version.test.ts`) fails when one changes without a decision.
   `bun run scripts/bump-harness-version.ts --bump "<reason>"` raises
   `HARNESS_VERSION` and starts a new series for every case;
   `--non-behavioral "<reason>"` records the new blobs as compatible with no
-  reset. Entries are one line per file so concurrent PRs that touch different
+  reset. Each pin is its own file so concurrent PRs that touch different
   files merge cleanly; on a conflict, take the higher version, then rerun.
 - **Weekly history (W4b).** Weeks for quarantine expiry and drift are
   `evals-periodic.yml` runs on `main`: scheduled runs and main dispatches.