Warcraft qualified-renderer attempt — 9 November 2026

The task did not reach Warcraft or Thrall control. The concrete blocker is the reused driver's ten-second Chrome startup wait under the actual kernel custodian. It expired before DevTools became available. The first failure stopped the attempt; there was no retry, subsequent input, second original, alternate backend, or renderer/emulator repair claim.

Evidence: scratch/runs/20261109-warcraft-qualified-renderer-gameplay-0224/. The exact Q20219 bx_vqksz83y ARCHIVED PHYSICAL_DRAINED board release at 02:28:37Z preceded allocation. Preparation used no local browser, heavy execution, peer box, or agents.

Prepared identity and actual failure

The canonical startup barrier verified 627 identical local/remote providers and 161,558,770 bytes. Source reference: df0932c1ce88ea67ddc164946ea2ad51cc06b157; the manifest, relevant binary diff, new boot-file patch, accepted helper hashes and small run inputs retain recovery without source/media/module archives. All twelve existing Warcraft media paths were hashed; the four historical EXE/Game.dll/Storm.dll/MPQ hashes match the Warcraft notes. No media was copied into evidence or reinstalled.

The prepared main module hashes to a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295. It was pinned and fetched for HTTP verification, not executed by Warcraft. The run composition uses the published 0efee3bf16 production renderer-identity helper with the accepted exact-owner/native-CDP/numbered-ACK driver. Its intended guard retains the eight-second/four-MiB qualification caps and ends tracing before gameplay. The call observer was disabled; no high-volume journal or per-import probes ran. Added identity-check overhead was not measured.

The actual failure is retained in retrieved/original/first-browser-failure.json: at 02:30:05.917Z, the driver read DevToolsActivePort after its 100 × 100 ms wait and received ENOENT. Chrome stderr subsequently contains a DevTools listener on port 36999. That line is untimestamped, between timestamped lines at 02:30:09.778980Z and 02:30:14.525579Z; it cannot be assigned either exact time. This establishes late browser startup relative to this driver's wait, without establishing why startup was slow or blaming an emulator operation.

No WebSocket connection, Page.navigate, Warcraft launch, page/frame/PID qualification, game input, or native screenshot followed. Renderer linkage is UNKNOWN. The earlier fixture proof and later process absence supply no missing Warcraft identity. No normal-gameplay trace occurred.

Independent terminals and recovery

The unchanged kernel custodian retained 107/107 actual terminal waits and 994 raw custody events. terminal-validation.json checks each raw reap and its before-consumption witness against the drain receipt. Browser PID 6404, start ticks 18550, has actual kernel status 9 at 02:30:28.094585Z; Node's separate Chrome exit event follows at 02:30:28.226Z. This SIGKILL followed cleanup, not a demonstrated renderer fault. Driver PID 6390, start 18304, has kernel status 9 at 02:30:39.004209Z.

The independent parent observed the first failure and, after thirty seconds, sent SIGTERM to its exact custodian PID 6389, start 18296, at 02:30:36.073Z. Custodian cancellation killed the stuck remaining command and completed all recorded reaps. The parent actually waited status 1, with separate stdout/stderr EOF; local Boat-launch child PID 859829 also actually waited status 1 with both EOFs. Kernel command-log EOF is true. Chrome's stdout and stderr were regular files; separate pipe EOF was not observed for Chrome. Untraced clone flags, nonleader exec coverage and missing historical evidence remain UNKNOWN.

The prearchive census found recorded PIDs absent, HTTP 46533 closed, no profile FDs, and free input/runtime locks. DevTools-port closure was not independently checked before archive because the endpoint receipt was never created; that historical check remains UNKNOWN. Empty profile directories persisted, with no profile files in the exhaustive inventory. They were not silently described as removed, and the archived box was not resumed.

All 26 remote artifacts / 145,401 bytes were size/SHA-256 verified before delegated normal stop; compressed artifacts also passed decoded hashes and GNU gzip CRC. One empty stdout artifact was initially deduplicated against an open local watchdog log. After that local file finalized, the alias was corrected to a separately materialized, verified empty file. Both receipts remain; recovery-final-verified.json is the final mapping.

Lifecycle, validation and next work

UUID 172647e7-d71e-4ee5-93f4-f83e056e349a and its immutable 25-minute deadline were durably recorded before create. Watchdog PID 857648, start 223854223, armed at 02:28:53.036Z. Box bx_gsub82ym was created at 02:28:56.791Z, TTL 1496 seconds, initial expiry 02:53:52.805Z. Normal stop stop_a53f73f5db637ea6 completed at 02:31:10.220Z, forced=false, error=null. Final API state is archived, archiveAfter=null; expiresAt was not returned. The watchdog actually exited 0 with both EOFs and the local runtime lock was released. Physical runtime release was posted before publication. No box remains billing idle.

The 38 production helper/integration controls, harness contracts, composition syntax check, and browser-free driver preflight pass. No production file changed, so no new build or failing-before/passing-after repair is claimed; accepted unchanged build evidence belongs to the published renderer helper and current module providers. /home briefly dipped below 1.5 GB during offline preparation; the coordinator restored headroom before allocation. Runtime/recovery samples stayed above the floor. No RAM gate was applied.

Next work is to qualify browser startup and terminal-aware cleanup under this custodian before a separately authorized original. This attempt consumed no Warcraft input but cannot continue after its first failure. Thrall control and tutorial consequences remain unverified.