docs(headless): record K4 resource envelope

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
+K4 implementation is complete through `776482da`. `cb512fd0` added one
-`cb512fd0` checkpoint adds one process-scheduler observation deadline,
+process-scheduler observation deadline and corrected pre-connect deadline
-structured CPU/private/resident/managed/GC/thread/handle/Linux-descriptor/
+arming plus a Linux sub-millisecond `Task.Delay` busy loop. `97c174fb` added
-socket/session/content/ownership/wakeup/lateness metrics, and exact
+1/5/10/30-root content, same-GUID, portal, reconnect, and two-hour simulated
-post-disposal convergence without per-session workers or timers. The first
+endurance gates; `bd236ce5` added death and randomized cancellation coverage;
-native Linux two-account run exposed and corrected pre-connect deadline arming
+`776482da` committed the diagnostic-only 30-session resource envelope and
-and a sub-millisecond `Task.Delay` busy loop. Windows and native Ubuntu
+exact running/terminal ownership checks. Windows and native Ubuntu Headless
-Headless tests pass 56/56; the complete Release suite passes 8,773 / 5 skips.
+tests pass 67/67; the complete Release suite passes 8,784 / 5 skips. The exact
-The user requested that the current two-client observer process remain
+`776482da` native Linux two-account process is currently running at Rynthid:
-running; exact-fixed-binary resource ceilings and automated 5/10/30-root
+both sessions are in-world with zero faults, bounded scheduler cadence, and
-endurance remain.
+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

CLAUDE.md

@@ -374,17 +374,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
+K4 implementation is complete through `776482da`. `cb512fd0` added one
-`cb512fd0` checkpoint adds one process-scheduler observation deadline,
+process-scheduler observation deadline and corrected pre-connect deadline
-structured CPU/private/resident/managed/GC/thread/handle/Linux-descriptor/
+arming plus a Linux sub-millisecond `Task.Delay` busy loop. `97c174fb` added
-socket/session/content/ownership/wakeup/lateness metrics, and exact
+1/5/10/30-root content, same-GUID, portal, reconnect, and two-hour simulated
-post-disposal convergence without per-session workers or timers. The first
+endurance gates; `bd236ce5` added death and randomized cancellation coverage;
-native Linux two-account run exposed and corrected pre-connect deadline arming
+`776482da` committed the diagnostic-only 30-session resource envelope and
-and a sub-millisecond `Task.Delay` busy loop. Windows and native Ubuntu
+exact running/terminal ownership checks. Windows and native Ubuntu Headless
-Headless tests pass 56/56; the complete Release suite passes 8,773 / 5 skips.
+tests pass 67/67; the complete Release suite passes 8,784 / 5 skips. The exact
-The user requested that the current two-client observer process remain
+`776482da` native Linux two-account process is currently running at Rynthid:
-running; exact-fixed-binary resource ceilings and automated 5/10/30-root
+both sessions are in-world with zero faults, bounded scheduler cadence, and
-endurance remain.
+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
@@ -451,7 +453,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

docs/plans/2026-04-11-roadmap.md

@@ -1,6 +1,6 @@
 # acdream — strategic roadmap
 
