6500ca0493466c7d53410fc0906f868a760275c9
Attempted to un-#[ignore] the M5 swarm leak-proof as the integration-level acceptance of bugfix-rc-global-stats-race (7bfa11e). Boss verification falsified the sufficiency premise: across 4-6 swarm runs the leak Σ is STILL non-deterministic — Σfrees stable-exact (12000003) every run, Σallocs short by a jittering ~1600-2260 in ~1/3 of runs (e.g. left:11998383 right:12000003, 4 stat lines). The atomic-global runtime fix (7bfa11e) is real, committed, and NECESSARY — the isolated 8x2M pure-global RED embed_rc_global_stats_race is deterministically green. It is NOT sufficient for the swarm: a second, distinct alloc-side undercount remains that the isolated RED did not model (Σfrees never loses => not a per-ctx race; not pure global contention => RED green). The un-#[ignore] was reverted (never committed). The ONLY shipped diff is the three now-stale #[ignore]-rationale breadcrumbs in ail-embed/tests/swarm.rs corrected from "un-ignore when the runtime makes the counters atomic" to the accurate necessary-but-insufficient state — a future agent seeing7bfa11emust NOT un-ignore on that basis (doc-honesty rule). The test body and the #[ignore] attribute itself are unchanged: still quarantined, NOT weakened. symbol_fan_swarm_bit_exact stays live and GREEN — the swarm IS actually correct and leak-free; only the accounting is wrong. Residual handed to a fresh debug RED-first cycle. Two framings recorded for it (genuine residual runtime defect vs Σ-over- heterogeneous-lines test-methodology unsoundness; the latter, if so, is a post-root-cause design decision). main stays green; M5 open [~]; m5.3 remains downstream of a sound leak-proof. Includes the resume-attempt journal + INDEX line.
Description
No description provided
Languages
Rust
91.6%
Python
4.6%
C
1.8%
LLVM
1.6%
Shell
0.4%