Darkstone streamed staging transaction repair

Stopped at the task's permitted substantive causal tested repair condition. The requested fresh remote restore, current numeric health/live BAT review, ordinary response and new native save remain unperformed. No allocation, UUID, browser, original or guest input occurred. Historical LIFE 16/35 is not a current reading. Historical 1940 UNKNOWN upload and 1910 SIGKILL / normalChrome UNPROVEN remain unchanged.

Evidence R: scratch/runs/20261108-darkstone-streamed-bat-response-2012/. Predecessors: streamed consumer, 1940 provisioning stop, browser close repair.

Cause and owned repair

The historical physical helper closure validator opens checkpoint paths as local raw files. Merely replacing the PUT loop with streamed decompression does not repair this selection/staging boundary: validation still fails before the transport runs. The new run-owned provision-streamed.py selects exactly the canonical FINAL1910 gzip providers and validates their metadata, compressed bytes, decompressed bytes and complete gzip integrity without a local raw stage. Noncheckpoint source selections remain explicit existing paths or full Git blob objects. Changed selections fail before any remote call.

The provision transaction exclusively claims a fresh remote root before any PUT. It uses the actual historical transport's HTTP upload function for noncheckpoint providers, and the published darkstone_streamed_restore.py / streamed_gzip_upload.py functions for both checkpoints. Both gzip sources are prevalidated before transfer; each PUT must complete its second CRC/SHA/length validation, return HTTP success, then pass an independent destination HASH. Only then does the transaction upload the selected manifest and execute the actual uploaded native-startup-barrier.py, which independently rereads every provider before publishing readiness.

An exclusive durable local claim precedes work. Every failure records sticky quarantine and prohibits launch and replay, including failures after one file was verified. Local acceptance and remote readiness are separate requirements: an UNKNOWN barrier reply can leave a real remote readiness file, but local quarantine still prohibits launch. The local require_accepted gate must be wired alongside remote barrier require by a future launcher; this task does not claim that a complete runtime launch closure has been integrated.

One absolute wall-clock alarm covers selection, API, upload, HASH and barrier work. The caller must also prearm the independent observable lifecycle watchdog; the helper does not allocate boxes or replace that watchdog. All transaction deadlines and destinations are recorded in the exclusive claim. Socket timeout alone is insufficient.

Validation and precise scope

13 focused integration controls pass in R/focused-final.log.gz. An isolated HTTP sink process receives actual Content-Length PUTs and retains bytes only in memory. Its independent command endpoint executes the exact hash commands and the uploaded barrier source against those received bytes. This is real local HTTP transport with a simulated remote execution/filesystem interface, not a cloud-provider or browser acceptance test.

The positive fixture selects six providers: the two canonical checkpoints, the startup barrier, guarded browser adapter, close helper, and published kernel blob. It performs seven PUTs including the manifest, two independent checkpoint HASHes, then the actual barrier. It transmits 4,546,657 checkpoint bytes with zero local raw checkpoint bytes, under a raw-write prohibition. The same checkpoint selection fails the historical physical validator and passes the new source-aware preflight.

Negative controls cover changed selected source, truncated gzip source, changed gzip between validation and PUT, partial second upload returning 2xx, HTTP error, UNKNOWN remote HASH, post-HASH destination corruption, an already claimed remote root, and UNKNOWN barrier ACK. No unsuccessful transaction can be repeated or pass its local launch gate. The deadline control interrupts a real delayed PUT at approximately 250 ms despite its 30-second socket timeout. The barrier corruption fixture initially targeted an earlier test's root; R/focused-01.log.gz retains that failure, and the corrected isolated-root control passes in focused-02 and focused-final.

The exact browser guard accepts selected SHA-256 2535a4fea2ad1acbc245d10fd00cc6c583913095aacdc9cd92462c4d6b346a2f, rejects changed bytes, and selects the shared close helper with terminal/drain failure handling. Chrome was not started. The kernel is selected via the exact published Git blob from d8573b542, incorporating the published gzip support; the peer-owned working file and command-log helpers were not read or captured. No normal-Chrome, kernel runtime custody or complete 550-provider selection is claimed. The inherited browser, Chrome and kernel-command raw logging paths still require their own supported integration before a fresh runtime.

flock /tmp/wine-build.lock bash tools/build.sh passes in R/build.log.gz. Every test/build log is gzip from its first byte, with original stream SHA/size and independent decompression reread receipts. Independent GNU timeout watchdogs were prearmed before log draining. The sink has an actual terminal wait of -15 and drained stdout/stderr. These are local fixture process receipts, not remote browser/kernel shutdown evidence.

The exact original FINAL1910 pair remains retained and independently reread:

File Bytes SHA-256
characters.lpl 1,342,316 4762ae9c0d7d048595433d121629a87d5a1aa24e7c3ebe84c7605006e3c10baa
game641d_6af0ca48.sav 3,204,341 5e898dc9d6f7a13350c939bf5b712eccfff95ef1072c93023103705999f84ffc

Source recovery uses the recorded exact Git SHA, selected source PATH/HASH or published Git blob, and R/owned-source.patch.gz for the small run-specific provisioner, controls and gzip runner. No source tree archive, media/module copies, peer WIP, old-run deletion, local Chrome, old-box operations, private guest writes, handler calls, configuration/backend/binding/clock/seed changes, deployment or subworkers occurred. Shared free space was sampled above 1.5 GB; there is no continuous global disk-floor claim.

Box ID/state: none / NOT_CREATED. Expiry: null. Stop receipt: N/A. There is no billing runtime or missing remote command log to recover. No new save pair is claimed; the canonical predecessor pair is unchanged.

Next is a separately assigned fresh runtime with the full helper closure, supported gzip logging for every unique stream including kernel command log, prearmed immutable lifecycle watchdog, both staging gates, actual current health/BAT review, one bounded independently released ordinary response, and immediate native New Save recovery. Full27, parity, audio and FPS remain open. RELEASE and STOP.