RUDPClient/openspec/changes/archive/2026-03-29-implement-server-authoritative-movement-state-broadcast/tasks.md

1. Server Authority Core

• 1.1 Add a dedicated server-authoritative movement coordinator and per-peer authoritative movement state model under Assets/Scripts/Network/.
• 1.2 Register MoveInput handling through the server host/runtime composition path and validate sender-scoped movement payloads before accepting them.
• 1.3 Keep stale movement tick acceptance independent per managed peer and ensure zero-vector input clears authoritative movement velocity.

2. Authoritative Snapshot Broadcast

• 2.1 Add an explicit server authority update hook that advances authoritative movement resolution on a fixed cadence.
• 2.2 Broadcast authoritative PlayerState snapshots through the existing MessageManager sync-lane contract, with reliable fallback when no sync transport exists.
• 2.3 Expose the minimal runtime/host surface needed for host processes and tests to drive movement authority updates and inspect authoritative peer state.

3. Regression Coverage And Documentation

• 3.1 Add edit-mode regression tests for accepted vs stale MoveInput handling across multiple peers.
• 3.2 Add edit-mode regression tests for zero-vector movement stop and fixed-cadence PlayerState broadcasting on sync and fallback lanes.
• 3.3 Update TODO.md and related change tracking/docs to reflect the completed server-authoritative movement/state broadcast work.