-**Status:** Living document. Updated 2026-07-27. **M3 landed; M4 is active.** M3's retail casting/UI, R6 locomotion/collision/projectile/teleport/radar rebaseline, deterministic fresh-login/portal world lifecycle, and final two-client portal observer flow are user-gated. All eight slices of the behavior-preserving ownership campaign in [`docs/architecture/code-structure.md`](../architecture/code-structure.md), their automated closeout, and the user's connected visual matrix are complete. Modern Runtime J3 canonical entity/object lifetime and J4 gameplay-state ownership are closed at `89e6b207`; J5.1 canonical selection/combat/target-mode ownership is closed at `b298f99f`, J5.2 interaction transactions at `f5f7b417`, J5.3 combat/magic intent at `20df9d15`, J5.4 local movement/outbound cadence at `aa3f4a60`, J5.5 per-session physics/remote simulation at `7e6033d0`, J5.6 projectile simulation at `2aee3356`, and J5.7 combined simulation closeout at `cdee7a4b`. J6.1 world-environment ownership is closed at `902076c0`; J6.2 canonical reveal generation and typed destination readiness is closed at `a6860d55` plus `acb845d8`; J6.3 exact F751/Position destination correlation is closed at `6a063a27`; J6.4 exact graphical-host acknowledgement and owner cleanup is closed at `18d17d8b`. J7's one graphical `GameRuntime` root is closed at `ce41efb9`, including the user's 2026-07-27 exact post-cutover visual acceptance. J8 closed Slice J at `a9a822f2` with one shared graphical/no-window root and generation-reset transaction. Slice K Linux headless/multi-session work is active; K0's tested no-presentation Windows/Linux boundary closed at `aada8a37`, K1's real portable single-session host closed at `f8cb840f`, and K2's deterministic scheduler plus complete shared bot command/event path closed at `7e8acb74` plus `38e83640`. K3 closed at `3f340125` after the shared-content/collision/isolation checkpoint, visible-terminal Windows and native Linux production runs, four-stop portal route, external-teleport handling, and user-accepted retail-observer movement. K4 resource and stability work is active; `cb512fd0` adds process-level CPU/memory/GC/descriptor/ownership/scheduler telemetry and corrects both pre-connect deadline arming and the Linux sub-millisecond scheduler busy loop. Issue #225's lifestone/particle alpha comparison remains a separate rendering visual gate.
+**Status:** Living document. Updated 2026-07-27. **M3 landed; M4 is active.** M3's retail casting/UI, R6 locomotion/collision/projectile/teleport/radar rebaseline, deterministic fresh-login/portal world lifecycle, and final two-client portal observer flow are user-gated. All eight slices of the behavior-preserving ownership campaign in [`docs/architecture/code-structure.md`](../architecture/code-structure.md), their automated closeout, and the user's connected visual matrix are complete. Modern Runtime J3 canonical entity/object lifetime and J4 gameplay-state ownership are closed at `89e6b207`; J5.1 canonical selection/combat/target-mode ownership is closed at `b298f99f`, J5.2 interaction transactions at `f5f7b417`, J5.3 combat/magic intent at `20df9d15`, J5.4 local movement/outbound cadence at `aa3f4a60`, J5.5 per-session physics/remote simulation at `7e6033d0`, J5.6 projectile simulation at `2aee3356`, and J5.7 combined simulation closeout at `cdee7a4b`. J6.1 world-environment ownership is closed at `902076c0`; J6.2 canonical reveal generation and typed destination readiness is closed at `a6860d55` plus `acb845d8`; J6.3 exact F751/Position destination correlation is closed at `6a063a27`; J6.4 exact graphical-host acknowledgement and owner cleanup is closed at `18d17d8b`. J7's one graphical `GameRuntime` root is closed at `ce41efb9`, including the user's 2026-07-27 exact post-cutover visual acceptance. J8 closed Slice J at `a9a822f2` with one shared graphical/no-window root and generation-reset transaction. Slice K Linux headless/multi-session work is active; K0's tested no-presentation Windows/Linux boundary closed at `aada8a37`, K1's real portable single-session host closed at `f8cb840f`, and K2's deterministic scheduler plus complete shared bot command/event path closed at `7e8acb74` plus `38e83640`. K3 closed at `3f340125` after the shared-content/collision/isolation checkpoint, visible-terminal Windows and native Linux production runs, four-stop portal route, external-teleport handling, and user-accepted retail-observer movement. K4 is implemented through `776482da`: resource telemetry/wait correction, 1/5/10/30-root isolation and two-hour simulated endurance, death/randomized cancellation, and a committed diagnostic-only resource/ownership envelope all pass. The exact `776482da` two-account Rynthid soak is active; graceful terminal convergence is the final Slice-K gate. Issue #225's lifestone/particle alpha comparison remains a separate rendering visual gate.
 **Purpose:** One source of truth for where the project is and where it's going. Every observed defect or missing feature has a named phase that owns it; when something looks wrong in-game, look here to find the phase that'll address it. Implementation details live in per-phase specs under `docs/superpowers/specs/`, not in this file.
 
 ---
@@ -1808,12 +1808,14 @@ port in any phase — no separate listing here.
 > event parity closed at `7e8acb74` plus `38e83640`; K3 closed at
 > `3f340125` after the shared-content/collision/isolation checkpoint, visible
 > Windows and native Linux production runs, exact portal routing, graceful
