Nox native staff action attempt, 2026-11-09

Run 20261109-nox-native-staff-action-1900 stopped during its sole native fixture, before Nox selection. No pickup, equipment, hit, defeat or onward consequence was verified. The existing browser startup bound expired without chrome-profile/DevToolsActivePort; the consumer recorded ENOENT at 19:02:56.284 UTC. This is a concrete browser-startup blocker, not a reproduced Nox defect. No causal repair is claimed.

Chrome stderr later contains a DevTools listening address, but this does not reopen the failed admission or establish why startup exceeded the bound. The existing 100 × 100 ms startup polling, input guards and deadlines were unchanged. There was no later input, capture, retry or original session. The first-failure handler closed the consumer; Chrome ultimately exited by SIGKILL at 19:03:10.923 UTC. Normal browser close was not achieved.

Preparation and exact inputs

The assigned 1750 and 1855 notes and repository instructions were read. The November 8 pickup image was separately reviewed: Jack northwest of the staff, native PICK UP / Force of Nature Staff of Recharge, and equipment change are the relevant visual criteria. The 1750 floor staff alone proves neither pickup nor equipment. Original default.cfg confirms left pickup / Action, right movement, I inventory and V swap. Network/Host/Conjurer/Bunker remains the prepared route; Solo and King are unavailable in the demo.

Final inspection and generation occurred after Q3 1856's published f68f79a28a888f47800d1de5276249421b7d494f RELEASE STOP. Its final note and allocation-record search independently confirmed no predecessor allocation; there was no predecessor box requiring an API stop query. The exact inspected Git base is that same commit. Compared with the 1750 closure, only the three published c6094c4ed GL providers differ. Their actual source diff and bytes were reviewed: armed glGetError stages cover context lookup, flush, frontend error read/clear and backend query. This Nox run did not arm diagnostics.

The write-once plan contains 776 inputs and 45 changed/added identities relative to the historical consumer, including both recompiled modules. All 126 original media identities and the accepted historical consumer are unchanged. Primary module SHA-256 is 3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18; compat is ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf. There was no repin after native admission. Terminal verification matched all 832 staged input files. Git SHA plus relevant small patches is the source recovery record; no source-tree or media archive was made.

Three production tests at the correct path node --test ops/browser-native-input.test.cjs passed. All ten generated consumer checks passed, including source/module/media/historical tampering, blind-repin refusal, ordinary boundary, balanced drag and first-error shutdown without a later capture. These used an offline peer, not local Chrome. The copied independent lifecycle watchdog passed its offline fake-API actual wait and separate EOF test. Actual copied request and phase entrypoints rejected both terminal markers and the exact disk floor before dispatch. flock /tmp/wine-build.lock bash tools/build.sh passed and was joined with exit zero. Routine offline read-only path errors were preserved and corrected.

Evidence and final lifecycle

The only box was bx_4bzv5zxa, UUID da9f0999-019e-49a5-9b3a-f9e1e1cd8612. Its observable independent watchdog was armed before allocation at 19:02:18.241 UTC, with immutable deadline 19:27:18.241 UTC. Initial box expiry (archiveAfter) was 19:27:18.633 UTC. No local Chrome, nested workers, second box, resume, delete or public deployment was used.

The native parent returned 1 with separate stdout/stderr EOF. Kernel custody completed with 128 reaps, no remaining or unreaped tasks and command-log EOF. The owning parent, custodian, consumer and Chrome were independently absent; HTTP port 46515 and DevTools port 39819 were closed, and the profile was gone. No original directory or runtime gameplay screenshot exists. Offline peer sentinel files named PNG are not actual captures.

All 25 remote artifact references were retrieved or matched to existing local bytes, SHA-256/size verified, and independently reread before stop. Every gzip stream was decompressed for CRC verification; there were no runtime PNGs. The sole delegated unforced stop was stop_218e6c0d31c478ef, completed at 19:04:10.340 UTC. A separate API GET confirmed archived, completed and forced: false, with archiveAfter: null; expiresAt was not returned. The real watchdog terminated STOP_CONFIRMED; its supervisor actually waited for exit 0 with separate stdout/stderr EOF and child-reaped confirmation.

Evidence is retained under the assigned run directory. The global evidence checker returned existing historical errors; this task's result references are checked separately. Free space on /home remained above 6 GB. No production code changed. Next work requires a separately assigned investigation of this Chrome startup boundary under the unchanged guards before another original staff attempt. This task releases its owned files and stops with the objective incomplete.