Forsaken current native D3DIM: prelaunch provider blocker, 2026-11-14

The fresh original was not launched. Current native-provider preflight failed its drawing-buffer resize/readback assertion. There is no current Forsaken scene, living traversal, identified enemy, aimed projectile/ammunition/hit consequence, or actual native Quit/Exit result. White-scene recurrence is unknown. The 900-second original and independent 920-second watchdog were prepared but never started; no second original or runtime extension occurred. Full27 remains unproved.

Evidence: scratch/runs/20261114-forsaken-native-d3d-gameplay/. Start with result-early.json, preflight-wait.json, native-preflight.log, build-reuse-check.json, postflight.json, and cleanup.json. There are no selected original PNGs: the failure preceded original execution.

Current identity and preflight

The exact 317-file accepted closure and current standard module matched under the heavy-runtime lock, with zero drift. Module SHA256 is dcf6e8f0ca9d361c10fa556fb30835d34cf5bfe4089f84d298cb57fd170dbd42. The accepted locked full build is scratch/runs/20261114-supertux-wall-time-consequence/build.log; no replacement build was necessary. Prequeue HEAD was 545d22c4f31f6885f7437204409c53160c6103f9. source-pins.json records postblock HEAD and an unchanged-closure recheck; source.patch and new-runtime.patch preserve relevant foreign WIP without editing it. Git remains the source archive. No source tree, media, wasm dump, frame series, or evidence bundle was copied into this run.

The registered forsaken_demo route, original manifest, original executable, all manifest media, and standing DLL directory were pinned. The manifest has 871 entries; its SHA256 is 587ce145ab73a3fed2c7136425bb6a7bcf28def312d430c8bf7d1be802b2260b. The original executable is 366ec5d0943daca839836296f9fb52724e94dc155630c6b0c30d7181106b5e24. All 894 pinned input paths match afterward. Media remains at its existing paths. No config, physics, AI, health, guest clock, guest function, blend, texture, depth, gamma, or renderer state was forced.

The private provider was restored from the existing Q3 package and lock using npm ci --offline --prefix <run>/native-deps --no-audit --no-fund. Both lock hashes and all 162 provider pins passed before and after preflight; root node_modules was untouched and no network installation was used. Actual lib/headless-gl.js provider imports succeeded in the test and produced an actual context identifying llvmpipe (LLVM 20.1.2, 256 bits), WebGL 1.0, GLSL 4.50. This is software GL through the native provider, not evidence of a physical GPU. It does not establish a current Forsaken D3DIM owner/readback or its exclusion of emulator SoftwareGL: the original never ran. actual-createRequire-resolution.json separately verifies both packages resolve from createRequire(lib/headless-gl.js) into this private installation. That read-only check created no context and launched no original. The prepared game observer was not executed.

At test/test-headless-gl.js:168, after resizing the canvas width from32 to64, the far-right blue byte was 0, expected 255: right edge stale: drawing buffer was not resized. The process exited1. Earlier assertions reached that point, including native shader draws, alpha, row orientation, compositing and PNG encoding. This identifies the failing test boundary, not its cause, repeatability, or a Forsaken white-scene defect. No speculative patch, test bypass, or native-control retry was made.

Tests and control preparation

Ten current focused scripts passed: CLI input ownership, guarded CLI input, control-server progress, main/thread bootstrap cleanup, thread-exit callback cleanup, D3DIM native16 default, GPU presentation, passive target inspection, and readback stop lifecycle. The last has15 passing tests. The complete native GL test failed as described above; it is not counted as a pass.

The new run-local controller passed eight final tests using the actual production HTTP transport and guarded-input implementation: delayed150ms delivery with a finite60ms pulse, independent release and subsequent progress; dropped ACK with sticky UNKNOWN/no replay; mouse input; immutable deadline cancellation/fallback; stale capture; stale review; one-use image; and native target identity binding. Four supervision controls and the actual outer-wait control passed. These are fixture results, not native gameplay.

Commands were prepared for ordinary Single Player/Normal/VOLCANO/menu controls, real ticks and default1000 batches. Each prospective action required personally reviewed full-scene bytes, capture-to-submit and review age at most30 seconds, a one-use image and matching process/window lease. Press duration40–1000ms was separate from the six-second operation deadline, with an independently prearmed release child. A final native Quit choice would await actual guest exit. None of these controls was exercised on Forsaken.

Queue, lifecycle, and remaining work

The heavy turn followed queued SuperTux and LMarbles6. This supervisor acquired /tmp/wine-heavy-runtime.lock at14:16:12.530 UTC, verified the closure, and stopped on preflight failure at14:16:28.967 UTC. Preflight actual wait1 has separate stdout/stderr EOF. The supervisor returned0 after recording the preflight blocker; its actual outer-child wait and the invoking exec session88455 also returned0 with separate EOF. Supervisor exit0 does not promote preflight1. Its descriptors closed on exit and the next queued worker acquired the heavy lock. There was no original native child or original watchdog to join; those results are missing, not successful shutdowns or native Quit.

Box ID none, state NOT_CREATED, expiry null, stop receipt N/A. No box, deployment, other worker, or foreign WIP was touched. Disk remained above1.5GB. Private provider installation is reproducible from the retained package/lock and offline cache; only this run's installed provider directory was removed after final162-pin verification.

The next dependency is qualifying the current native-provider resize/readback boundary under the heavy lock, then a separately authorized fresh original check. The earlier unsaturated whitening witness still matches actual sampling and native565 arithmetic without proving a renderer defect. It supplies no substitute current-game result. No renderer patch follows from this prelaunch failure.