board: state the consequence, not the confession

Rewrites two passages as guidance for the next session: the CI note now says
do not add a job (one exists) and names upstream-change notification as the
open gap; the harness note states the CWD requirement and how to run the flip
correctly. Technical content unchanged.

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

Author: claude

.claude/board/EPIPHANIES.md

@@ -15,10 +15,10 @@ lance-graph — exactly what added `ExecError::RangeOutOfBounds` — cannot star
 it, so the break stayed invisible until the next push here. Coverage was never
 missing; the *event* was.
 
-**Why the wrong diagnosis was worse than no diagnosis:** it would have sent the
-next session to add a CI job that already exists, and left the real gap — no
-upstream-change notification — untouched. Found by Codex P2 on #82; I verified
-it against the workflow rather than accepting or dismissing the finding.
+**Consequence for the next session:** do not add a CI job for this — one
+exists. The open gap is upstream-change notification, and nothing in this
+repository's triggers can close it. Raised by Codex P2 on #82, verified
+against the workflow.
 
 ## E-PANAMA-TIMES-VALHALLA-IS-ONE-MEMBRANE-AND-THE-LAB-FINALLY-HAS-ONE-VARIABLE-1 (2026-09-19)
 
@@ -153,14 +153,13 @@ tripwire, not a safety net:** it converts an upstream additive change into a
 downstream build failure, and nothing in either repo's CI noticed, because no
 CI job here compiles the native crate.
 
-**Two false failures I nearly reported, both mine, both caught by reading.**
-The flipped suite showed `1 FAILED` twice. Both times it was
-`DoctrineFenceTest` refusing to run — it requires `java/src/main/java` AND
-`native/lgj-abi/src` relative to CWD, and I had run the flipped build from a
-scratch directory that had neither. The fence is *correct*: its first check is
-*"a fence that cannot find its corpus must fail, not skip."* Running the flip
-in the real tree (committed first, restored with `git checkout`) gave the true
-result. **A harness artifact and a regression look identical in a summary
+**Harness note, so the next run is not misread.** The flipped suite reports
+`1 FAILED` when run from a directory lacking `java/src/main/java` AND
+`native/lgj-abi/src` — `DoctrineFenceTest` resolves both relative to CWD and
+refuses to run without them. The fence is behaving correctly: its first check
+is *"a fence that cannot find its corpus must fail, not skip."* **Run the flip
+in the real tree** (commit first; restore with `git checkout`) or the result is
+not the suite's. **A harness artifact and a regression look identical in a summary
 line** — this is the ruff trap "a disable that does not apply is
 indistinguishable from a guard that is not load-bearing", met from the other
 direction.