Blood II corrected lifetime observation, 2026-11-18
Evidence: scratch/runs/20261118-blood2-corrected-lifetime-world-cause/.
This task uses the owner's newly authorized single original after correction
215dc7b8f. The earlier original's UNKNOWN scope remains closed. No prior
runtime endpoint was reused, and the correction is an observer repair rather
than an emulator behavior repair.
The corrected handoff passed on the actual registered recipe. Native PID
2338631 constructed IMRT's real object at 0x00c189ec, with allocation header
208. The actual DLL table identifies IMUSIC25 at 0x00cd0000 and IMRT25 at
0x00d41000. The late audio Worker's Node host thread 6, native exported thread
5, successfully inherited that pointer through .dat at 03:06:15.847 UTC.
Its initial primary/secondary words were 0x00d440f8, 0x00d440e0, and
0x00d440b8, with reference count 2. The old unsealed-JSON rejection did not
recur. Native threads 3 and 4 independently observed the same real object at
their interface entries; launcher Worker labels are a separate numbering.
Exact preparation and retained proofs
The sealed graph is unchanged: published 4808701dec187469a900bef81d668e10067f2a76,
1,404 rows, 99 media pins, source hash
f804ccd3c1a2d4cf077c39ba8fa56d88ff16b66d0d12afc16a00b54c36fe6c4e,
index hash 44545c5af3faf15fd5ec1d18ef293b606cd10d5c1a5d3dd78facea569591779a,
and module hash 7d347a6a631ab77335a14935a533feb896be71aa2508fc5aa19b1e5df8f096ce.
The unique module stays at its existing recovery path; media are not copied.
FoxBear owns current preparation/loader changes. This task leaves those files
untouched. Optional canonical-identity metadata is omitted from the run's
collected rows before asserting byte-for-byte equality with the exact old
inventory/index/source. A small run-owned bootstrap recovers the already
qualified source loader directly from Git 215dc7b8f in memory, without a
source snapshot. Every native guest Worker inherits that loader, the same
sealed descriptors and corrected explicit observer preload. The durable
launcher's current receipt-only addition records its child's start token;
its exact hash and unapplied diff are retained. No runtime graph substitution
or source-admission relaxation is used.
Read-only native main/Worker registry and all-media preflights passed, as did renderer/whole-PNG/normal guest-Worker preparation. Direct descriptor hashes match before and after launching. Required source reads are verified against the inventory, including actual original main and guest Workers, registry, filesystem, process boot, renderer, PNG codec and actual module. Media and module hashes are rechecked after cleanup.
The unchanged observer SHA-256 is
fa9d1d7a5edf3dfcb61c93baf0c2a7217dfa53f31bc22d3693bf2e3e3d290c2b.
The preceding actual native authentic IMRT/IMUSIC constructor/QI/transfer and
final Release on/off, normal guest-Worker/software whole-pixel on/off,
sealed-JSON old rejection/DAT new pass, focused tests and locked build proofs
are reused with their readback hashes. No redundant qualification/build was
run. These controls establish their contract/pixel outcomes; they do not
establish full engine behavior or scheduling equivalence.
Scope and interpretation
The route is the registered BUILD109 native Node CLI, normal guest Workers, real ticks and supported software D3DIM. The observer remains unchanged and passive: existing native block/import boundaries and getters, no guest writes, forced polling, fake references, music disabling or crash suppression. Limits remain 600 seconds, 16,000 rows and 20,000,000 boundaries per Node thread, with finite object bounds and cancellation on an observation UNKNOWN. Tracing disables optimized dispatch; elapsed time and thread interleavings here are not evidence of normal timing. Object differences are interval observations, not identification of the exact writer.
Complete original frames reviewed during startup are black. Native batches advance, but no menu, loading card or world has been visually established. No owner was bound and no Enter, movement, fire or Quit gesture was sent. The first-three-Enter route remains unused; a black frame authorizes none of those actions. Identity/freshness/confirmation/independent-UP/operation guards and the immutable Quit reserve are unchanged.
Measured blocker and terminal cleanup
At 03:11:16.010 UTC, Node host thread 4 reached its 16,000-row limit after
52,708 observed boundaries. It emitted UNKNOWN:row-bound and requested
owned cancellation. The scope closed permanently. No later endpoint request,
replay, additional original or postclosure capture was attempted. The last
read-only capture completed over a minute before closure. Five manually
requested snapshot/whole-PNG pairs made ten read-only endpoint requests;
their byte-identical black PNGs were reduced to one selected named image.
The complete image was personally reviewed. It establishes no visible menu,
loading card, world or game control consequence.
The original retained 35,485 observer records, including 6,071 real Release
entries and 6,071 corresponding nonzero-return boundary observations. Native
Release callers are 0x00d2ee99, 0x00d2eeb6, 0x00d2eed4, 0x00cd2ef4,
0x00cd2be7, 0x00d14bdc, and 0x00d14bf8. The recorded return-count register
values are 2, 3 and 4. There is no observed zero branch, object destructor,
allocator free whose argument is this object, or primary-word invalidation.
Allocator wrappers also service unrelated allocations: their presence alone
is not an object-free proof. No earlier worker-termination/NULL-call sequence
is reproduced before this bound. None of these observations identifies an
invalidating writer or establishes that the object cannot fail later.
The concrete blocker is exhaustion of the bounded trace before a visible menu and before the first invalidating write/final Release/free. The native host reports 922,797 API calls and 5,019 batches in 322.418 seconds. These are this traced run's measurements; no untraced-original comparison, emulator speed claim or normal-scheduling conclusion is drawn. No relevant emulator defect was proved, no COM/runtime behavior was changed, and no speculative repair or second affected original followed. Movement, fire, enemy consequence and ordinary Quit remain unproved.
Native and independent finite/disk-watchdog actual waits are zero, both stdout
and stderr EOFs are true, drain errors are empty, and native-supervise reports
leaked:false. Exit zero follows owned host cancellation, not ordinary game
Quit. Eight known owned process IDs are nonlive and port 35951 has no listener.
The watchdog's minimum free /home space was 2,012,172,288 bytes; no RAM gate
was used. The invoking launch tool returned zero. The earlier board watcher
returned actual wait 143/SIGTERM; its signal origin is unknown and no foreign
watcher was stopped.
Final readback verifies 525 sealed reads, the required main/Worker/render
coverage, every one of the unchanged 99 media pins and the retained module.
Evidence records Git, the relevant unapplied binary diff, owned new-file/helper
patches, reused proof hashes, native lifetime/module/caller/thread observations,
selected whole PNG, actual waits and cleanup. Run-local audit corrections
addressed exclusive-write filenames and the final zero-sample trace-cost
footer; neither is an original failure or emulator defect. There is no source
archive, frame series, capture bundle or media copy. result.json is published
last, with unknown cause and failed goal explicit.
No agents, Codex workers, boxes, Python, Wine, deployment or held investigation were used. Box ID null, state NOT_CREATED, expiry null, stop receipt null. Only this report is committed; ownership is released and the single task stops.