-> teardown, and user-accepted retail-observer movement. K4 is active;
+> teardown, and user-accepted retail-observer movement. K4 is implemented
-> `cb512fd0` adds one process-level resource/ownership sampling deadline,
+> through `776482da`: one process-level resource/ownership sampler, exact
-> exact scheduler lateness/wakeup accounting, terminal convergence reporting,
+> scheduler lateness/wakeup accounting, deadline/wait correction, 1/5/10/30
-> post-connect deadline rebasing, and the Linux sub-millisecond busy-wait
+> root isolation and two-hour simulated endurance, death/randomized
-> correction. Windows/native-Ubuntu Headless tests pass 56/56 and the complete
+> cancellation, and a committed numeric envelope. Windows/native-Ubuntu
-> Release suite passes 8,773 / 5 skips.
+> Headless tests pass 67/67 and the complete Release suite passes 8,784 / 5
+> skips. The exact two-account connected soak is active; graceful terminal
+> convergence remains.
 > The historical exact cutover
 > rollback remains
 > `git revert ef1d263337997bb030eadb7b8e71d73dc659907a`. Slice H is complete:
@@ -1860,9 +1862,11 @@ hitch and follows.
 > no-window Linux host and approximately 30-session target from
 > [`2026-07-26-modern-runtime-slice-k.md`](2026-07-26-modern-runtime-slice-k.md);
 > Slice L executes the graphical Linux/platform work. K0-K3 are complete and
-> K4 is active. Its telemetry/CPU checkpoint is `cb512fd0`; exact fixed-binary
+> K4 is implemented through `776482da`. Its automated 1/5/10/30-root
-> connected baselines and automated 5/10/30-root endurance gates remain. The
+> isolation, two-hour simulated endurance, death/cancellation, and committed
-> historical LH rows below remain the stable outcome map.
+> resource-envelope gates pass; the exact two-account connected process is
+> running inside the envelope and only its graceful terminal convergence
+> remains. The historical LH rows below remain the stable outcome map.
 
 The governing architectural rule is that a game session must not be a hidden
 `GameWindow`. Authentication, networking, world state, movement, inventory,

docs/plans/2026-05-12-milestones.md

@@ -303,16 +303,17 @@ residency is `0/0/0` at every stable checkpoint and teardown converges. Slice I
   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
+  3,722 App / 3 skips, and 8,764 complete Release tests / 5 skips. K4 is
-  1/5/10/30-session resource-ceiling and stress work is active. Its
+  implemented through `776482da`: process-level resource telemetry and the
-  `cb512fd0` telemetry checkpoint adds one process-level sampling deadline,
+  deadline/wait correction (`cb512fd0`), 1/5/10/30-root content/isolation/
-  structured CPU/memory/GC/thread/descriptor/socket/ownership/content/
+  portal/reconnect plus two-hour simulated endurance (`97c174fb`), death and
-  scheduler metrics, exact terminal convergence, post-connect deadline
+  randomized cancellation (`bd236ce5`), and committed diagnostic-only
-  rebasing, and the Linux sub-millisecond busy-wait correction without adding
+  per-process/per-session ceilings with exact running/terminal ownership
-  per-session workers or timers. Windows and native Ubuntu Headless tests pass
+  checks (`776482da`). Windows and native Ubuntu Headless tests pass 67/67 and
-  56/56 and the complete Release suite passes 8,773 tests / 5 skips. The
+  the complete Release suite passes 8,784 tests / 5 skips. The exact
-  exact-fixed-binary one/two-account baseline and automated 5/10/30-root
+  `776482da` two-account Rynthid soak is active with zero faults and every
-  endurance gates remain.
+  sampled resource dimension inside its ceiling; graceful terminal
+  convergence remains the final Slice-K closeout gate.
 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

docs/plans/2026-07-26-modern-runtime-slice-k.md

@@ -1,6 +1,7 @@
 # Modern runtime Slice K — Linux headless and multi-session host
 
-**Status:** K0–K3 COMPLETE; K4 ACTIVE 2026-07-27
+**Status:** K0–K3 COMPLETE; K4 IMPLEMENTED, CONNECTED TERMINAL GATE ACTIVE
+2026-07-27
 **Parent:** `2026-07-24-modern-runtime-architecture.md`, Slice K
 **Authorization:** the user approved Slices F–L on 2026-07-24
 **Purpose:** run efficient automated clients on Linux without a display, GPU,
@@ -341,16 +342,37 @@ disposes only after the final host acknowledgement.
 
 ### K4 — 30-session stress and closeout
 
-K4 telemetry checkpoint `cb512fd0` is complete. One process-level
+K4 implementation is complete through `776482da`. One process-level
-absolute-deadline sampler now reports CPU, private/resident/managed memory,
+absolute-deadline sampler reports CPU, private/resident/managed memory, GC,
-GC, threads, handles, Linux descriptors/sockets, session/ownership debt,
+threads, handles, Linux descriptors/sockets, session/ownership debt,
 shared-content leases, scheduler wakeups, and deadline lateness without adding
 per-session workers or timers. The first native Linux two-account run exposed
 and corrected both pre-connect deadline arming and a sub-millisecond
