urt-rs / docs /research /QVM_NOTIFICATION_REENTRY.md
nmarshall's picture
qvm: audit notification reentry
ef920e6
|
Raw History Blame Contribute Delete
975 Bytes
# Audited notification reentry and 64-slot recipient dispatch
RE-784. Reproduce with `python3 scripts/analyze_qvm_notification_reentry.py`; validate with `cargo xtask test-group notification-reentry`. See the [machine report](qvm-notification-reentry.json).
Twenty-four source fixtures vary single/pair paths, activity and counts-1,0,1,4,16,64 with five connection states. Tests independently enumerate state2 recipients and exact call arguments. Differential comparison checks the complete returned memory, trace and effect tuple, not only call counts. Captured recipients have no modeled memory effects, so equivalence here does not audit real callback internals. Existing notification and resolved lifecycle report consumers are regenerated by the focused group.
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.