[FIX] REVIEWED-134: suspend automatic grading, with a replacement terminus

The steward's ruling of 2026-09-04 amends REVIEWED-123 condition 2. Applied as
data, in the deferral record's own vocabulary: no code changed, and
governance-drift-check.py:513 stays excluded from repair and unexamined, as the
ruling's Notes require. The counter still counts and still fires at 84; what a
firing INSTRUCTS is now recording, not grading.

Condition 3 replaces the terminus that suspension removed. Grading at 84 was the
ladder hold's only terminal bound, so the suspension carries its own: the joint
PENDING-178/-179 ruling, or 2026-10-15, whichever falls first. That bound is given
a trigger rather than a memory — a dated DEFERRED-DECISION block whose discriminator
states, in its own text, that firing returns the falsifier for a steward ruling and
does not resume grading (condition 4). PENDING-168 is the reason it is not left to care.

N-now at suspension, measured live by the trial's own method: 65 = 41 real + 24
mumble (36.9%), distance 19. Unchanged from 2026-09-03 in count and composition.

Left knowingly wrong, and recorded rather than fixed: the /wake-up trial line still
reads "Graded automatically at 84 transcripts". It is the trial's own intervention
text, frozen by its own terms and by REVIEWED-123 condition 1; rewording it would
confound the measurement the suspension exists to protect.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7

claude/governance/harvest-routing-JURIST-PACKAGE-2026-08-07.md

@@ -266,7 +266,16 @@ This proposal is a case where correlated misses are foreseeable rather than hypo
      since: 2026-08-07
      owner: executor
      trigger: transcripts 84
-     discriminator: recount the ladder's reach rate by the Part II census method (any-route tool-call access across all transcripts); >60% supports H1, below refutes it and reopens Q2's rationale per the jurist ruling Q6. File the result as a dated PENDING entry regardless of outcome. -->
+     discriminator: recount the ladder's reach rate by the Part II census method (any-route tool-call access across all transcripts); >60% supports H1, below refutes it and reopens Q2's rationale per the jurist ruling Q6. File the result as a dated PENDING entry regardless of outcome.
+     ⚠ SUPERSEDED IN PART 2026-09-04 by REVIEWED-134 (steward-originated, AUTHORIZED),
+     which amends REVIEWED-123 condition 2. The grading instruction above is SUSPENDED: on
+     reaching 84 this fires as before and the counter is untouched, but a crossing is
+     RECORDED, NOT GRADED — record the date of crossing and the real/mumble split on that
+     date, and do not recount the reach rate. A crossing is evidence for the ruling that
+     lifts the suspension; it is not a trigger and produces no grade. The suspension lapses
+     on the joint PENDING-178 / PENDING-179 ruling, or on 2026-10-15, whichever falls first,
+     and lapse returns the falsifier for a steward ruling rather than resuming grading.
+     Application record and the lapse trigger: claude/governance/REVIEWED-134-grading-suspension-2026-09-04.md -->
 
 *A date trigger was considered and rejected: sessions run at highly variable rates, so a date would be a proxy for the real condition — and the deferred-decision instrument's own comment records that proxies are what failed the last time. `transcripts 84` encodes the condition itself. The trigger type and the scan's reach into `claude/governance/` were both added this session to make this pre-registration checkable; the mechanism existed and did not look where it was most needed.*