Walking43626 entry routing and full40966 state
RE-546 / F-269. Reproduce with python3 scripts/analyze_qvm_walk_entry.py; check with python3 scripts/test_qvm_walk_entry.py. The report contains24 standalone prefix fixtures and4 actual main chains. It connects full40966 at walking CALL43660, replacing stored local108 before the caller reads it.
The prefix first checks level>2 and forward-basis dot ground-normal>0. Both conditions request41848 immediately, bypassing40966 entirely. Otherwise it evaluates the actual entry helper. Return1 chooses41848 when level>1 and42838 otherwise. Return0 continues at43683 before ordinary walking friction. Source guards, strict dot comparison, source child call order and helper memory/command-byte changes are retained.
Prepared entry effects never attach to the initial deep-level bypass. Existing8192/up10 instead stores up0 in the reached helper and returns0, so the parent continues ordinary walking with changed input. Successful non-flags12 entry clears plane/walk, sets ground1023, changes velocity/resource/animation and emits event99 before the delegated movement request.
The standalone grid varies level0/2/3, supplied forward Z−3/0, up9/10 and flags0/8192. Main uses actual clock/timer/action/query routing with flags32/160 controls. Two cases select43626; higher-priority128 selects41768 in two controls and receives no walking callback. Main leg timer77 ages to61 before entry. A successful entry then forces leg timer0 and reduces resource4000 to400 with inventory slot0=17; queue99 persists into the recorded suffix.
This report stops at normal continuation43683 or delegated jump45199. Ordinary walking suffix and requested41848/42838 effects remain omitted here. Source main callback applies at54433 after43626's actual CALL/POP. Native roots, level/basis/normal/ground/input state remain supplied; no original executable/full QVM/native collision/physics/rendering executes. A later task can attach recovered42838 effects to this explicit request boundary.
Eight independent tests check prefix/deep-level priority, full helper state/child formulas, delegated target and stop, held-up byte propagation, actual main gating, timer/resource/event order and source/scope. Full-suite/regeneration/storage/link/whitespace results are recorded in the ledger. Complete walking and other modes, native/reference/legal domains, full main/scheduler and Rust/Bevy/Solari platform gameplay remain open.
Follow-up: ordinary42838 continuation attaches reached air movement to successful launch, retaining ordinary walking/deep-water gaps. The earlier prefix-only report remains byte-identical.