feat(L.2b): outbound movement wire parity — RawMotionState default-difference, JumpPack, contact byte

Ports the three retail outbound-movement packers verbatim (decomp-derived
golden bytes, confirmed via the Ghidra bridge, cross-checked vs holtburger):

- D1 — RawMotionState::Pack (0x0051ed10): new AcDream.Core.Physics.RawMotionState
  data type (11 fields + actions, retail defaults) + RawMotionStatePacker that
  sets a flag bit only when the field DIFFERS from its default. MoveToState.Build
  now takes a RawMotionState instead of presence-based nullable params, so the
  over-sent forwardSpeed=1.0 / currentHoldKey=None / default per-axis holdkeys are
  no longer emitted. num_actions packs into bits 11-15 (not "bits 11-31").
- D3 — MoveToStatePack::Pack (0x005168f0) trailing byte =
  (standingLongjump ? 0x02 : 0) | (contact ? 0x01 : 0); explicit contact/
  standingLongjump params (standingLongjump=false honestly until the feature lands).
- D4 — JumpAction rewritten to retail JumpPack::Pack (0x00516d10): extent,
  velocity, full Position, four u16 timestamps, align. Removed the spurious
  objectGuid/spellId u32s; Position is now packed (it was absent). Body 56 bytes.
- Position::Pack (0x005a9640) / Frame::Pack (0x00535130) verified already-correct
  (cellId, origin xyz, quaternion wxyz); locked with a golden test, no change.

GameWindow callers adapted minimally: build the RawMotionState from the existing
MovementResult values (behavior preserved except the intended D1 omissions) and
pass cellId/position/rotation to the Jump send. Pre-existing MotionInterpreter
placeholder struct RawMotionState renamed LegacyRawMotionState (D6/Phase-2 scope,
pure rename) to free the name for the retail-faithful type.

D5 audit: confirmed a real divergence — retail SendMovementEvent (0x006b4680)
stamps only last_sent_position_time after an MTS while SendPositionEvent
(0x006b4770) stamps all three; acdream's NotePositionSent stamps all three on
both paths. Left unchanged (comments added at both call sites), recorded as
register TS-33, deferred to a dedicated cadence-port slice.

Tests: RawMotionStatePackTests / MoveToStateGoldenTests / JumpActionTests /
PositionPackTests + updated MoveToStateTests / AutonomousPositionTests. Full
suite green (Core.Net.Tests 372, full solution 3228 passed / 4 pre-existing skips).

Register: TS-24/TS-25 refreshed (packer now supports actions/style; runtime
emission still deferred), TS-33 added. Roadmap L.2b shipped note added.
Spec: docs/superpowers/specs/2026-06-30-movement-wire-parity-design.md (2-6)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/superpowers/specs/2026-06-30-movement-wire-parity-design.md

@@ -261,7 +261,15 @@ address in each test) and cross-checked against holtburger's Rust packers.
   `RawMotionState` (run-vs-walk `forward_command`, hold-key derivation, backward
   / sidestep-left speed normalization). This slice makes the *packer* verbatim;
   state construction is `adjust_motion`/`apply_raw_movement` (audit Phase 2).
-- **D5:** heartbeat-clock stamping is *audited* here, changed only if proven.
+- **D5 (CONFIRMED 2026-06-30, deferred):** the audit found a real divergence —
+  retail's `SendMovementEvent` (0x006b4680) stamps ONLY `last_sent_position_time`
+  after an MTS, while `SendPositionEvent` (0x006b4770, AP) stamps all three
+  (time + position + contact-plane); acdream's `NotePositionSent` stamps all three
+  after both. Broader: acdream gates APs on a plain interval (`HeartbeatDue`) where
+  retail uses `ShouldSendPositionEvent` (0x006b45e0). Left unchanged this slice (code
+  comments added at both call sites); recorded as register row **TS-33** and deferred
+  to a dedicated cadence-port follow-up slice (port `ShouldSendPositionEvent` + split
+  MTS/AP stamping).
 - **D2:** actions-list / current_style packing is structurally supported and
   tested, but the runtime emits 0 actions; populated emission is Phase 2+.
 - **D9/D8/D10/D11/D12, D7:** later L.1/L.2 slices.