docs(tests): tracked comments name the measurement, not the coordination

`origin` is a public mirror. Comments in tracked test files named the internal
review mechanism by its role rather than the measurement they came from; the
same class as the frozen file's overclaim fixed in 83d82f1. Replaced with what
they actually are: a re-measurement on a named commit, with the date.

The one remaining occurrence is the assertion that FORBIDS those phrases in
tests/fixtures/end-state-frozen.json - a guard has to spell out what it guards.

Suite 1161 (1159/0/2). Comment-only change.

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

tests/lib/criteria-runner.test.mjs

@@ -367,7 +367,7 @@ test('CLI: --evidence and --json together exit 2 — one output shape at a time'
 // D-03's runner read bullet lines only. The repo's own example plan writes its
 // `## Verification` as a fenced bash block, so it parsed to ZERO criteria, the
 // runner exited 1, and Phase 7 forbade `result: completed` — a correct plan
-// felled every single-session run. Measured 2026-09-18 (PM checkpoint on
+// felled every single-session run. Measured 2026-09-18 (re-measured on
 // 6cafb4c): 0 of the repo's plan artifacts exited 0.
 
 const SHELL_BLOCK_PLAN = [

tests/lib/doc-consistency.test.mjs

@@ -1857,7 +1857,7 @@ test('D-03: trekexecute Phase 7 runs the plan Verification on the single-session
 // Success Criterion's verification command "exists and passes" — with Read/Glob/Grep. The
 // command now runs the commands and hands over the result; the reviewer stays read-only.
 // Fix the SOURCE.
-// PM checkpoint 2026-09-18, MINOR: /trekreview passed --cwd and Phase 7 did not,
+// Re-measured 2026-09-18, minor: /trekreview passed --cwd and Phase 7 did not,
 // so the same criterion could resolve two ways in the two phases. It is no longer
 // cosmetic - --cwd is where every allowlisted command is executed and where a
 // `bash tests/<script>.sh` criterion resolves, so an unset one silently moves
@@ -1886,7 +1886,7 @@ test('D-04: the conformance reviewer judges a supplied result, and never runs a
   assert.match(a, /Success-criteria check results/, 'the reviewer must document the supplied evidence as an input');
 });
 
-// Follow-up to D-04 (PM checkpoint 2026-09-18): the runner now reports a criterion
+// Follow-up to D-04 (re-measured 2026-09-18): the runner now reports a criterion
 // whose sentence named a flag or a path as NOT RUN with reason `not-a-command`,
 // instead of running it and reporting exit 2 / exit 126. The rubric must not turn
 // that absent measurement into a finding of its own - it judges delivered code.
@@ -1918,7 +1918,7 @@ test('D-04: trekreview runs the success-criteria commands and hands the reviewer
   );
 });
 
-// MAJOR from the 2026-09-18 PM checkpoint: the plan's `## Verification` section
+// Re-measured 2026-09-18: the plan's `## Verification` section
 // is the one artifact BOTH /trekplan (writer) and lib/verification/criteria-runner.mjs
 // (reader) touch, and nothing pinned them to the same format. Measured: nine
 // ordinary shapes of that section parsed to zero criteria, which fells the

tests/scripts/end-state-gate.test.mjs

@@ -34,7 +34,7 @@ const ROOT = resolve(dirname(fileURLToPath(import.meta.url)), '..', '..');
 const GATE = join(ROOT, 'scripts', 'end-state-gate.mjs');
 
 // --- the frozen denominator ------------------------------------------------
-// Denominator frozen 2026-09-17 by the end-state work order, the day the end-state
+// Denominator frozen 2026-09-17, the day the end-state
 // direction was chosen. An entry may CLOSE; it may never be removed or have its check
 // changed, and the gate's agent/decision/freeze configuration may not move. To change
 // anything below you must change this test — say in the commit message who decided it.
@@ -771,7 +771,7 @@ test('the detail line carries one note per probe kind PRESENT, and none for kind
 
 // --- a probe that RUNS a test, and the M6 mutant ---------------------------
 //
-// Measured 2026-09-18 (PM checkpoint on 6cafb4c): a two-line file
+// Measured 2026-09-18 (re-measured on 6cafb4c): a two-line file
 //   export function runPlanVerification() { return { ok: true }; }
 //   export function formatCriteriaEvidence() { return ''; }
 // dropped into an otherwise UNFIXED tree closed both D-03 and D-04, and the
@@ -849,7 +849,7 @@ test('the gate states out loud that the wiring is pinned by text, not proven', (
 
 // --- M7: a probe must bind the test's CONTENT, not its name ---------------
 //
-// Measured 2026-09-18 (PM checkpoint on e1e7bdf): the cosmetic close came back
+// Measured 2026-09-18 (re-measured on e1e7bdf): the cosmetic close came back
 // one level up. The probe reads the test file from the SAME tree it measures,
 // so a four-line file holding two EMPTY tests with the two named names —
 //   test('runPlanVerification: a plan whose success criterion FAILS fells the run', () => {});
@@ -937,10 +937,10 @@ test('the stub mutant leaves the measured tree untouched', () => {
 });
 
 test('the frozen file claims no authority it does not have', () => {
-  // MINOR from the same checkpoint: the tracked frozen file said the second
-  // amendment was "operator-authorised by work order". No operator authorised
-  // it; it followed from a maintenance decision. A file whose whole job is to
-  // be an explicit decision trail may not overclaim in either direction.
+  // Measured the same day: the tracked frozen file claimed its second
+  // amendment was operator-authorised. No operator authorised it; it followed
+  // from a maintenance decision. A file whose whole job is to be an explicit
+  // decision trail may not overclaim in either direction.
   const why = loadFrozen(ROOT).why;
   assert.ok(why.length > 0, 'the frozen manifest must say WHY it changed');
   assert.ok(