urt-rs / docs /research /QVM_FLOAT_EXIT_RULES_BATCH.md
nmarshall's picture
gameplay: compose recovered exit rules
5f7b2df
|
Raw History Blame Contribute Delete
3.2 kB
# Float formatter and exit-rule composition: RE-824–833
Ten tasks recover original float formatting and compose the exit-rule body 7805 into Rust. These are bounded source contracts, not a running game or complete native parity.
| Task | Result |
| --- | --- |
| RE-824 | [Float formatter source arithmetic](QVM_FORMAT_FLOAT.md) |
| RE-825 | [Rust float formatter](RUST_FORMAT_FLOAT.md) |
| RE-826 | [Mode11 class guard](QVM_EXIT_CLASS.md) |
| RE-827 | [Rust class guard](RUST_EXIT_CLASS.md) |
| RE-828 | [Score/team exit limit priority](QVM_EXIT_LIMITS.md) |
| RE-829 | [Rust limit policy](RUST_EXIT_LIMITS.md) |
| RE-830 | [Round/time gates and mode 9 reset effects](QVM_EXIT_TIMERS.md) |
| RE-831 | [Rust timers and reset intentions](RUST_EXIT_TIMERS.md) |
| RE-832 | [Continuous exit-rule source composition](QVM_EXIT_COMPLETE.md) |
| RE-833 | [Rust complete recovered exit policy](RUST_EXIT_COMPLETE.md) |
## Evidence and boundaries
The float helper has 126 fixtures, plus 12 central formatter fixtures. It truncates repeated f32 fractional arithmetic; width applies to the integer portion. Negative zero loses its sign. Rust rejects nonfinite/out-of-domain values and bounds precision and width explicitly.
Exit class, limit and timer contracts have 45, 125 and 116 fixtures respectively. Continuous 7805 execution covers 438 cases, including conflicting priorities and shared client mutations. Rust matches those decisions, pending-state updates and reset intentions. The active round gate bypasses time-limit evaluation; the mode 9 path distinguishes collected client count from configured scan bounds.
Child 7662 remains a supplied predicate. Calls 7525/6825/7367, formatting, sending, logging and event allocation are captured or supplied effects. Event 69 intentions expose owner/time and flag OR 256; the source fixture supplies initial constructor flags 16. Neither adapter establishes the real allocator or transition implementation. Native/JIT execution, real game traces and unrestricted memory legality remain unverified.
## Validation
Focused cargo xtask groups passed before each task commit. Reports were regenerated twice with deterministic output, relevant Python and scoped Rust checks, storage policy, documentation links and whitespace validation. After commit ten, `cargo xtask test-full --since 1ed43d40` passed: 1,628 Python tests, 127 Rust tests (assets 10, gameplay 89, xtask 28), 43 affected producers regenerated twice deterministically, storage policy, 392 documentation files and whitespace checks. Generated reports left no uncommitted differences. This was the only full-suite invocation in the batch.
## Next work: RE-834
- [ ] Recover 7662 and replace the supplied predicate with original instruction evidence.
- [ ] Recover 7525/6825/7367 transition effects and their world/state ownership.
- [ ] Resolve formatting, copy, log, send and event constructors used by these paths.
- [ ] Integrate ranking, exit decisions and scoreboard publication across shared state.
- [ ] Audit legacy trace/memory assumptions and compare actual native/gameplay traces.
- [ ] Connect verified policies to the game runtime and validate macOS/Linux Bevy/Solari behavior.