Remaining Tunnel, Twist and Boids Worker configurations, 7 November 2026
This attempt fills zero of the four configuration gaps from f6c0a8392.
The first original software Tunnel Worker launched, then a CDP serialization
error stopped the harness before its first capture. WebGL Tunnel, Twist and
Boids Workers were not launched. No emulator defect or fix is established.
The current-frustum worker completed no overlapping Worker configuration;
its cooperative Boids observer failure remains separate evidence.
Evidence is in scratch/runs/20261107-graphics-remaining-worker-configs/.
Local qualification and its exposed limit
The staged transport actually executed locally in Chromium. Positive numbered
key/combo requests were atomically published, consumed, delivered as trusted
native events, and acknowledged with exact IDs. Independent release completed
before slow diagnostics. UNKNOWN, partial delivery, late/wrong ACK, stale
capture, owner/module replacement and sticky closure controls passed with
reason-specific assertions. All staged imports resolved; an intentionally
missing import had to fail with MODULE_NOT_FOUND. Three native-input tests
and the owning D3DIM trace regression passed. An initial command used nonexistent
test paths and failed; the corrected test command and output are retained.
The exact driver prefix passed deadline checks and missing/corrupt controls for every one of its 620 pinned inputs. The actual driver ran through cold native key/type/combo checks and its registered selection boundary locally, with zero original launches, including a final execution after refreshing shared-source pins. Hold durations and independent release guards were unchanged.
A separate generated x86 public-COM fixture exercised production
GuestWorkerLink, RenderWorker.Manager, guest Worker and render Worker.
The owning guest's instance.exports.get_image_base() returned 0x01000000;
guest_to_wasm(base) returned 73728 and a read-only copy found the MZ header.
The production guest has no moduleMap variable. The fixture installed the
existing bounded raw trace on the actual owning render endpoint, observed
completed natural submissions and passed independent pixel expectations.
No cooperative-only observer or guessed executable-name lookup was reused.
The raw trace is not a complete scene/frustum oracle. Its test fixture uses
ordinary public COM Lock synchronization; no diagnostic fence was added to an
original. Both generated fixture images were inspected.
Two preparation errors precede that successful production qualification: custom fixture responses initially lacked isolation headers; the next attempt looked for the render Worker before its first draw created it. All attempts are retained. The successful fixture waits after a natural first EndScene.
These checks did not exercise the complete original-launch branch of the actual driver against production objects. That missing coverage invalidates the complete-driver admission prerequisite requested for this task. The prelaunch fixture and separate production observer checks must not be reported as full driver qualification.
First remote blocker
One UUID-idempotent fresh box, bx_8ptdehqn, was allocated at
10:18:38 UTC, with a 35-minute inclusive deadline of 10:53:38 UTC.
Cold native key/type/combo/partial-delivery checks passed before original
selection; there was no raised bound, input replay or guest configuration,
camera, clock or media edit. The ordinary registered dx_tunnel software route
launched at 10:18:52.379 UTC with the host Worker setting enabled.
At 10:18:53.468 UTC the driver received:
Error: {"code":-32000,"message":"Object reference chain is too long"}
The first readiness loop evaluates
runningApps.find(a => a.name === selectedApp)?.wine?.guestWorker with
returnByValue:true. This returns the production controller object rather than
a boolean, asking CDP to serialize its reference graph. The exception occurs
before capture('scene-15'), owning endpoint receipts or passive geometry
installation. The retained console confirms guest Worker slot 0 instantiated
the module and patched 1,807 thunks. It does not establish the actual endpoint
identity, completed draws, active backend/provider, motion or scene visibility.
There are no original compositor captures and no reviewed original motion or
crash result. This is a harness error, not a rendering-loss observation.
The driver closed Chrome normally at 10:18:54.492 UTC and did not relaunch the original or proceed to another configuration. A successor must make the readiness expression return a scalar boolean and execute that exact driver branch against a generated production Worker before allocating another box. The failed script is retained unchanged after the remote failure.
Identity, retrieval and custody
The tested runtime source is main
b1c02256aff03a072b3702c8a40a0f3b22192e9d plus
relevant-source.patch, untracked-inputs.patch and owned-inputs.patch.
All 315 checked source inputs reconstruct from Git plus those patches. All
40 unique files in the three registered original manifests matched the prior
original pins. All 620 staged pins matched before launch and at terminal
inspection. Git is the source archive; no source/media archive was created.
Only the small helpers and individually pinned runtime inputs were staged.
The CDP-recovered live module is the 2,182,493-byte standard module,
SHA-256 e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467.
The recovered staged compatibility module is 2,185,139 bytes,
SHA-256 04acbb89f66ad9814836b5e2c34de659b518f4e1994f50c4ee8069c991f02f72;
it is not identified as live. This task did not rebuild modules and does not
assert the runtime-source commit as their compilation commit. Earlier graphics
notes retain build provenance. No production code changed in this task.
The environment was Node 24.22.1 and Chrome 151.0.7922.108 through
BetterChromium. Its launcher forces ANGLE SwiftShader; /dev/dri is absent.
Native inner geometry was 1024×712, outer geometry 1024×855, with no emulated
viewport. No actual owning rendering-context provider receipt was obtained.
All 26 remote artifact paths, representing 25 unique files and 4,457,173 bytes,
including both modules, were retrieved and SHA-256 verified before the delegated
normal nonforced shutdown. Both controller/Chrome PIDs were absent; both
HTTP/DevTools ports refused connections; profile, profile processes, writer
locks and command files were clear; the original native-input recorder was
empty. Chrome exited zero. Local /home stayed above 2 GB at recorded guards.
The box is confirmed archived at 10:20:05.045 UTC, expiry null; its stop
operation completed with forced:false. Custody returns to the coordinator
with no active runtime. Do not resume this box. All four named configuration
gaps remain open. No FPS, audio, parity, broad crash freedom, historical27
membership or full-corpus completion follows from this attempt.