Redline joined fixture and side-door task — 2026-11-09
Evidence: scratch/runs/20261109-redline-joined-side-door-0756/.
The current tracked native fixture passed its whole lifecycle. Original Redline was not launched: an offline caller terminal-boundary defect was found before that step and repaired here. Vehicle entry and driving remain unverified. The repaired caller is not covered by the earlier frozen native proof; no further runtime or original retry is made in this task.
This task integrates the published 2cc66eccb shutdown repair into the actual
gameplay sequence. Native orchestration invokes the tracked
tools/redline-native-fixture.cjs and pins both that file and
tools/redline-fixture-shutdown.cjs. It does not launch the historical 0724
fixture copy. The ordinary fixture must pass its complete current lifecycle,
including separate actual waits and gzip EOF, before original Redline is
authorized. Historical startup/key partial success does not release that gate.
No deadline extension or cause for the historical Chrome latency is inferred.
The prepared closure uses tools/redline-browser-run.cjs,
tools/redline-startup.cjs, lib/redline-startup-admission.js, and host.js.
It preserves the private selected a320 CPU (2,185,596 bytes,
SHA-256 a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295),
actual owning Worker/module/instance/endpoint/slot and pre-CPU/pre-DLLmain
ordering. No shared host, custody, WAT, clock, scheduler, guest binding or
configuration change is made. Native lifetime remains REVOKED;
all-writer coverage and edict ABA remain UNKNOWN.
Offline startup composition passes the actual old/new caller regression and 15 refusal/retirement scenarios. The authored shutdown regression passes its nine inert child compositions and late-acquisition cancellation control; its historical comparison executes only in the offline CDP seam. This is not current native qualification. Accepted unchanged proofs are referenced by SHA/size, and eight underlying input/capture helper files match their accepted source pins. The 18-field identity, exact work ACK, sticky UNKNOWN, freshness, 5,000 ms hold bound and 24-count relative-input limits remain unchanged.
The shipped MAINDIR/Readme.rtf documents comma/period on-foot strafe and
vehicle entry by walking into a driver/passenger side door. The intended route
starts from fresh personally reviewed living pixels, clears the rear corner
laterally, identifies a side door, and requires changed vehicle HUD/camera
before bounded terrain-relative driving. The earlier blocked forward holds
are not repeated. First unexpected native UNKNOWN, failure or death terminates
input and capture; subsequent work is independent no-input cleanup only.
Runtime order is Quake II 0754 first, this task second, Q3 offline. Allocation requires Quake II's exact acquired UUID to be released ARCHIVED and PHYSICAL_DRAINED, or an explicit NOT_CREATED STOP. An observable independent UUID-bound 25-minute watchdog is required before the one finite-TTL create. Normal stop is delegated after retrieval and independent SHA/size/gzip CRC verification. Physical absence never substitutes for missing wait evidence.
Git is the source archive. The run records its exact Git base, small binary
closure patch and small run-input patch; media and modules use existing
path/hash references. No source tree or source/media/module archive is created.
Logs are gzip streams from their first byte. Free /home space must stay above
1.5 GB.
Current native result
The remote startup barrier verified all 735 providers (148,651,155 referenced
bytes) against the immutable prepared manifest. Tested Git base is
e55f0a03a9693c8a4ff36a02f56aa03c79699776; the existing relevant uncommitted
lib/wininit-boot.js patch is retained separately, without editing it.
The tracked fixture ran from the staged root under pre-exec kernel lineage
custody. Its actual owning Worker target was
EFA197E263F581D1BCFA1CC87AED7856, instance
c7f069e4-f301-41bd-a939-80c9d8c94719, endpoint 1, slot 0.
At the parked barrier, fixture EXE load, DLL load and CPU execution had not
started. The supported startup helper authenticated the private selected
module and actual live owning Worker before releasing ordinary fixture entry.
Comma and period each used a 600 ms independent-release hold. The guest's
native keyboard results include respectively six and five wholly held high
samples; subsequent reads are [0,0]. These are ordinary fixture results,
not original-game strafe or terrain displacement claims. Chrome exit 0,
controller exit 0, terminal-free cleanup, both Chrome gzip EOF joins and
all 180 owned identities' actual kernel reaps are recorded. Custody is
complete with no failure or cancellation. Its command log separately records
closed/EOF, and its decompressed journal SHA/size is verified. Physical absence
is checked separately. The whole-native gate is PASS for these tested bytes.
A local outer/inner evidence-label collision initially raised FileExistsError
before subprocess creation or remote execution. Its logs are retained under
offline-invocation-*; the corrected invocation launched the tracked fixture
once. No native fixture failure or native retry occurred.
Concrete blocker and caller fix
Before original launch, inspection found close() still calling
traceSnapshot('terminal') after first-browser-failure.json was written.
That executes guest reads after the first terminal error. In addition, an
already pending command could reach capture after close began. Running the
whole tracked caller from 2cc66eccb in the existing inert composition proves
the defect: after the first-terminal marker its CDP sequence is
Runtime.evaluate, Browser.close. This is an authored offline reproduction,
not a claim of failure or death in original Redline.
The caller now gates ordinary CDP sends synchronously once close begins,
removes terminal guest-trace sampling, refuses capture after closure and
discards unsettled captures. Only the isolated browser-close command is
allowed through that terminal send gate. The same whole-caller composition
now produces only Browser.close after the marker. Explicit postterminal
input and capture probes reject with zero CDP calls. All 15 existing startup
refusal/retirement scenarios, successful startup, source compilation and
private snapshot/token controls still pass. The locked full build passes and
the selected CPU remains byte-identical a320.
This caller change happened after the native manifest was frozen. That manifest and its successful proof remain unchanged. The changed caller requires fresh current runtime integration before original gameplay; the earlier fixture PASS is not borrowed to authorize it. No original menu, training scene, input or gameplay PNG was produced. The intended side-door route remains unexecuted, and the prior blocked forward holds were not repeated.
Retrieval and shutdown
The task retrieves 23 remote files and independently rereads their SHA-256, size and four gzip CRCs before requesting normal stop. This includes separate child waits, gzip EOF, the complete custody journal and physical drain. HTTP 41899 and CDP 33115 are closed; owned identities, profile processes, profile directory and writer locks are absent. The last native keys are zero; final guest input-queue length remains UNKNOWN because no postterminal guest read is issued. No duplicate source/media/module archive is created.
Box bx_jvzc62kr, UUID 69ce5bd6-8e7d-4300-a29a-4f0bd7715acf,
was created at 08:03:51.294Z with initial expiry 08:28:41.155Z.
Stop stop_f4cdb22d404ad552 completed at 08:08:42.905Z,
forced:false, error null, final state ARCHIVED. Final archiveAfter
is null; expiresAt is not returned. The independent watchdog and lifecycle
supervisor have actual exit-0 waits and separate stdout/stderr EOF; the heavy
runtime lock is released. Exact UUID ARCHIVED PHYSICAL_DRAINED release was
posted promptly to the board. No box resume/delete, public deployment, agent,
worker, Heroes II or Claude change occurs. This single task stops here.