Add M10.6a probe-motion experiment core and session protocol v3
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m1s
Foundation / checks (network) (push) Successful in 12m13s
Foundation / checks (client) (push) Successful in 14m28s
Foundation / checks (tsan) (push) Successful in 7m56s
Foundation / checks (checks) (push) Successful in 32m49s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 40m58s

EXPERIMENT (ADR-0094), not an organism movement rule: one non-biological
marker per session, moved by admitted intentions with a shared integer rule
(probe-motion-v1, 100 mm per tick, clamped to the area), held in region
memory only.

- ProbeMarkers: spawn, area, bounded per-marker schedule, catch-up bound
- session protocol v3: marker records in snapshot chunks; the own marker is
  always sent with its applied sequence and area; v1 and v2 are refused
- MotionPredictor (bounded replay from the authoritative marker, corrections,
  error samples), CorrectionSmoother and InputLead
- tests: exact prediction with enough lead, refusal and lead adaptation,
  lost inputs, bounds, marker records through the codec

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-06 15:12:13 -04:00
co-authored by Claude Opus 5.5
parent d781492957
commit ab7e26c02e
20 changed files with 1135 additions and 18 deletions
+47
View File
@@ -4479,3 +4479,50 @@ Not done:
not in the dev manifest);
- ASan of the client remote test (msquic under sanitizers is still open);
- a clean-VM package run.
## 2026-10-06 — M10.6a probe-motion experiment core (ADR-0094)
Implemented (EXPERIMENT, not a game rule):
- probe-motion-v1, shared and integer-exact (`include/evo/network/probe_motion.hpp`);
- the server's `ProbeMarkers` (spawn, area, bounded schedule, catch-up bound);
- session protocol v3 marker records, kinds 5 and 6:
- the own marker is always sent, with its applied sequence and area;
- other markers pass the spatial filter;
- v1 and v2 are refused;
- the client `MotionPredictor` (bounded inputs, rebase and replay, corrections, error
samples), `CorrectionSmoother` and `InputLead` (`include/evo/client/motion_prediction.hpp`).
Tests (`tests/network_motion.cpp`):
- the rule's arithmetic and clamping;
- the marker rules;
- client/server loops with whole-tick delays:
- with enough lead, every prediction is exact (zero corrections);
- with too little lead, refusals until the lead adapts, then exact;
- lost inputs give corrections;
- predictor bounds, refusal, drop and reset;
- smoothing and snap, and lead adaptation;
- marker records through the real codec: own versus other, the own marker outside the
interest, unchanged markers not resent, removal, and four malformed records.
The tests that used "3" as a future protocol version now use 4.
Executed:
- **Linux GCC 14**
- `evo-network-tests` and `evo-quic-session-tests`;
- preset `quic`: CTest 4/4;
- `client-network`: 14/14;
- `postgres-check.sh` with QUIC: 20 suites, including region m10 session.
- **Linux Clang 19:** build, ASan/UBSan `evo-network-tests`, clang-tidy 19 on the new and
changed sources and tests.
- **Windows MSVC 19.44** (fresh binaries):
- preset `quic`: 4/4;
- preset `client-network`: 12/12.
The repository format check fails only on `include/evo/server/session_window.hpp`, as
before.
Not done:
- wiring into sessions, evo-server, the probe and the GUI (10.6b);
- impaired traces (10.6c).
Deployed v2 servers refuse v3 clients until redeployed.