Remove the flawed busy-wait relaunch and WAIT-check logs (Captain Bob: "no need to keep flawed logs")

logs/20260924-062703 and logs/20260924-081340 plus their run CSVs; they
remain in history at 00058e53. FABRIC-3.8 entry updated to match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

FABRIC-3.8.md

@@ -1372,8 +1372,10 @@ explicit instruction.
       **FABRIC-3.8's staged plan (A–I) is complete.** What's next is the per-ISA DoE relaunch
       (seed 12345, 3 reps) on the rebuilt driver, then the merge to master.
 - [x] **DoE relaunch, first attempt, stopped (2026-09-24).** Launched `12345 3 S" amd64" DOE` at
-      06:31 (`logs/20260924-062703/amd64/`, kept). Captain Bob stopped it at 08:12 (*"STOP and
-      hold"*) after a progress check showed the busy-wait cost.
+      06:31. Captain Bob stopped it at 08:12 (*"STOP and hold"*) after a progress check showed
+      the busy-wait cost. **Its log and the `100 WAIT` check log below were removed at Captain
+      Bob's instruction** (*"no need to keep flawed logs"*). They are still in git history, at
+      commit `00058e53`.
       - 173k heartbeat rows at ~31 rows/s, ~100k switches, 0 faults. Trial 1 (cfg 3,
         heterogeneous) was still running, so no trial had finished.
       - **Hera had written 75,117 rows against its last worker `mu0`'s 75,114.** `MU-WAIT-ALL`'s
@@ -1387,12 +1389,12 @@ explicit instruction.
           writes no rows.
         - The decision then favours the workers at her next checkpoint.
         - No yield word; capsule-only change.
-      - **Check** (`logs/20260924-081340/amd64/`, own boot, images reset after): a cfg-0 trial ran
-        in **115 s against ~210 s before**, `fail=0`, 2/2 dead.
+      - **Check** (own boot, images reset after): a cfg-0 trial ran in **115 s against ~210 s
+        before**, `fail=0`, 2/2 dead.
       - **REVERTED the same day, Captain Bob:** *"not liking this much ... redistribute work when
         hera is the major consumer"*, then *"1, revert the WAIT commit"*.
         - `100 WAIT` had the application steer its own scheduling, by faking work so the kernel
           would back off. The fix belongs in the kernel's compudynamics (option 1: charge by
           share), not in the DoE capsule.
-        - Only the one capsule line is reverted. The logs and this entry stay, because logs are
-          never deleted.
+        - Only the one capsule line is reverted. This entry stays as the record; the two logs were
+          removed afterwards, on Captain Bob's instruction (see above).