-`Task.Delay` busy loop. Windows and native Ubuntu Headless tests pass 56/56;
+`Task.Delay` busy loop.
-the complete Release suite passes 8,773 tests / 5 skips. The user requested
+
-that the active two-client observer process remain running, so the exact fixed-
+The automated 1/5/10/30-root gate opens one exact process-content owner,
-binary connected baseline and numeric ceilings remain next. Evidence:
+isolates equal GUIDs, portal/reconnect generations, mutable Runtime/physics
+state, and policy faults, and converges every root and content lease. Its
+30-root workload advances 480,000 frames per root (two simulated hours),
+14.4 million turns total, with recurring movement, use, combat, casting, chat,
+portal, death, and reconnect. Five additional 30-root runs cancel at
+randomized connect/entry/activity/portal/reconnect/teardown edges.
+
+The committed `k4-linux-30-session` envelope is diagnostic-only. It scales
+private/resident memory, managed live/heap memory, CPU, handles, descriptors,
+and sockets by configured session count while bounding threads, scheduler
+wakeups/catch-ups, and deadline lateness process-wide. It names every
+violation and requires exact Runtime/content convergence in the final
+`disposed` sample; it never changes simulation, networking, scheduling, or
+teardown.
+
+Windows and native Ubuntu Headless tests pass 67/67; the complete Release
+suite passes 8,784 tests / 5 skips. The exact `776482da` native Linux process
+has both available accounts in-world at Rynthid, zero faults/reconnect debt,
+bounded wakeups and CPU, and every sampled dimension inside the committed
+ceiling. The user requested that it remain running for observation; its
+graceful `disposed` sample is the sole remaining K4/Slice-K closeout gate.
+Evidence:
 `docs/research/2026-07-27-slice-k4-resource-telemetry-checkpoint.md`.
 
 - Measure a 1-session warm baseline, then 5, 10, and 30 sessions.
