fix(881): the replacement clause asserted an absolute I had not measured

The previous commit replaced "the order is load-bearing" with "and that is the
whole of what the order buys". What was measured is narrower: with the relevance
gate moved first, the three gates are each still witnessed refusing alone. That
does not establish the order buys nothing else - the reset placement is a second
candidate, unmeasured either way - so the absolute is gone from both sites and
what stays is the cost reason, which is readable from the control flow.

refs #881

Decisions-Edit: yes
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QqCpYFsKgnAnx6jVwrKiV

scripts/tests/mutation_harness_lib.py

@@ -430,13 +430,13 @@ def verify_claim(sandbox: Path, claim: Claim) -> Verdict:
     disarmed on its own and seen to matter; a single clause covering all three would be a guard
     nothing can witness failing.
 
-    THE RELEVANCE GATE RUNS LAST BECAUSE IT IS THE EXPENSIVE ONE, and that is the whole of what the
-    order buys: it is the only one of the three that costs a second full run of the proof — under the
-    reach mutation, with a sandbox reset in between — so an entry the status or the vacuity gate has
-    already refused never pays for it. What keeps the three worth three is that each carries its own
-    disarm proof, not the sequence they are written in. The sandbox is reset between the two runs
-    because the first proof run can dirty the tree, and a second result that is a function of the
-    first's is what `reset_sandbox` exists to prevent.
+    THE RELEVANCE GATE RUNS LAST BECAUSE IT IS THE EXPENSIVE ONE: it is the only one of the three
+    that costs a second full run of the proof — under the reach mutation, with a sandbox reset in
+    between — so an entry the status or the vacuity gate has already refused never pays for it. What
+    keeps the three worth three is that each carries its own disarm proof, rather than the position
+    it sits in. The sandbox is reset between the two runs because the first proof run can dirty the
+    tree, and a second result that is a function of the first's is what `reset_sandbox` exists to
+    prevent.
     """
     if claim.outcome == Claim.RED:
         return verify_mutation(