Wire M10.6b probe markers through sessions, evo-server, probe and client
Foundation / checks (checks) (push) Successful in 32m33s
Foundation / checks (client) (push) Successful in 12m28s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (network) (push) Successful in 12m8s
Foundation / checks (postgres) (push) Successful in 40m38s
Foundation / checks (tsan) (push) Successful in 8m4s
Foundation / postgres-tools (push) Successful in 1m36s
Foundation / image (push) Successful in 2m33s
Foundation / server-image (push) Successful in 3m53s

EXPERIMENT (ADR-0094). RegionSessions owns the probe markers: admitted
intentions schedule them, each poll advances them to the simulated tick, and
snapshots carry them. evo-server sets the motion area from the region's
habitat sites; the probe prints its own marker.

The engineering client predicts its marker with the adaptive input lead,
rebases on each snapshot, resends a lost or refused intention, smooths
corrections, draws markers and follows its own with camera and interest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-06 16:07:34 -04:00
co-authored by Claude Opus 5.5
parent ab7e26c02e
commit 96237ca10a
17 changed files with 334 additions and 27 deletions
+36
View File
@@ -4526,3 +4526,39 @@ Not done:
- impaired traces (10.6c).
Deployed v2 servers refuse v3 clients until redeployed.
## 2026-10-06 — M10.6b probe-marker wiring (ADR-0094)
Implemented:
- `RegionSessions` markers (`set_motion_area`, schedule on admission, advance per poll,
close and loss, clear on a new epoch, markers in every snapshot source);
- the evo-server motion area (the habitat sites' bounding cells, `m10 motion area`);
- the probe's `marker` lines;
- the engineering client's prediction, adaptive lead, resend after loss or refusal,
smoothing, marker drawing, the follow camera and interest, and Session panel rows.
Evidence:
- `client-remote-session`: the marker at its spawn, followed by camera and interest; an
intention moves the predicted marker +x, and the authority confirms it with zero maximum
error and no pending inputs. Passed 3 times in a row.
- The real-process test (`region_m10_session_tests`): the probe's own marker moved +x with
its intention applied, and evo-server printed its motion area. The snapshot report is
now 8,966 bytes in 40 ticks, including the marker records.
Executed:
- **Linux GCC 14:**
- preset `client-network`: CTest 14/14;
- preset `quic`: 4/4;
- `postgres-check.sh` with QUIC: 20 suites.
- **Linux Clang 19:** build, plus clang-tidy 19 on the client app, the remote test,
RegionSessions, the probe and probe_motion.
- **Windows MSVC 19.44** (fresh binaries; built while the formatting pass ran, which
changed whitespace only):
- preset `quic`: 4/4;
- preset `client-network`: 12/12.
clang-format 19 was applied to the changed files.
Not done:
- impaired traces (10.6c);
- a GUI run against evolution-dev, which needs a v3 server.