test(app): add canonical connected soak snapshots

Make scripted lifecycle checkpoints acknowledged post-diagnostics render barriers, capture the exact frame outcome beside canonical resource ownership, and harden the nine-stop route with ordered same-location cache and lifetime gates without weakening process residency thresholds.

Co-authored-by: Codex <codex@openai.com>
This commit is contained in:
Erik 2026-07-22 20:01:06 +02:00
parent 2862622ba2
commit bca4148739
17 changed files with 995 additions and 52 deletions

View file

@ -137,13 +137,16 @@ Every checkpoint hard-gates zero:
- composite warmup work.
The same-location Caul return → Caul plateau comparison requires exact equality
for deterministic owner/cache counts and bytes: loaded/visible/total landblocks,
materialized live owners, teardown/retirement queues, VFX binding/owner/script/
light counts, mesh render-data/atlas/estimated bytes, staged work, tracked GPU
bytes/buffers/textures, and composite/particle texture ownership. Connected
`WorldEntities`, `AnimatedEntities`, `LiveEntities`, particles, and active
scripts may legitimately change with authoritative population or transient
effects; those deltas remain named workload warnings, not silent exclusions.
for deterministic cache/allocator state: loaded/visible/total landblocks,
teardown/retirement queues, mesh render-data/atlas/estimated bytes, staged work,
tracked GPU bytes/buffers/textures, and composite/particle texture ownership.
Connected `WorldEntities`, `AnimatedEntities`, `LiveEntities`, and materialized
live entities may legitimately change with authoritative population; those
deltas are named workload warnings. VFX binding/owner/script/light counts remain
hard equality gates when that population is stable, and become named workload
warnings when the authoritative population changed. Particles, emitters, and
active scripts are always transient workload warnings rather than silent
exclusions.
Managed used/committed deltas are reported diagnostically. Existing
working/private-memory, update-p95, and allocation-p50 thresholds remain byte-
for-byte unchanged as the secondary residency/performance guard.