docs: hand off placement campaign finish

This commit is contained in:
Erik 2026-08-03 12:54:47 +02:00
parent 175ad6b0d0
commit 205f3fea6f
8 changed files with 441 additions and 176 deletions

View file

@ -4547,3 +4547,41 @@ _entities.AdvanceCreateAuthority in the executor, inside
ApplyWeenieDescriptionAction; registration advance still residence-gated).
Focused files 82/82; Runtime 1,003/1,003; App 4,039/3 skips of 4,042;
git diff --check exit 0. No staging/commits.
## 2026-08-03 stabilization checkpoint and handoff
Five separately bisectable root-cause fixes followed the O1/O2/O3 checkpoint:
1. `01f4791e` — pending-only live projection buckets no longer manufacture a
second origin-recenter retirement receipt. Complete Release, lifecycle,
and canonical nine-stop soak passed on this binary; the soak had nine
checkpoints, zero failures, zero wait cues, and zero pending retirements.
2. `670f307c` — Runtime converts remote Create frames through the accepted
local-player world center and publishes the local physics body's world
position. The user accepted monster/static placement, chase, and attacks.
3. `1fc529cd` — distant Use materializes the canonical minimal static physics
host before MoveTo, and presentation attach reconciles the pre-PartArray
startup motion suffix. The user accepted near and distant object use.
4. `f24532ad` — exact-incarnation effect packets wait for canonical
presentation binding; projectile and static-animation sidecars retry on the
committed visibility edge; effect cells follow rebuckets. The user accepted
buffs, recalls, arrows, combat spell projectiles, portals, and statics.
5. `175ad6b0` — LoginComplete is emitted from the local first-placement
terminal edge instead of raw PlayerCreate receipt. The user accepted login
materialization haze behavior.
Post-fix focused evidence: 90 App effect/projectile/static-scheduler tests,
two Runtime login tests, the exact live-entity cell tracking test, all 79
Headless tests, and a Release solution build with zero errors passed. The
complete suite and connected nine-stop soak were not rerun after the final
four stabilization commits. A broader selected fixture run exposed five
still-open `LiveEntityRuntimeTests` failures associated with the placement
cutover and one old remote-first-entry fixture that supplies an empty
collision source. These are campaign work, not evidence to weaken the new
production contracts.
Open campaign finish: classify/fix those six fixtures; finish placement routes
27 and delete legacy writers; resolve #276/#277 and portal-prefetch #280; run
the final-binary complete suite/lifecycle/nine-stop/two-client gates; perform
the #269 slope-glide visual check; retire AP-1/AD-1/AP-131/AD-60 only when the
legacy paths are gone; then land AP-22 and AD-10 and close the ledger.