# Full40966 entry helper: resource, event and animation RE-545 / F-268. Reproduce with `python3 scripts/analyze_qvm_jump_entry.py`; check with `python3 scripts/test_qvm_jump_entry.py`. The [machine report](qvm-jump-entry.json) contains the complete40966–41485 partition and84 finite fixtures. This extends the earlier [flags12 entry subset](QVM_FLAGGED_MODE.md). No original executable, full QVM, native collision, physics or rendering executes. The initial guards retain their source order: flags256 returns0; signed up<10 returns0; existing8192 stores command up0 and returns0. Otherwise40966 clears plane/walk, sets8192 and ground1023. The flags12 branch retains its planar direction×−50 impulse and16 store, without event/resource/animation suffix effects. For the successful non-flags12 branch, state220 bit128 or resource strictly below1500 selects the reduced launch: all current velocity components are first halved and Z is then replaced with202.5. Otherwise current X/Y remain and Z becomes270. Equality1500 takes the full launch unless128 is set. This branch does not set16. Actual39238(99)/29913 updates the two-slot numeric event queue. Flag4096 then toggles. Previously set4096 chooses animation26 for nonnegative forward or30 for negative forward; previously clear4096 chooses28 or32. Actual39525/39383 runs before resource deduction. Raw animation equality retains the leg timer; otherwise the forced helper clears it even when type3 prevents the animation store. Numeric event/flag meanings and the full gameplay interpretation remain unverified. The base cost is3600 when any of the first16 inventory low bytes equals17, otherwise1800. Slot16 is excluded from this scan. Configuration34065924>=2 skips deduction; otherwise the helper subtracts cost and clamps negative resource to0. Launch-speed selection precedes this cost, so the resulting low resource does not retroactively change the launch. Fixtures cover1499/1500/4000,128, existing4096, inventory absence/slot0/slot16 and configuration0/2, plus guard/flags12/type/equality controls. Eight tests independently predict the full captured helper state, command bytes, return and child order; threshold/velocity/cost behavior; numeric queue; all four requests; timer/type/equality priority; guarded STORE1; and source identity. Native planar roots, basis, commands, finite state and configuration remain supplied. No movement caller or scheduler is evaluated by this report. Original reference traces, native/legal domains and platform gameplay remain open. Subsequent tasks connect this helper to actual walking-mode routing and air movement. Follow-up: [actual walking entry routing](QVM_WALK_ENTRY.md) consumes the full helper return/state at43626 and the main walking boundary. Delegated movement effects remain explicit gaps in that report.