docs(headless): record K3 isolation checkpoint
This commit is contained in:
parent
b6547ff38c
commit
fd9559a063
6 changed files with 114 additions and 10 deletions
|
|
@ -294,8 +294,14 @@ 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 shared
|
||||
immutable process content and per-session mutable isolation are active.
|
||||
App / 3 skips, and 8,744 complete Release tests / 5 skips. K3's automated
|
||||
checkpoint landed across `12b500d3`, `9569dadb`, and `b6547ff3`: 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.
|
||||
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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue