[FIX] fool harness: record mlx version correctly + self-hash; trial-03 pre-run addendum

Two instrument defects, both of the class the harness was built to prevent —
a probe that could not look reporting a value that reads like a result:

- environment() read mlx.__version__, which does not exist (only
  mlx.core.__version__). Every run record would have said mlx_version
  "unknown" for an installed, versioned package, losing the one field that
  makes trial 03 comparable to trial 02. It is MLX 0.31.2, identical.
- git_revision() returns null whenever the harness runs outside its repo,
  which is always — it must run on the machine holding the model. The prompt
  and input were hashed; the instrument itself was not. Now self-hashed.

The pre-registration addendum is committed BEFORE the run produced output, so
the ordering is checkable rather than asserted. It records: the 'unruled'
premise expiring at REVIEWED-86 (12:13, 32 min after the pre-registration was
written) and why the ordering favours the ground truth; the contamination that
CANNOT be removed, since the amended doctrine is in the executor's auto-loaded
context and I am therefore not a blind grader; the (a)/anti-echo collision
resolved against my own convenience before output existed; and the seed.

Ground truth (a)-(e) is unrevised and will not be revised.

claude/governance/fool/trial-03-PREREGISTRATION.md

@@ -71,6 +71,51 @@ And per the standing caveat: the grade below will be assigned by the executor, w
 errors are among those being graded. The findings will be individually checkable; the
 grade will not be independent.
 
+## Addendum, written DURING the run and BEFORE any output was seen
+
+*(Run launched 2026-08-02 ~13:0x; model still loading; the output file was empty when
+each item below was written. Recorded here rather than in the write-up precisely because
+its whole value is that it precedes the result.)*
+
+**1. The "unruled" premise above expired 32 minutes after it was written.** It was true at
+11:41. At **12:13** the steward placed **REVIEWED-86**, design-gating this doctrine with two
+required conditions. The ordering is the part that matters and it is favourable: ground truth
+(a)–(e) was fixed **before** the jurist ruled, so the jurist's conditions are an *independent*
+check on the ground-truth list rather than a source of it. (a)–(e) will **not** be revised.
+Grading order is therefore fixed: **grade against (a)–(e) first and write it down, then read
+REVIEWED-86 and compare.**
+
+**Contamination that cannot be removed, stated plainly:** the *amended* doctrine text now sits
+in `~/CLAUDE.md`, which is loaded into the executor's context automatically. I have therefore
+already seen the jurist's conditions in their applied form. I am not a blind grader and must
+not be described as one. What survives clean is the timestamp on (a)–(e), which is checkable
+in git.
+
+**2. Ground-truth item (a) collides with the anti-echo clause, and the collision must be
+resolved now rather than conveniently.** Part VII §1 of the document already states *"The
+doctrine's own second consequence is the sharpest argument against the arrangement that
+produced it."* So the first half of (a) is **author-named** and, per the prompt's own
+instruction, is **not a finding**. Ruling, fixed before output:
+
+- Reporting that consequence 2 indicts the jurist–executor pair → **ECHO**, not a hit.
+- Reporting that the package **never resolves what should change** as a result — that it
+  proposes the doctrine anyway and leaves its own configuration in place — → **HIT on (a)**.
+- This makes (a) *harder* to score than the other four, not easier. Recorded because the
+  temptation afterwards will run the other way.
+
+**3. Seed declared before the run: `20260802`.** The pre-registration left the seed
+unspecified, which would have meant `None` — non-deterministic, and a reproduction of the exact
+irreproducibility this harness exists to end. Fixing a seed changes nothing pre-registered
+(input, prompt, absence of steer, thinking ON).
+
+**4. Two harness edits made before the run, both environment-recording only, neither touching
+the trial design.** `mlx.__version__` does not exist — only `mlx.core.__version__` — so the
+probe would have recorded `"unknown"` for an installed, versioned package, losing the single
+field that makes trial 03 comparable to trial 02. It is **MLX 0.31.2, identical to trial 02**.
+Second: the harness now hashes *itself* into the run record, because `git_revision()` returns
+null whenever the harness runs outside its repository — which is always, since it must run on
+the machine holding the model.
+
 ## Result
 
 *(To be filled after the run. Empty until then — deliberately.)*