Redline phased side-door preparation, 1617
Fresh preparation uses the published 1f69c75b6 first-error/phase repair and
the existing explicit publication and current-startup selectors. The native
closure has 903 providers, 149,103,332 bytes, and independent manifest SHA-256
80c158a980d2e17672af94c924591a89c83345999b4fbf0f38a90b2e6ab2c9bc.
The primary 3e491c08… and compatibility ecb45716… modules remain unchanged.
Peer-owned Q2/Q3 implementation/test paths have no intersection with this
closure. No provider substitution, blanket repin, or peer freeze was used.
Evidence is in
scratch/runs/20261109-redline-phased-side-door-progress-1617/.
git-base.txt and relevant-uncommitted.patch identify the tested source;
small run-specific scripts remain as inputs. Source trees and media were not
archived. Game media is referenced through the existing authenticated paths.
offline-provision.py invokes the exact retained production provision routine.
Uploads are byte checked without copying a source/media tree. The original
generated media assembly command executes with a memory-backed transport
destination; its chunk and final hashes must match. The actual startup barrier
then executes on the checkout and authenticates all providers. These transport
controls establish offline preparation only.
offline-launch.py prepares a separate closure and executes the exact generated
remote launch command in a real local Python subprocess. The remote transport
is explicitly local and DRIVER_PREFLIGHT=1 exits before server/Chrome creation.
The production staged CLI, generated controller, publication custodian, and
owning caller execute. The independently supplied manifest digest is retained.
The expected missing-ACK first error is written; the caller exits zero, the
controller exits one, and its ordinary parent records an actual wait and
separate stdout/stderr EOF. The kernel receipt records all seven actual reaps.
This expected offline failure is not native readiness or gameplay.
The actual first-error controls, both prebrowser controls, staged CLI controls with Git forbidden and 16 missing/changed-provider cases plus forged repin, current startup/admission controls, and the locked build pass. Production deadlines, admission limits, physical input/capture custody, and immutable provider pins are unchanged. The historical 1114-second delay and native startup cause remain UNKNOWN.
An independent Q2 reread verifies bx_y37jnhc6, UUID
fd8fb7e6-b84e-4ff0-9ee0-a715bc859c6c, exact API state ARCHIVED, and completed
unforced normal stop stop_2175d0a06f9c43a9. Retrieved artifacts pass SHA/size
and gzip CRC; six kernel reaps, two distinct parent waits with separate EOF,
physical process/FD/profile/writer/lock drain, and the actual watchdog join are
verified. Its final published RELEASE STOP at 16:24:16 UTC names
a48191173c9436ed6fb…, independently verified as an ancestor of origin/main.
Its generated parent wait remains UNKNOWN because its helper was
missing; actual kernel reaps do not fill that gap. No endpoint was created, so
there is no numbered-port connect proof.
Runtime remains gated on both queued workers' final published RELEASE STOP and independent exact API/archive, normal-stop, physical-drain and watchdog-join verification. A bounded 600-second boardwatch was armed at 16:19:12 UTC. Pending observations are not runtime permission. The direct generated caller also passes an actual transitive-import/read audit: every checkout dependency read or required before its preflight exit belongs to the authenticated closure. The old/new startup-boundary controls pass, preserving the existing readiness I/O behavior and deliberately incomplete inherited-writer evidence limits.
The boardwatch reached its original 600-second fallback at 16:29:12 UTC and actually joined with exit 2 and separate stdout/stderr EOF. Q2 had published its final release; Q3 had not. No runtime allocation was permitted at that boundary.
Newly available Q3 evidence was independently checked before this worker's
final publication: exact bx_t2ubq3yn, UUID
e6dac148-e633-495b-b3f4-2727b4c80540, is ARCHIVED, with completed unforced
normal stop stop_eb076fca0d3c6cdf at 16:28:23.692 UTC. Its 218 retrieved artifact
records pass SHA/size and gzip CRC, with 132 actual kernel reaps, three distinct
parent waits and separate pipe EOF, two closed physical ports, absent profile
and FD holders, drained input/runtime locks, and an actual watchdog join with
status zero. These observations do not supply the still-required Q3 final
published RELEASE STOP. Browser normal close and nonleader completeness retain
the peer's explicit UNKNOWN limits.
Outcome: runtime queue blocked; gameplay unverified. No new Redline production defect was found in the offline checks, so no production code was changed. No leased box, native fixture, original-game input/capture, local Chrome, agent, worker or public deployment was created by this task. Own box ID/state: NOT_CREATED; expiry and stop receipt: N/A. Historical native startup/readiness and the 1114-second stall cause remain UNKNOWN.
The evidence manifest independently rechecks stored hashes/sizes and valid
gzip CRC. Empty files remain EMPTY_INVALID, and the two deliberate
inherited-writer streams remain INVALID_INCOMPLETE, never proof. One own
completed duplicate manifest was losslessly compressed, independently verified,
and supplied with a restoration recipe before removing its raw duplicate.
Free /home remained above 1.5 GB at recorded checks.
Next requires the missing final published Q3 release and a fresh authentication of the prepared production closure before the sole runtime lane can be used. Prearm the independent immutable 25-minute UUID watchdog before allocation; perform one fixture and inspect its new phase/first-error records. Only passing every existing gate permits the original car-door comma attempt. This worker ends with published RELEASE STOP and no background watcher left running.