Revert the MU-WAIT-ALL '100 WAIT' change (Captain Bob); keep its logs

The fix belongs in the kernel's compudynamics, not in the DoE capsule
steering its own scheduling. Logs from the stopped relaunch and the check
run stay committed.

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

FABRIC-3.8.md

@@ -1389,3 +1389,10 @@ explicit instruction.
         - 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.
+      - **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.

capsules/multiuser-doe.4th

@@ -120,7 +120,7 @@ Block 5052
     I MU-SEND-WORKER
   LOOP ;
 : MU-WAIT-ALL ( -- )
-  BEGIN MU-DONE-COUNT @ MU-NW @ < WHILE 100 WAIT REPEAT ;
+  BEGIN MU-DONE-COUNT @ MU-NW @ < WHILE REPEAT ;
 
 Block 5053
 : MU-KILL-ALL ( -- )