docs(runtime): record world environment ownership

This commit is contained in:
Erik 2026-07-26 16:52:43 +02:00
parent 902076c0a4
commit 4ab98b080e
7 changed files with 119 additions and 9 deletions

View file

@ -1,6 +1,6 @@
# Modern runtime Slice J6 — world, transit, and host handshake
**Status:** J6.0 ACTIVE
**Status:** J6.0J6.1 COMPLETE; J6.2 ACTIVE
**Parent:** `2026-07-25-modern-runtime-slice-j.md`, J6
**Authorization:** the user approved Slices FL, including gameplay-owner
moves, on 2026-07-24
@ -194,6 +194,8 @@ planned owner and no accepted presentation edge changes.
### J6.1 — instance-scoped environment owner
**Complete 2026-07-26 at `902076c0`.**
- Add `DerethCalendar` and make `WorldTimeService` consume its exact instance.
- Add `RuntimeWorldEnvironmentState` and immutable environment definitions.
- Reduce App's `WorldEnvironmentController` to DAT conversion plus
@ -207,6 +209,16 @@ planned owner and no accepted presentation edge changes.
Gate: Core/Runtime/App focused tests, Release build, full tests, exact
day-group fixtures, and no Runtime dependency violation.
Result: Runtime now owns the one instance-scoped calendar, synchronized world
clock, weather state, selected day group, AdminEnvirons state, and debug
overrides. App only translates immutable DAT sky definitions and projects the
selected Runtime state into the renderer. The 332 Runtime tests, 3,718 App
tests / 3 skips, 8,611 complete Release tests / 5 skips, and exact-binary
connected lifecycle/reconnect route pass. Both connected clients used
`902076c0a42079596a8a273e9be402776cabf4b0`, completed all seven checkpoints,
and exited gracefully with code zero. Evidence:
[`../research/2026-07-26-slice-j6-1-environment-ownership.md`](../research/2026-07-26-slice-j6-1-environment-ownership.md).
### J6.2 — canonical reveal generation and typed readiness
- Add `RuntimeWorldTransitState`, immutable readiness acknowledgement, and
@ -306,6 +318,12 @@ Release, full-suite, dependency, and teardown gates. The exact production
commit and matching `git revert <sha>` are recorded here, in the parent plan,
the closeout evidence, architecture, and durable memory before moving on.
J6.1 exact rollback:
```text
git revert 902076c0a42079596a8a273e9be402776cabf4b0
```
Documentation-only research/plan commits are not behavior rollback points.
No workaround, timer, forced-ready path, duplicated owner, or alternate
headless behavior is permitted.