erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs: close #161 (user-verified) - landing-pose fix b1cf0102; next up #162 adjudication + #163 diag strip

Browse source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-07-03 17:11:16 +02:00
parent b1cf01029a
commit 584ad0a8f6
2 changed files with 51 additions and 56 deletions
Download patch file Download diff file Expand all files Collapse all files

26
docs/research/2026-07-03-r4-verify-session-handoff.md
View file

@ -36,19 +36,19 @@ whole gate state — it is how both wedges were pinned.
## OPEN — next session picks up here (full trails in docs/ISSUES.md)
1. **#161 — remote jump landing stuck in the falling pose** (retested
post-TS-40: still broken). Evidence in the issue: `VU.land` fires but
the first post-landing UM still sees `seq now motion=0x40000015`; the
char recovers only via subsequent wire UMs; window-focus change also
unsticks it (a frame-advance/big-dt hint). PRIME SUSPECT: the funnel's
airborne branch dispatches Falling via `DoInterpretedMotion` with
ctor-default `ModifyInterpretedState=true` → interpreted fwd BECOMES
0x40000015 → `HitGround`'s `apply_current_movement` (interpreted branch
for remotes) re-dispatches FALLING instead of the pre-fall wire command.
CHECK RETAIL FIRST: does raw ~305730's falling dispatch really write
interpreted fwd; what exits Falling on a retail REMOTE landing
(HitGround raw @305949, the `apply_current_movement(this, 1, ...)`
arg semantics); does K-fix17's landing SetCycle even execute (probe it).
1. ~~**#161 — remote jump landing stuck in the falling pose**~~ **CLOSED
2026-07-03 `b1cf0102`, user live-verified.** The prime suspect was
right; the mechanism was a BN decomp artifact: retail REWRITES the
apply pass's params word (raw 305778 smeared store, mask 0x37ff →
`ModifyInterpretedState=false`; ACE MotionInterp.cs:444-449 confirms),
so retail PRESERVES interpreted fwd through the fall and HitGround
re-dispatches it (the landing-link exit). Also: both landing blocks
cleared Gravity BEFORE `Motion.HitGround()` (whose verbatim state&0x400
gate then no-opped — fixed order, AP-81); K-fix17's SetCycle DID
execute but re-set the clobbered Falling command — both copies deleted.
NOTE: "HitGround raw @305949" below was a mislabel (that line is inside
`move_to_interpreted_state`; real HitGround = 0x00528ac0 →
`apply_current_movement(0,0)`). Full trail: ISSUES Recently-closed #161.
2. **#162 — glide-class adjudication (PENDING USER)**: ACE re-broadcasts
every mover MoveToState to observers as autonomous mt-0
(MovementData.cs:162 — ACE's own "this is a hack" comment;