542 B
542 B
Stress test outline (to add in PR‑7.9 or here if desired) • Build a bytecode program with a tight loop containing arithmetic + occasional YIELD and ensure: ◦ Under tiny budgets (1–n cycles), pc progression is identical across runs. What I changed and why Open in editor ◦ Switches (simulated by alternating between two VMs) occur only ▪ immediately after step() completes, or ▪ when run_budget returns FrameSync. ◦ No observable state change occurs when force‑switching between two VMs mid‑tick except at these safepoints.