MW3 current buffered runtime — 2026-11-07
The installed GetDeviceData observer and ordinary top-row 5 input passed
local composed qualification with production browser guest/render Workers.
The published fece02eca desktop GL completeness repair was incorporated and
preserved. The single authorized fresh box then stopped at upload PUT HTTP
502, before runtime launch. No original menu, cockpit poll, movement, turn or
fire was observed in this attempt. This establishes a staging blocker, not an
emulator or game-input defect.
Evidence: scratch/runs/20261107-mw3-current-buffered/. Work began after
mw3-buffered-original released at 16:37:24Z. Its note and the bb2a58205
keyboard-path note were read first. Preparation SHA in source.json is
cd98b939d97f6e115bad35e1d2b38876dfdb023d. No production source was edited
by this worker.
Current runtime and installed observation
The retained 308-file manifest was checked against the checkout. Its only
changed file was lib/gl-compat.js, from retained SHA-256
b007377dd11a736b3eeb36f8191597b9657323900fe4698f0c489779b8a6380b to
2b1f2dc28b08e318e65c95bc4e2df94f4ce31dadb53f3dd84bb12d3067313c32.
retained-drift.json records the comparison; incorporated-gl-repair.patch
preserves commit fece02eca5b8cb41aacc46d8c2d98482524b0689. No unrelated
functional drift was silently adopted. Its texture-completeness behavior
remained intact: test-gl-texture-environment-web.js passed all 38 WebGL1/2
pixel checks, including undefined images, mip completeness and texture units.
An initial invocation omitted the required evidence-directory argument; that
usage error is retained separately from the passing run.
The locked build passed with WINE_WAT_NAMES=1. The canonical module remained
2,182,493 bytes, SHA-256
e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467.
The named build was used only to identify the actual function: canonical and
named code bodies were compared byte-for-byte, and the retained GetDeviceState
body provided a second calibration. The executing GetDeviceData function is
index 5962, definition 5668, body [888196,889324), first instruction
888199, successful keyboard-return instruction 888442. Source-order
function indexing alone was not used to install observation.
The run-specific observer.cjs uses CDP-recovered executing module bytes,
verifies their complete module hash and exact function body, and requires both
exact executable breakpoint locations. A false-returning entry condition saves
the real request count and stack arguments; a false-returning completion
condition pairs the request with the stack after its 24-byte adjustment and
calls bb2a58205's tools/mw3-keyboard-completion.js decoder. Normal results
retain request/count, HRESULT, device, format/acquired flags, pointers, caller
and returned records. Normal caller 0x4f76c8 is distinguished from startup
flush 0x4f73fd, drain 0x4f7ae0 and other callers. Non-normal calls have
separate raw request/completion metadata and cannot qualify a normal pulse.
Observation is bounded, detects drops/pairing errors, and removes both
breakpoints and its diagnostic globals on stop. It writes no guest memory.
The retained browser/input/admission controls were recovered into the owned
run directory. Their full 18-field owner/module/epoch identity and 120-second
freshness checks remain unchanged. The current manifest pins 310 inputs;
recursive literal Node dependencies plus the driver's dynamic runtime roots
qualified 66 files. That static closure check first detected an omitted optional
startup-proof.cjs; the retained helper was recovered and pinned, then the
check passed. Its optional startup-proof branch was not executed. Manifest
membership was checked in addition to file hashes.
Local composed qualification
local3/ ran the exact pinned driver/observer with the production guest and
render Workers and CDP-recovered module. The generated public-COM fixture
acquired a standard 256-object keyboard format with buffer capacity 128 and
called vtable slot 10 with stride 16, flags 0 and request 128. Its generated
x86 CALL really returned to 0x4f76c8. The fixture's PE bootstrap base was
adjusted to 0x400000 before loading the generated fixture; no original MW3
EXE, original guest memory, binding, setting or clock was altered. Two earlier
fixture attempts placed that CALL below the bootstrap image base and exited
through an unexpected host exit; their failure logs are preserved. Neither
attempt ran the original game or sent input.
The observer captured 2,445 successful normal completions with no diagnostic errors or drops. Empty polls preceded input. One ordinary trusted CDP Digit5 DOWN/UP pair used VK 53, with independent UP armed before DOWN. Both ACKs arrived; UP was attempted exactly 150 ms after arming. Consumed records were DIK 6, data 128, sequence 1, timestamp 66014, then DIK 6, data 0, sequence 2, timestamp 66158. The decoder's ordered consuming pair requirement passed. This proves fixture consumption, not original MW3 consumption or gameplay.
qualify.cjs additionally passed module/body/location and Worker-owner
refusals, every one of the 18 identity-field mutations, nine request/result/
format negatives, distinct flush/drain classification, zero-effect expired
scene refusal, and UNKNOWN DOWN with independently attempted UP. Observer
restoration and normal Chromium exit were checked. Accepted native input,
motion-envelope and documented bindings controls were reused; no earlier
UNKNOWN original pulse was replayed. Existing focused regressions passed:
buffered MW3 OS Worker path, buffered keyboard --rpc, and independent Worker
acquire. local-qualification.json, closure-qualification.json and test logs
retain the results. No emulator mismatch or repair is claimed.
Fresh box: first unresolved boundary and custody
Normal shutdown was explicitly delegated in shutdown-delegation.json.
Separate normal-stop and immutable 1,500-second watchdog OS processes were
armed and checked alive before the UUID-idempotent allocation. The single box
was bx_9c57f4aq, created at 16:49:16Z, initially expiring at
17:49:16.682Z; its independent cap was 17:14:16.853Z.
The complete pinned input set passed local pre-upload checks. The individual
file uploader then received HTTP 502 Bad Gateway on the upload URL's PUT.
The upload-URL API call had succeeded; the signed URL and credentials were not
logged. provision.log retains the stack. This is a file-transfer failure,
not a CDP/input UNKNOWN. Nevertheless, the attempt stopped at this unresolved
boundary with no upload replay, new box, runtime boot or original input.
The uploader did not annotate the exception with a file path; that precise
failed object remains unknown. Its completion ledger was empty because the
first completed future raised before successful peers were drained.
A read-only remote inventory recovered the actual partial stage: seven files,
the canonical WASM plus six font/license files. All seven sizes and hashes
matched their recorded inputs. The repaired GL file, driver and full closure
had not reached the box, so the remote stage was not qualified as runnable.
No Node/Chrome runtime process, runtime output, port, profile or held input had
been created there. There were zero unique remote output artifacts to download;
the inventory and command results were recovered locally before requesting
normal stop. retrieval-verified.json records that distinction.
Normal stop stop_9e9f30300c7a1886 completed at 16:50:10.008Z,
forced:false; final state is archived, archiveAfter:null, retained-data
expiry unknown. The watchdog was alive before and after normal stop and both
lifecycle processes exited normally. All three local browser attempts exited
with code 0 and their ports, profiles, writer locks and processes were checked
closed. The local input pair left no held key. Free disk sampled above 2 GB.
Recovery uses the recorded Git SHA, relevant-tracked.patch,
relevant-new-source.patch, owned-helper-source.patch, runtime manifest and
the unique CDP module in local3/; no source-tree archive was made. Thirty-six
existing media/system-data paths were hash-checked in place and referenced,
never copied into evidence. Verified duplicate module captures from the two
failed fixture attempts were removed only after matching the retained unique
module; module-custody.json records this. The global evidence checker still
reports unrelated Alice and Tunnel/Twist containment errors. MW3 has no corpus
candidate, so this run uses investigation metadata without attaching an
unrelated candidate.
The next task needs separately authorized original execution after resolving the upload-service boundary. Retain this qualified buffered observer, record each upload's path/outcome, and qualify the complete remote stage before boot. Native menu/default setup/Launch/cockpit review, passive original normal polls, a fresh consumed Digit5 pair with visible speed/displacement/terrain change, and documented Left Arrow/Space gameplay remain undone. This worker allocated no second box and retains no runtime or lifecycle ownership.