@@ -443,3 +465,12 @@ git revert b6547ff38c375328417855200f41c8af6436f246
 git revert 9569dadb578b299b24e30aec85eee86ec0c2b3fb
 git revert 12b500d38362e8aae0a23a4f9712b86367006f76
 ```
+
+K4 rollback, newest first:
+
+```text
+git revert 776482da8225d88a7c6128022d137d26f9266a87
+git revert bd236ce553718cfb1248703f4a2b17b35733b11c
+git revert 97c174fbb2d72fb94e2fe07448bb257989ed8941
+git revert cb512fd0916fbf49285c9b64df1630c5a69a0d20
+```

docs/research/2026-07-27-slice-k4-resource-telemetry-checkpoint.md

@@ -1,13 +1,13 @@
 # Slice K4 resource telemetry checkpoint
 
 **Date:** 2026-07-27
-**Status:** Instrumentation and CPU-wakeup correction complete; fixed-binary
+**Status:** Implementation and automated gates complete; exact connected
-connected baselines remain active
+terminal gate active
-**Production commit:** `cb512fd0`
+**Production commits:** `cb512fd0`, `97c174fb`, `bd236ce5`, `776482da`
 
 ## Outcome
 
-The Linux headless process now emits one structured resource sample at
+The Linux headless process emits one structured resource sample at
 startup, every 30 seconds, before scheduler stop, and after terminal disposal.
 Sampling is driven by the existing process scheduler's absolute deadline. It
 does not add a worker, timer, or callback per session.
@@ -36,7 +36,8 @@ One native Linux process connected the two locally available accounts:
 - `testaccount2` / `+Horan`
 
 Both entered Rynthid and maintained independent Runtime roots and movement.
-The user asked that this process stay running for the retail-observer gate.
+The user asked that the current exact `776482da` process stay running for the
+retail-observer gate.
 
 The first process sample after both world entries reported:
 
@@ -55,12 +56,20 @@ The first process sample after both world entries reported:
 The roughly 29.9 GB mapped-package value is address space, not resident or
 private memory. The mmap remains shared and demand-paged.
 
-After movement and additional portal/density activity, the latest recorded
+The earlier fixed scheduler artifact ran for roughly 16 minutes and plateaued
-sample before this checkpoint reported 305,393,664 private bytes, 332,742,656
+near 311.8 MiB private / 303.8 MiB resident while entity count rose to roughly
-working-set bytes, 139,609,360 managed live bytes, 418 entities, 16 threads,
+600. Its steady combined two-bot CPU was 2.3–3.2% of one core, scheduler mean
-117 handles, and the same three socket descriptors. Entity count changed from
+lateness was about 3.3 ms, and it retained 15–17 threads, 115 handles, 116
-187 to 418 during that interval, so the memory delta is not treated as a
+Linux descriptors, and three sockets. It recorded no session fault or
-same-workload per-session ceiling.
+reconnect debt. That process ended without a terminal sample, so it is soak
+evidence rather than the closeout teardown gate.
+
+The current exact `776482da` process entered Rynthid with both accounts and
+reported four consecutive passing samples in its first 90 seconds. After
+initial hydration, combined CPU was 2.5–2.9% of one core, waits were
+89–96/second, turns were 133/second, continuing catch-ups were zero, mean
+lateness was about 3.1 ms, and maximum lateness was 145.1 ms. It had zero
+faulted or reconnecting sessions and exactly two Runtime/content leases.
 
 ## Scheduler finding and correction
 
@@ -86,30 +95,77 @@ its high wait counter belongs to the pre-correction artifact. The committed
 correction is protected by deterministic rebase/lateness tests and a real
 system-timer test that fails if the scheduler busy-loops between turns.
 
-## Automated gates
+## Committed resource envelope
 
-- Windows Headless Release: 56 passed.
+`776482da` commits the `k4-linux-30-session` numeric profile. For `N`
-- Native Ubuntu Headless Release: 56 passed.
+configured sessions, the principal ceilings are:
-- Complete Windows Release suite: 8,773 passed / 5 skipped.
+
+| Dimension | Ceiling |
+|---|---:|
+| private bytes | 224 MiB shared + 64 MiB/session |
+| working set | 224 MiB shared + 64 MiB/session |
+| managed live bytes | 64 MiB shared + 48 MiB/session |
+| managed heap | 64 MiB shared + 48 MiB/session |
+| CPU | 2% of one core shared + 3%/session |
+| threads | 48 process-wide |
+| handles | 128 shared + 3/session |
+| Linux descriptors | 128 shared + 3/session |
+| sockets | 1 shared + 2/session |
+| scheduler waits | 250/second process-wide |
+| scheduler catch-ups | 1/second process-wide |
+| mean/max lateness | 10/750 ms |
+
+The evaluator fails closed on non-finite metrics, reports named violations,
+requires exact running lease/session accounting, and requires all Runtime
+roots plus shared content to converge in the `disposed` sample. It is
+observational only.
+
+## Automated endurance and adversarial gates
+
+- Content sharing and same-GUID/portal/reconnect isolation run at 1, 5, 10,
+  and 30 roots.
+- The 30-root workload advances 480,000 frames per root: two simulated hours
+  and 14.4 million stable-order scheduler turns.
+- Every root performs recurring movement, use, combat, spell, chat, portal,
+  death, and reconnect activity.
+- Whole-process allocation stays below 384 KiB/second and retained growth
+  stays below 16 MiB in the deterministic endurance fixture.
+- Five 30-root process runs inject randomized cancellation across lifecycle
+  edges and converge every Runtime root and shared-content lease.
+- The resource evaluator covers a passing recorded Rynthid sample, every
+  individually named resource/ownership debt, terminal success/failure, and
+  non-finite metrics.
+
+- Windows Headless Release: 67 passed.
+- Native Ubuntu Headless Release: 67 passed.
+- Runtime Release: 412 passed.
+- App Release: 3,722 passed / 3 skipped.
+- Complete Windows Release suite: 8,784 passed / 5 skipped.
 - Windows and native Ubuntu Release builds complete.
-- Diagnostics assert two configured sessions, no password text, and exact
+- Diagnostics assert no credential text and exact 1/5/10/30-root terminal
-  two-runtime terminal convergence.
+  convergence.
 
 ## Remaining K4 gate
 
-The next connected restart must use exact binary `cb512fd0` or a documented
+The exact `776482da` two-account process is running under the committed
-descendant and prove the wait counter remains cadence-bounded, initial
+envelope. After the observer window it must receive graceful cancellation and
-catch-up remains zero, CPU falls accordingly, and terminal resource samples
+emit a final `disposed` sample with:
-converge. Available credentials support a two-account connected scale gate.
-The 5/10/30-session isolation and endurance dimensions therefore remain
-automated in-process gates unless additional local ACE accounts are
-provisioned.
 
-Numeric ceilings are not yet committed: they will be derived only from the
+- two converged Runtime roots;
-fixed binary under matched 1- and 2-session workloads.
+- zero in-world/reconnecting/faulted sessions;
+- zero entities, inventory objects, and host leases;
+- zero shared-content leases with content disposed/converged;
+- `withinCeilings=true`.
+
+Only then does Slice K close. Available credentials support two simultaneous
+connected accounts; 5/10/30-session scale and two-hour duration are therefore
+proved by the deterministic in-process production-owner fixtures.
 
 ## Rollback
 
 ```text
