Nox current-browser target attempt, 2026-11-09
Run 20261109-nox-current-native-target-1750 reached the original Bunker and
staff alcove using the published current-input driver. No staff pickup,
hit, defeat or objective consequence was verified. At 18:17:25 UTC the
shared /home filesystem had 1,488,084,992 bytes free, below the owner's
1,500,000,000-byte floor. That observation ended gameplay. Later disk recovery
did not reopen admission. No later gameplay input, capture or retry occurred.
The native Solo and King of the Realm selections explicitly displayed
“Not Available In Demo.” An attempted Capture the Flag selection left Arena
unchanged; its availability is not established. Ordinary Network/Host flag
placement, Conjurer/default Jack, Chat Area dismissal and Bunker/Arena GO
worked. Right-button movement traversed the northwest corridor and wooden
doorway into the blue-flame room. The green floor staff was visible beside
Jack, but the final hover captures did not identify it with a native pickup
label. Equipment and target effects must not be inferred from those images.
There were 34 successful numbered ACKs, commands 0–33; command 33,
staff-floor-hover, is the final capture. Menu animation misses, cursor
corrections and the ineffective Enter on customization are retained.
Exact current consumer and gates
The accepted historical consumer remains unchanged at SHA-256
72b2eead63b36ef53fb5e3e1457536eaf1b94d1d0792eb425a3419f6a39c0705.
The final write-once plan and generated directory were created only after
Q3's published release. Q3 box bx_7de5kh4r was independently confirmed
archived with completed unforced stop stop_92a6058ee1659620 and expiry null.
No reconstruction of failed historical ReturnFire joins was required.
tools/nox-current-driver.cjs inspect/generate accepted exact HEAD
afbe245cbe8271bf4a6260b1361c3b12d9a00772: 776 inputs, 44 changed/added
identities, exact patches, and all 126 unchanged original media identities.
Both current modules were freshly compiled. Primary/live module SHA-256 is
3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18;
compat is ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf.
The embedded plan guard was unchanged. A separate preparation-only generation
had correctly refused stale HEAD 769aefe44 → d829d3545; that failed plan
was retained, never repinned or reused for runtime.
All ten actual generated-consumer cases passed, including source/module/media/ historical tampering and blind-repin refusal before startup, ordinary boundary, balanced drag/release and first-error shutdown without a later capture. These tests used an offline CDP peer, not local Chrome. Three production native-input tests, the locked build, offline watchdog actual-wait/EOF test and actual request entrypoint terminal-marker refusals passed. One remote native preflight then passed its final no-original-selection boundary: Chrome exit 0, parent wait 0, both EOFs and complete kernel drain with 151 reaps. Exactly one original guest session followed. Terminal verification matched all 831 staged input files.
Original Chrome was 151.0.7922.108, V8 15.1.206.16. The actual page renderer was
Win98Renderer / CanvasRenderingContext2D, guest endpoint 1, slot 0; the
640×480 canvas had native page rectangle 945×855 at top 34. No owning D3D
render Worker was present. The WebGL selector does not establish GL rendering.
Terminal evidence and lifecycle
The sole box was bx_2as4ut9t, UUID
77caa711-0f20-4c7f-aa71-9e4f3b5f4ddb. An observable independent watchdog was
armed before allocation at 18:06:51.379 UTC with immutable deadline
18:31:51.379 UTC. Initial box expiry was 18:31:54.346 UTC. No agents, other
boxes, local Chrome, resume, delete, guest-state edits or public deployment
were used.
After the disk failure, SIGTERM to the owning kernel custodian performed cleanup without gameplay input or capture. The original parent waited with return code 1 and both EOFs; kernel exit was −15 with cancellation recorded. Kernel drain completed with 358 reaps, no remaining/unreaped tasks, controller and Chrome absent, and both ports closed. Normal browser close is unknown. The stale owned profile was removed only after those absence checks.
All 435 remote artifact references were retrieved or matched to existing local bytes, SHA-256/size verified and independently reread before normal stop. Every gzip stream was decompressed for CRC validation. Lossless same-byte deduplication preserves evidence paths; two reproducible offline peer module copies were replaced by canonical-module identity/recovery records. Git plus exact small patches is the source archive; no source/media archive was made. The previously released, regenerated disposable plugin catalog cache was claimed and cleared with a SHA/size recovery record to permit retrieval. The original below-floor observation and the later recovered measurement are both retained; recovery does not erase the first failure.
Delegated unforced stop stop_baf1f82b2a185e8f completed at
18:20:04.864 UTC. Independent API verification confirms the box archived,
expiry null. The watchdog separately terminated STOP_CONFIRMED; its
supervisor actually waited for exit 0 and both stdout/stderr EOFs. These are
separate from browser cancellation, parent EOFs and kernel custody records.
No production code changed. Next work needs a separately assigned fresh target attempt with stable disk headroom and the same current-input guards. This task releases its files and stops.