# Damage location jump table and client flags

RE-709. Reproduce with `python3 scripts/analyze_qvm_damage_location_flags.py`; check with `python3 scripts/test_qvm_damage_location_flags.py`. The [machine report](qvm-damage-location-flags.json) retains source identity and bounded fixtures.

Actual290298–290373 checks signed location1–14 before reading the original file-backed32796+4×location jump table. Locations1/2 dispatch290357 and set bit4 at client192. Locations3/4/7/8 dispatch290319 and set bit1. Locations5/6/9–14 dispatch290338 and set bit2. OR operations preserve existing bits, including high-bit fixtures. Negative, zero and above14 locations bypass all writes. This slice assumes a nonnull client for accepted locations, matching its explicit fixtures; null-client legality remains unproven. No child calls or health damage occur.

No original executable/full QVM/native collision/physics/rendering executes. Native responses and legal input domains are supplied or unverified where stated; full runtime/macOS/Linux Rust/Bevy/Solari gameplay remains open.