-git revert cb512fd0
+git revert 776482da8225d88a7c6128022d137d26f9266a87
+git revert bd236ce553718cfb1248703f4a2b17b35733b11c
+git revert 97c174fbb2d72fb94e2fe07448bb257989ed8941
+git revert cb512fd0916fbf49285c9b64df1630c5a69a0d20
 ```

memory/project_modern_runtime_headless.md

@@ -2,17 +2,24 @@
 
 ## Current checkpoint
 
-Slice J is closed. Slice K0-K3 are closed; K4 is active.
+Slice J is closed. Slice K0-K3 are closed; K4 implementation is complete
+through `776482da`, with the exact connected terminal gate active.
 
 K3's production closeout commit is `3f340125`. Its automated predecessors are
 `12b500d3`, `9569dadb`, and `b6547ff3`.
 
-K4's resource-telemetry/CPU checkpoint is `cb512fd0`. It adds one
+K4 commits after the telemetry/CPU checkpoint are:
-process-scheduler observation deadline, structured process/managed/session/
+
-content/scheduler metrics, exact post-disposal convergence reporting, startup
+- `97c174fb`: 1/5/10/30-root content sharing, same-GUID isolation, portal,
-deadline rebasing, and the Linux sub-millisecond busy-wait correction. It does
+  reconnect, and 480,000-frame-per-root two-hour simulated endurance;
-not add per-session timers or workers. Windows and native Ubuntu Headless
+- `bd236ce5`: death during the endurance route plus five randomized
-tests pass 56/56; the complete Release suite passes 8,773 / 5 skips.
+  30-session cancellation-edge runs;
+- `776482da`: committed diagnostic-only 30-session resource ceilings,
+  per-sample evaluation, named failures, 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 Windows visible-terminal host and native Linux/WSL host both connected to
 local ACE without loading presentation assemblies. Linux completed the
@@ -54,17 +61,16 @@ continues to use credential providers.
 
 ## Next work
 
-Execute K4 from `docs/plans/2026-07-26-modern-runtime-slice-k.md`:
+Finish K4 from `docs/plans/2026-07-26-modern-runtime-slice-k.md`:
 
-1. after the user finishes observing the current two clients, restart on exact
+1. keep the exact `776482da` two-account Rynthid process running while the user
-   `cb512fd0` or a documented descendant;
+   observes it;
-2. prove cadence-bounded wait count, zero startup catch-up, reduced CPU, and
+2. verify every periodic sample remains inside the committed envelope with no
-   exact teardown convergence under matched one- and two-account workloads;
+   fault/reconnect/lease debt;
-3. derive and commit numeric per-session/process ceilings;
+3. stop it gracefully and require a final `disposed` sample with two converged
-4. run automated 5/10/30-root stress and endurance gates; the connected scale
+   Runtime roots, zero entities/inventory/host leases, disposed shared
-   gate is presently limited to the two available local ACE accounts;
+   content, and `withinCeilings=true`;
-5. prove stable plateaus and exact teardown convergence;
+4. close Slice K and begin Slice L Linux graphical/platform work.
-6. close Slice K, then start Slice L Linux graphical/platform work.
 
 Final K3 automated counts: Runtime 412, Headless 47, App 3,722 / 3 skips,
 complete Release 8,764 / 5 skips.
@@ -75,8 +81,11 @@ K3 connected-closeout rollback:
 git revert 3f3401257c83bdd9f557eb577ba08cf2e5ec9a06
 ```
 
-K4 telemetry/CPU rollback:
+K4 rollbacks, newest first:
 
 ```text
+git revert 776482da8225d88a7c6128022d137d26f9266a87
+git revert bd236ce553718cfb1248703f4a2b17b35733b11c
+git revert 97c174fbb2d72fb94e2fe07448bb257989ed8941
 git revert cb512fd0
 ```