docs(headless): record K4 resource envelope
This commit is contained in:
parent
776482da82
commit
b2ab0956f2
7 changed files with 208 additions and 97 deletions
29
AGENTS.md
29
AGENTS.md
|
|
@ -376,17 +376,19 @@ ForcePosition projection, explicit-only collision diagnostics, visible Windows
|
|||
and native Linux production runs, user-accepted smooth retail-observer
|
||||
movement, and ACE-confirmed graceful logout. Final gates pass 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. Its
|
||||
`cb512fd0` checkpoint adds one process-scheduler observation deadline,
|
||||
structured CPU/private/resident/managed/GC/thread/handle/Linux-descriptor/
|
||||
socket/session/content/ownership/wakeup/lateness metrics, and exact
|
||||
post-disposal convergence without per-session workers or timers. The first
|
||||
native Linux two-account run exposed and corrected pre-connect deadline arming
|
||||
and a sub-millisecond `Task.Delay` busy loop. Windows and native Ubuntu
|
||||
Headless tests pass 56/56; the complete Release suite passes 8,773 / 5 skips.
|
||||
The user requested that the current two-client observer process remain
|
||||
running; exact-fixed-binary resource ceilings and automated 5/10/30-root
|
||||
endurance remain.
|
||||
K4 implementation is complete through `776482da`. `cb512fd0` added one
|
||||
process-scheduler observation deadline and corrected pre-connect deadline
|
||||
arming plus a Linux sub-millisecond `Task.Delay` busy loop. `97c174fb` added
|
||||
1/5/10/30-root content, same-GUID, portal, reconnect, and two-hour simulated
|
||||
endurance gates; `bd236ce5` added death and randomized cancellation coverage;
|
||||
`776482da` committed the diagnostic-only 30-session resource envelope and
|
||||
exact running/terminal ownership checks. Windows and native Ubuntu Headless
|
||||
tests pass 67/67; the complete Release suite passes 8,784 / 5 skips. The exact
|
||||
`776482da` native Linux two-account process is currently running at Rynthid:
|
||||
both sessions are in-world with zero faults, bounded scheduler cadence, and
|
||||
every sampled CPU/memory/thread/descriptor/socket/lateness dimension within
|
||||
the committed ceiling. Its graceful terminal convergence remains the final
|
||||
K4/Slice-K closeout gate.
|
||||
J0's rollback is
|
||||
`git revert b632672e5ccabfb44c551e08f1c411ab2669c44a`.
|
||||
J1's rollback is
|
||||
|
|
@ -453,7 +455,10 @@ K2's rollback is, newest first,
|
|||
K3's connected-closeout rollback is
|
||||
`git revert 3f3401257c83bdd9f557eb577ba08cf2e5ec9a06`; its earlier automated
|
||||
checkpoint rollbacks remain recorded in the Slice K plan.
|
||||
K4's resource-telemetry/CPU rollback is
|
||||
K4's current rollbacks, newest first, are
|
||||
`git revert 776482da8225d88a7c6128022d137d26f9266a87`,
|
||||
`git revert bd236ce553718cfb1248703f4a2b17b35733b11c`,
|
||||
`git revert 97c174fbb2d72fb94e2fe07448bb257989ed8941`, then
|
||||
`git revert cb512fd0916fbf49285c9b64df1630c5a69a0d20`.
|
||||
Slice H's retained UI/frame, bounded-light, and pooled/borrowed/direct network
|
||||
work is complete; the exact seven-checkpoint connected lifecycle/reconnect gate
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue