board: revert my in-place edit of a MERGED EPIPHANIES entry (append-only)

Self-caught, prompted by the append-only learnings CodeRabbit surfaced on
#927: "the append-only rule applies to entries that have merged to main ...
After merge, preserve the historical entry unchanged except for permitted
Status and Confidence updates."

The EPIPHANIES entry carrying "5x WORSE" merged with #926. My previous commit
changed that number to 4.7x IN PLACE and UNMARKED -- which is history
rewriting, not correction, and is the one thing an append-only ledger exists
to prevent. Restored verbatim.

The correction still stands where it belongs: in the newly-prepended #926 arc
entry, which now also records that the merged line is deliberately frozen and
why. A newest-first ledger is read from the top, so a frozen historical line
is not a trap -- it is the audit trail.

COMET_TAIL_REPORT.md keeps the 4.7x fix; it is not a board file and carries no
append-only constraint.

Noting the shape without excusing it: I made an unmarked edit to a frozen
ledger inside a commit whose subject was propagation discipline. The rule I
was citing is the rule I broke.

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

Author: claude

.claude/board/EPIPHANIES.md

@@ -34,7 +34,7 @@ more than the pass.**
    already perfect.
 
 2. **L3 failed, and so did my proposed rescue** — the more useful half.
-   Fisher-z centroid axes are **4.7× WORSE** than uniform on the ring means
+   Fisher-z centroid axes are **5× WORSE** than uniform on the ring means
    (18.07 vs 3.84 Pa). I hypothesised the population was wrong (ranks against
    the 24 encoded values rather than the field) and measured that too: **19.00
    Pa, no rescue.** So the mechanism is not population size but *what the read

.claude/board/PR_ARC_INVENTORY.md

@@ -11,7 +11,7 @@
 - **Deferred / not claimed.** `domino.rs` does **not** implement the moderator model — its `W` is a *fixed* tridiagonal smoothing kernel (`domino.rs:113`), no learned weights, gates, hidden or cell state; the tile-GEMM **shape and substrate** exist, the model does not. θe / TCWV / precipitation / vertical velocity are **proxies**, not a closed entropy budget — that budget must be written before the CT-M1..M3 diabatic gate is used as a moderator. CT-F16 (score the dipole against **steering-level** motion, the one moderator this chain measured) NOT run. C-register calibration is single-timestep, not climatological — an operator call.
 - **Docs.** `COMET_TAIL_REPORT.md` §1/§4/§5.1–5.11/§6.1/§6.2/§8b/§9; EPIPHANIES ×3 new + 2 regraded in place; PR title/body corrected post-merge-review.
 
-**Correction (2026-08-12, same-day, caught by verifying this entry's own figures against the committed JSONs before landing it):** the Fisher-z ring-mean ratio is **4.7×**, not the *5×* first written here and in `COMET_TAIL_REPORT.md` §6.1 / `EPIPHANIES.md` — 18.07 / 3.84 = 4.71. A 6 % rounding in the FAVOURABLE direction, about to be frozen into an append-only record. Fixed in all four homes in this commit, which makes this PR mixed (hygiene + one correction) rather than hygiene-only; the correction is recorded here rather than in a separate entry because it corrects #926's own content. **Nine of ten figures verified exactly; this was the tenth** — and it is the arc's signature defect one more time, committed by the person who spent the arc naming it.
+**Correction (2026-08-12, same-day, caught by verifying this entry's own figures against the committed JSONs before landing it):** the Fisher-z ring-mean ratio is **4.7×**, not the *5×* first written here and in `COMET_TAIL_REPORT.md` §6.1 / `EPIPHANIES.md` — 18.07 / 3.84 = 4.71. A 6 % rounding in the FAVOURABLE direction, about to be frozen into an append-only record. Fixed in the two NEW board entries and in `COMET_TAIL_REPORT.md` §6.1 (not a board file). **`EPIPHANIES.md`'s merged entry is deliberately left reading *5×*** — it merged with #926, and the append-only rule freezes a merged entry except its Status/Confidence lines. **My first attempt edited that number in place, unmarked, which is history rewriting, not correction** — reverted the same commit. THIS entry is where the correction lives; a newest-first ledger is read from the top, so the frozen line is not a trap. That makes this PR mixed (hygiene + one correction) rather than hygiene-only, and the correction is recorded here rather than as a separate entry because it corrects #926's own content. **Nine of ten figures verified exactly; this was the tenth** — and it is the arc's signature defect one more time, committed by the person who spent the arc naming it.
 
 **Confidence (2026-08-12):** merged. The **structural** claim is `[G]` — wn-1 dominance and the R² lift replicated across three independent samples and survived every apparatus gate, and the f64 headlines are unaffected by the `var()`→MSE fix. The **carrier fit** is `[H]`: 2 storms, 1 timestep, 1 variable — structural fit to the 12-byte facet, saying nothing about forecast skill. The **directional predictor is `[S]` and measured-unsupported at this power**, not merely pending. External review (CodeRabbit) found 8 real defects across 23 threads; the two most valuable were the `var()`/MSE numerator and the CT-F14 artifact contradicting its own report. Docstring-coverage reported 69.23 % for three runs while measuring 100 % five ways locally; it self-corrected to 100 % — **declining to manufacture docstrings for an unreproducible metric was the right call.**