Blood II armed native music watch, 2026-11-18
Evidence: scratch/runs/20261118-blood2-armed-native-watch-music-cause/.
The corrected published consumer successfully observes the actual IMRT25 constructor and first live state in a fresh registered original, PID 2457185. This replaces the preceding original's zero-armed missing boundary with real constructor/module/receiver evidence. It does not itself repair Blood II.
Exact preparation and actual first state
The cheap preflight reproduces the frozen source/index identities, 1,404 rows,
99 unchanged media pins, native module
21cbbb4ae9a08860007ea3e74799c8a42fc0c377d5f6c182f09b01dff26bbe80, and
corrected observer SHA-256
3648ee7086e249aef15f11c735564446593068aed076535745a31f4fb01af762.
The observer is byte-identical to published 888b66809; the native watch is
published 12ecbef77. Their authentic native Worker contracts, final Release,
destructor/free/invalidation, register/flags, unrelated-write and software-pixel
on/off controls and locked builds are reused, without redundant qualification.
The underlying graph remains Git 4808701de plus the recorded selective
variant and inherited Win16 blobs, explicitly distinct from current main.
The actual load_dll boundary arms the main instance before constructor
execution. The occupied native DLL rows identify IMRT25 base 0x00d41000
and IMUSIC25 base 0x00cd0000. At 04:09:59.821 UTC the real constructor
receives ECX 0x00c189ec, allocation header 208 and zero initial payload.
The first live witness follows at 04:09:59.835 with primary vtable
0x00d440f8, secondary vtables 0x00d440e0/0x00d440b8, and reference
count 1. Native shared configuration arms both music Worker instances before
their execution. Their pre-init arming rows still report export thread ID 1;
the subsequent real initialization logs establish actual guest IDs 2 and 3.
The earlier SoftSnd Worker predates module publication and has no armed row;
complete concurrent-writer coverage is not claimed.
The actual CreateThread entries are 0x00cd3706 and 0x00cd373d, both
with parameter 0x00c1907c. Authentic DLL disassembly shows stdcall thread
entries loading the stack parameter, placing it in ECX, calling the respective
thiscall engine methods, and returning with ret 4. A bounded live native
read establishes [0x00c1907c+4] == 0x00c189ec and the secondary interface
at +8. Guest-to-native translations are 0x0082a9ec for the real-time object
and 0x0082b07c for the engine. These are observed mappings in this run,
not addresses to copy into runtime code. Later samples show an intact primary
word and positive references. A rising sampled reference count does not
identify a leak, race, final Release or invalidating writer.
Visible game progress and guarded input
The first whole frame is black and authorizes no input. The later complete
BUILD 109 main menu is personally reviewed, followed by the Caleb character
menu and Homicide difficulty menu. Exactly three finite 90 ms Enter gestures
receive native CONSUMED receipts and independent physical-UP ACKs.
No fourth startup Enter is sent. The complete Center for Disease Management,
Demo Level 1 loading card is subsequently reviewed. The gameplay cutoff
passes while this card remains visible. At batch 91,554 / guest-ms 548,114,
the actual first-person world is captured: weapon, 100-health HUD, ammunition,
lit doorway, corridor and crates. A second selected world review shows the
doors further open. This establishes real rendered world progress. Movement,
fire and enemy effects remain unproved because gameplay admission had closed.
A run-local invocation initially attempted to save an already-existing review
file after binding; the exclusive file save rejected it before any pulse
intent or endpoint request. The first actual Enter used that existing fresh
review through the unchanged helper. There was no ambiguous input or replay.
The run-local monitor also adds the retained unexpected-eip=0 log spelling
to its conservative closure pattern; the old pattern misses the retained
fault and the new pattern detects it. This changes no guest/module/guard
behavior and supplies no music repair or reason to launch another original.
The original retains the finite 600-second native deadline, 180-second Quit reserve, independent disk watchdog, real ticks, normal guest Workers, software renderer, sealed main/Worker/media/boot paths and existing input identity/freshness/confirmation/UP controls. No fake reference, vtable repair, music disable, guest write, forced polling/clock or crash suppression is used.
Outcome and concrete blocker
No primary invalidation, reference zero, zero-Release branch, destructor, free, observation-loss or music-thread EIP-zero event is recorded. All four guest Workers remain active at shutdown. The final sampled reference count is 230 with intact vtables; it is sampled during the Quit reserve, not at process exit. This valid armed scope does not reproduce the earlier music NULL call and identifies no emulator cause. The watch disables chaining/uops on armed instances and can perturb scheduling; reaching world under it is not an oldfail/newpass repair proof or timing-equivalence claim. The earlier unarmed original and other closed scopes remain closed.
The guarded ordinary-Quit Escape attempt closes UNKNOWN. Its native input trace progresses through handler return and DELIVERY_PENDING, then cancels at the immutable input deadline without a native consumption receipt. The next recorded renderer/native USER poll occurs after cancellation. The client times out; its prearmed independent release fires but its reply also times out and is UNKNOWN, not ACK. A later native key-up log is not a successful down-consumption or ordinary-Quit receipt. No additional endpoint requests follow closure, except that already-armed release. No input replay, later endpoint inspection or additional original is attempted.
There is a review-order limitation on this last attempt: the preceding whole
world image was personally inspected before dispatch, but the refreshed
quit-ready.png was inspected after dispatch. The refreshed image therefore
does not establish compliant personal pixel review before this Quit attempt.
Its later inspection cannot repair that ordering or qualify ordinary Quit.
Owned host cancellation produces native exit 0 after 588.361 seconds and
93,430 batches. This is not ordinary game Quit. Actual native and independent
watchdog waits have both EOFs, empty drain errors and exit 0; native-supervise
reports leaked:false. Owned processes are nonlive and the control port is
absent. The watchdog minimum free disk is 1,521,405,952 bytes, above the
1.5 GB floor; no RAM gate is used. Main/Worker/boot/renderer source reads,
all 99 unchanged media pins and the exact retained module are verified.
Only this report is committed. No runtime repair is supported, so no speculative runtime change or additional original is made. Evidence retains exact Git, relevant diffs/owned new-file patches, retained-module/media recovery recipes, bounded logs and selected named whole-frame PNGs. There are no source archives, media copies, frame series, workers, agents, boxes, Python, Wine or deployment. Box ID null, state NOT_CREATED, expiry null, stop receipt null. The final run result is written last, then ownership is released and this task stops.