Rewrote EXEC-STD79-DOE-CD's dispatch to coordinate via MSG-SEND/
MSG-TICK instead of blocking VM-EXEC, now that Hera can genuinely
message (§XX). RUN-TEST/EXEC-STD79-DOE (the serialized baseline) are
untouched, kept as a byte-for-byte-reproducible historical comparison
point.
A small 2-identity smoke test before any multi-architecture
commitment caught two real defects the design alone didn't predict:
1. Absolute VM-HEAT can't produce fine-grained interleaving -- a
fresh identity starts at heat=0 against Hera's ~62000+, a gap no
1..24 divisor closes, so priority locked onto whichever identity
had executed least, for its entire campaign. Fixed with BASE-HEAT:
each identity's heat is snapshotted once at campaign start, and
priority is computed from heat gained *this campaign*, not
lifetime heat.
2. Single-test-per-message granularity silently drops most of a
campaign's data: MSG-SEND no-ops on MSG-ALLOC failure, and the
turn bookkeeping advanced regardless, so rows looked complete
while missing most of their tests. A live reservoir probe showed
Hera's own STADIUM-RES@ draining ~725/cycle with no
replenishment observed -- a 648-send full campaign would exhaust
it almost immediately. Fixed by dispatching a whole rep (24 tests,
one concatenated command, measured 442 bytes, well under
VM-EXEC's 1025-byte cap) per message instead -- 27 sends for a
full campaign, not 648.
Re-verified after both fixes: 99/99 expected test outputs present,
zero drops, zero faults, genuine rep-level interleaving instead of
either the serialized baseline's fixed order or the first cut's
72-test lock-in.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EXieurDfDSsDFdnSyusuWo
