diff --git a/docs/LANES/ROUND26_INSTRUCTIONS.md b/docs/LANES/ROUND26_INSTRUCTIONS.md
index 53ec482..31d27cb 100644
--- a/docs/LANES/ROUND26_INSTRUCTIONS.md
+++ b/docs/LANES/ROUND26_INSTRUCTIONS.md
@@ -18,10 +18,13 @@ in the tree; and F is mid-harness on its re-run. Round 26 opens by closing both,
 
 ## WAVE 0 — close the alpha (before anything else starts)
 
-*Status update (Fable, post-F-close): F's half is **DONE** — verdict GREEN, work committed and
-pushed (`2994200`), and F held the tag a third time, correctly: tagging would have produced a
-tag whose tree lacks the code that produced the green (E's rebuild is uncommitted). Only step 1
-remains, then F tags immediately.*
+*Status update (Fable): **WAVE 0 IS COMPLETE.** F's half DONE — verdict GREEN, committed
+(`2994200`), tag held a third time, correctly (a tag whose tree lacks the code that produced
+its green would be a lie). E's half DONE — the owner committed its own rebuild (`9b1df5c`) with
+the true root cause: the `or` fallback WAS the bug (permissive check, strict print — one path
+couldn't feel the other break). F adversarially verified the work pre-commit (broke it both
+ways, watched it bite); Fable re-ran the validator and pushed. **F: step 2 is GO — confirm and
+tag `v5.0-alpha` on resume, then the beta waves below.***
 
 1. **E: commit your own work.** `pipeline/validate_atlas.py` carries your R25 rebuild, unstaged.
    If your session died before the commit: a fresh Lane E session verifies the diff against