Add data-only proxy animation debug logging

Track and log per-slot animation/movement diagnostics for runtime proxy actors without applying any visual animation. Adds a ProxyAnimationSpeedBucket enum and GetProxyAnimationSpeedBucket/GetProxyAnimationSpeedBucketLabel helpers, a new UpdateProxyAnimationStateDebug() routine, and fields on ProxyActorSlot to remember last-observed moving, sprinting, sneaking, jumping, weapon-drawn, movement type, and coarse speed-bucket state. Resets observation state when slots are created/reused and emits initial/transition-only logs including playerId and proxy FormID. Documentation and dev-log entries updated; visual animation, animation graph changes, and AI/movement behavior remain intentionally unmodified.

docs/architecture.md

@@ -32,7 +32,7 @@ both send and receive paths:
 12. For each eligible remote `playerId`, the controller maintains a
     `remotePlayerId -> runtime proxy slot` mapping. Each slot stores its
     `ObjectRefHandle`, lifecycle state, PlaceAtMe-backed spawn/candidate state,
-    movement smoothing state, and sneak observation state. Stage 4 caps runtime
+    movement smoothing state, and data-only animation debug state. Stage 4 caps runtime
     proxy slots at four actors for testing.
 13. Runtime proxies are demand-driven. A slot executes the Stage 3.7
     PlaceAtMe-backed spawn flow only when that remote player needs a same-cell
@@ -53,8 +53,9 @@ both send and receive paths:
     actor.
 15. Proxy visual updates are independent per slot. Normal movement is smoothed
     toward that player’s latest target, while `cell_change`, `worldspace_change`,
-    and `teleport` snap directly. Sneak state is still observed and logged only;
-    no visual crouch/sneak application is attempted.
+    and `teleport` snap directly. Movement and animation-related remote state is
+    still observed and logged only; no visual crouch/sneak, jump, weapon drawn,
+    locomotion, animation graph, or actor-state application is attempted.
 16. When a remote player leaves the cell or disconnects, only that player’s
     runtime proxy is moved to the hidden holding position inside
     `F4TTestCell01`. Runtime actors are not disabled or deleted. Connected
@@ -118,6 +119,15 @@ reused.
 The placed proxy reference remains as a single fallback path if runtime spawning
 fails for one selected remote player.
 
+Current animation-state handling is data/debug only:
+
+```mermaid
+flowchart LR
+    RemotePlayerState[RemotePlayerState] --> ProxyActorSlot[ProxyActorSlot animation debug state]
+    ProxyActorSlot --> Logs[Initial and transition logs]
+    ProxyActorSlot --> FutureVisualAnimation[Future visual animation application]
+```
+
 ## Main Components
 
 ### F4SE Plugin
@@ -153,6 +163,9 @@ The native plugin is responsible for:
   path after spawn promotion, during reusable-slot reassignment, periodically
   while active, and while held so they remain passive visual puppets rather than
   independent combat actors
+- Logging initial and transition-only data/debug animation state per resolved
+  runtime proxy slot from `RemotePlayerState`, including moving, speed bucket,
+  sprinting, sneaking, jumping, weapon drawn, and movement type
 - Suppressing exposed AI movement intent for runtime proxies by clearing safe
   process target handles and using validated package interruption/do-nothing
   calls when combat, pathing, flee/alarm, bump, or package movement state is
@@ -237,6 +250,7 @@ Game update attempts at most one PlaceAtMe-backed runtime actor spawn at a time
 Game update snapshots matching candidates, isolates the new actor, and waits for the settle window
 Game update moves isolated Stage 4 runtime spawn candidates to the remote player's current transform
 Game update stores promoted runtime actors as ObjectRefHandle values in slots
+Game update logs data-only animation debug state for resolved runtime proxy slots
 Game update neutralizes resolved runtime proxy actors after spawn promotion, reuse, active throttled checks, and holding
 Game update suppresses exposed AI movement/pathing intent without forcing animation graph events
 Game update moves each valid proxy from its assigned remote player state

docs/dev-log.md

@@ -2257,6 +2257,63 @@ starting near the local player before snapping away.
 
 ---
 
+## 2026-06-03 - Proxy Animation State Debug Pass
+
+### Summary
+
+Added data-only per-slot animation state diagnostics for runtime proxy actors so
+the proxy controller can observe movement and animation-related state assigned to
+each remote `playerId` without visually applying animation.
+
+### Files Changed
+
+- `plugin/src/F4TProxyActorController.cpp`
+- `docs/architecture.md`
+- `docs/dev-log.md`
+
+### Details
+
+- Added per-runtime-proxy-slot debug tracking for moving, speed bucket,
+  sprinting, sneaking, jumping, weapon drawn, and movement type.
+- Added transition-only runtime proxy animation state logs that include the
+  remote `playerId` and resolved proxy actor FormID.
+- Movement speed diagnostics use coarse buckets (`idle`, `slow`, `walk`, `run`,
+  `sprint`) so small float changes do not spam the log.
+- Reset animation debug state when slots are created, reassigned, held, or pass
+  through the existing slot observation reset helper.
+- Kept this pass data/debug only. It does not apply visual animation, force
+  animation graph events, write animation graph variables, call `PerformAction`,
+  write `ActorState`, or add package/pathing/AI movement changes.
+- Networking, protocol, Python server code, fake-client tooling, placed fallback
+  behavior, spawn-at-remote-position, movement smoothing, snap behavior,
+  same-cell gating, held/reusable lifecycle, and combat/AI neutralization were
+  unchanged.
+
+### Testing
+
+- Ran `xmake build` from `plugin`; it succeeded and rebuilt
+  `Fallout4Together.dll`.
+- Pending manual validation: launch through F4SE, start the server, add fake
+  clients in `F4TTestCell01`, and confirm per-player initial and transition
+  animation state logs without visual animation changes.
+
+### Known Issues
+
+- Speed bucket thresholds are conservative diagnostics and still need tuning
+  against real Fallout 4 movement units before any future visual locomotion work.
+- Visual animation application remains intentionally unimplemented.
+
+### Next Steps
+
+- Investigate safe visual sneak/crouch application.
+- Investigate weapon drawn visual application.
+- Investigate locomotion animation graph behavior.
+- Investigate jump animation behavior.
+- Research safe animation graph variable/event reads or writes before any visual
+  animation milestone.
+
+---
+
 ## Entry Template
 
 Use this format for future updates: