Drakan browser original 2203: disk floor stopped preparation before T

The one fresh remote original launched with the newly published ordinary-browser observer closure and the actual owning CPU's canonical 4b45 module, then reached the main menu. Shared /home space fell below 1,500,000,000 bytes before a living mounted scene and fresh actor/device/code pins were established. Preparation stopped and the original closed normally. No T, Up, gameplay heading or attack was dispatched. No native COMPLETE, takeoff, ascent, worldZ or sustained-flight result is qualified. The accepted cc6a14236 ascent remains separate and unchanged. This result authorizes no restart or replacement hold.

Evidence: scratch/runs/20261108-drakan-browser-original-2203/ (ignored). The source authority is published Git 0e2bd19d802278aacc06dd952e135529c1edad63, plus the small run-specific helper patches and the explicitly referenced existing boot-provider recovery patch. source-head.txt identifies the shared main observed during preparation; production providers were selected from published Git blobs, excluding peer WIP. No production code was changed in this task.

Closure and caller preparation

The complete closure has 673 providers, 126,026,745 bytes and 16 physical helpers. Actual driver preflight passed without starting Chrome; all uploads joined before the final remote HASH barrier, manifest SHA256 0bcffc52d58fdf1560c73396df68e08c90e977f371114c2fa6b6807a9d1dcb0a. A pre-runtime correction serializes i64 diagnostic identities as exact strings; only that helper, the parent barrier filename and manifest were restaged, then rehashed before the sole launch. The earlier barrier is preserved.

Kernel remains published bcf8c7bd788f2c63668406b11f72652006cde8dc, SHA256 5371233b12d3a63e13a9768529af43e5a61b7ff1682b2d3c09e4db6a976e12d0. Journal and command compression are gzip. The accepted logger 979b3a8b, readiness 9ba9ae8b and normal-close 1f4fe08b providers are unchanged. The ordinary physical caller uses the accepted Drakan T event encoding, independent release timer and the current browser lifecycle consumers; unrelated TR2 shot observation was removed from this run-specific driver.

The preload sets boolean WINE_DRAKAN_OBSERVER=true before the first compile. It observes trusted DOM delivery and reads the already-created renderer buffer record without another input poll. The prepared bridge retains that record's stamp/sequence and the original event-start clock, and returns a Promise tied to the Node caller's actual CDP key-up completion. Its independent timer is installed before down dispatch. Owner/installed-relocation/live-code checks and a no-input bridge probe precede any proposed T. A validated Controller COMPLETE would stop the controller on the next task; UNKNOWN already stops it. The actual browser method remains responsible for joining live releasePromise/releaseError.

Those pre-T gates were not reached in this original. The physical T bridge, actual native down-active state1 and all enclosing CALL/RET completion therefore remain unqualified. Prepared code is not substituted for their execution. Synthetic page-caller checks pass for boolean opt-in, original start and buffered stamp/sequence retention, pending physical Promise, wrong-token refusal and release-before-result behavior. No local Chrome or local game was used.

The retained 2140, 2105 and 2127 proof inventories (33, 68 and 57 entries, including the declared self-index entry) were independently reread by SHA/size and gzip CRC, with their indexes hashed separately. The 155 kernel proof references were likewise checked. Their unchanged focused/build proofs were reused without identical reruns; no fresh production build is claimed. Initial preparation failures involving canonical symlink targets and inventory schemas are retained. A premature startup-file fetch failed before that capture existed; it dispatched no input and was not replayed.

Original and resource blocker

DevTools readiness took 16,387 ms within the unchanged 30-second cap. HTTP, loaded-source and actual owning Worker bytecode checks identify canonical 4b45bda53a90b665896cf3b85d9a157b7c3703563c88b6666e4ee2e4b346bcc3, 2,184,500 bytes. No supplied Module, canonical refetch substitution, backend, CPU, binding, guest-clock, seed or configuration change was used.

Reviewed ordinary Warning/OK, publisher/startup/title and menu input reached the main menu and acquired pointer lock. Two stale startup/menu requests were explicitly refused before dispatch, effects0; no UNKNOWN input was replayed. There was no New Game selection, living mounted review, independently qualified fresh actor/device pin set or T dispatch. The final reviewed menu capture is review/webgl/menu-action-fresh.png, 22:15:25.407Z, SHA256 3b39d47240696e0b4d10f0612471653320c5887cead60c54b58d0a6b31d9625a. It is menu evidence, not living gameplay evidence.

Space initially exceeded the floor but concurrent writes depleted it. The observed breach was 1,499,586,560 bytes. Preparation stopped and the coordinator was notified. Own lossless compression of already-used metadata and one independently identical PNG saved 1,047,427 bytes with reconstruction records written before removal. The floor fell again; the recovery runner initially refused before running its remote inventory. Coordinator compression briefly restored headroom for recovery, then ongoing writes crossed the floor during recovery. No continuous-floor compliance is claimed. The coordinator later restored substantial headroom by losslessly compressing its own rotated logs. No peer file or old run was deleted by this worker.

Normal close, custody exception, recovery and box stop

Normal Quit received ACK12. Chrome exited 0, signal-null, with normal close ACK, no signals and 11,524 ms close duration. Both compressed pipes reached EOF before profile removal. Ports 41829/43725 closed; the profile, writer lock and observable owned writable FDs are absent; the runtime lock is released. Absence is supplemental evidence, not a replacement for terminal waits.

All 356 owned PID/start identities have 356 actual terminal reaps, with empty remaining, unreaped, unresolved-ptrace and cancellation sets. Kernel complete is nevertheless false, and the actual outer wait is 1. PID 7411/start29590, TGID7399, PPID7234, entered through kernel-autoattach-stop with parentCustodian:null, custody sequence917. Its actual before-reap/reap are sequences922/923, status0, but lineage remains unresolved. The kernel asserts unresolved kernel lineage; this exception is preserved, not promoted to a complete-custody PASS. CLONE_UNTRACED/nonleader-exec limits remain.

Before box stop, all 180 regular remote artifacts, 4,128,392 original bytes, were covered by independent original/compressed SHA/size and gzip CRC rereads. There are no remote symlinks or special files. 114 new gzip transports, 205,461 bytes, plus 44 existing raw/lossless references, recover the unique evidence without duplicating reviewed captures or modules. Every selected physical helper is covered by the final barrier and its recovery patch. The all-file local inventory has no extension filter and supplies recovery recipes for used metadata. Logs, including commands/kernel streams, were gzip from their first stored byte; early preparation tool-output-only limitations are disclosed.

A durable new UUID and independent observable 25-minute watchdog preceded the single idempotent create. Box ID and initial archive deadline 22:35:02.156Z preceded runtime; watchdog deadline was 22:35:02.418Z. Evidence verification preceded delegated normal stop. Both lifecycle roles and their supervisor have actual exit-zero parent waits; the watchdog did not fire.

Box bx_dt4bhpk6 is ARCHIVED, archiveAfter:null (the API does not return a separate expiresAt field). Stop stop_d0d4f3398047361a completed 22:19:04.685Z, forced=false, error=null; stoppedAt22:19:04.664Z. No old box was resumed/deleted, no runtime restarted, no public deployment or additional agent was used. RELEASE STOP after publication. Full27, parity, audio, FPS, worldZ and sustained controlled flight remain open. The next work needs a separately authorized original with durable disk headroom and the same unextended, unrepeated native-completion/release gates.