# Corrected movement resumption with persistent byte and command state

RE-783. Reproduce with `python3 scripts/analyze_qvm_execute_reentry.py`; validate with `cargo xtask test-group execute-reentry`. See the [machine report](qvm-execute-reentry.json).

Eighteen byte persistence witnesses retain legacy/corrected results. Five countdown loops, signed command-byte reinjection, dynamic returned-word byte reads and nonempty-stack rejection exercise the corrected movement resumer. The new optional repeated_calls flag preserves existing fixtures by default during migration. Correct mode uses the shared fail-closed return patch and retains byte state between segments; command bytes remain explicitly authoritative through the handler return tuple. Child arbitrary byte writes are not part of that interface.

No original executable/full VM/native world collision or rendering runs. Supplied callback/native responses and fixture domains remain explicit; complete macOS/Linux Rust/Bevy/Solari gameplay remains open.