docs(headless): close K3 connected gates

This commit is contained in:
Erik 2026-07-27 10:28:53 +02:00
parent 3f3401257c
commit 827a039760
7 changed files with 183 additions and 44 deletions

View file

@ -294,14 +294,17 @@ residency is `0/0/0` at every stable checkpoint and teardown converges. Slice I
absolute-deadline scheduler, the shared Runtime local-player frame sequence,
complete generation-gated bot commands, and lifecycle/entity/inventory/chat/
movement/portal/combat/command events pass 411 Runtime, 31 Headless, 3,732
App / 3 skips, and 8,744 complete Release tests / 5 skips. K3's automated
checkpoint landed across `12b500d3`, `9569dadb`, and `b6547ff3`: exact
App / 3 skips, and 8,744 complete Release tests / 5 skips. K3 completed
across `12b500d3`, `9569dadb`, `b6547ff3`, and `3f340125`: exact
process content leases, immutable magic/terrain/bounded collision sharing,
presentation-free local-player/collision hydration, 1/5/10-session
same-GUID/portal/reconnect isolation, and policy-fault quarantine pass 412
Runtime, 42 Headless, 3,722 App / 3 skips, and 8,758 complete Release tests
/ 5 skips. The visible-terminal Windows and Linux/WSL production gates
remain before K3 closes.
same-GUID/portal/reconnect isolation, and policy-fault quarantine are joined
by the visible-terminal Windows and native Linux/WSL production gates.
Direct launch, four-stop portal routing, external `teleallto`, retail-client
observer movement, graceful logout, and the corrected normal-position versus
ForcePosition routing pass. Final gates report 412 Runtime, 47 Headless,
3,722 App / 3 skips, and 8,764 complete Release tests / 5 skips. K4
1/5/10/30-session resource-ceiling and stress work is active.
Slice-I closeout evidence is
[`../research/2026-07-25-slice-i7-closeout.md`](../research/2026-07-25-slice-i7-closeout.md).
Slice-J2 closeout evidence is