Half-Life: paused continuation held during provisioning

Run scratch/runs/20261112-halflife-paused-progress-2035/, lifecycle sibling -control/. This attempt adds no gameplay progress. It stops at a different stage from the parent: shared disk space falls below the owner floor during provisioning, before any remote command or original browser launch.

Read the native Pause handoff (ea06ee5e4, input repair ae83f8d55) and half-life-uplink.md. All 881 inherited pins match locally. The FINAL corrected browser, input/cycle, transport, semantic ACK selector and capture/admission helpers are byte-identical to the parent, with SHA pairs in helper-reuse.json. Only cancellation/recovery paths are relocated; the lifecycle manager adds a floor check immediately before create. No production source or media changes. No pre-fix arm or unchanged input/cycle qualification is repeated.

The local staged import gate passes with no effects; Python and JS syntax checks pass. The combined local manifest verifies 905 files before allocation. Exact source Git SHA and relevant binary diff are retained, with owned new helpers as patches. Media remains referenced by existing path and SHA. The authoritative 1825 export is rehashed at 758472 bytes, df8d61b2fcdd285a6a28e2e180930e6ee60eff388cd9bf31c557d3409dd18e51. All thirteen export records decode to 2342063 bytes and match their hashes; the thirteen existing mount inputs also match. They remain unchanged.

The independent two-hour watchdog is armed and observed alive before create. The immediate pre-create disk sample is 1514532864 bytes, above 1500000000. The joined two-worker uploader later refuses an authorization at 1443745792 bytes (disk-samples.jsonl, lifecycle api-events.jsonl). The failed item records phase authorize, completeChunksSent0 and remoteEffects UNKNOWN. No retry, remote import gate or original launch follows. The uploader's actual parent returns1 with both EOFs. Shared free space subsequently recovers; this does not erase the refusal or authorize replaying a terminal provision operation. Reserve is unchanged; no RAM gate.

No new CPU/owning GL identity, PAUSED frame, native Load, attack, traversal, death or successor Save is claimed. There is no current game health; the parent's last repaired frame was30/0. The requested combat remains unfinished. No source defect is established, so no runtime repair or build claim follows.

All unique task evidence is local, generated by the joined uploader and lifecycle manager; uploaded files are only the pinned source/media prefix. Pre-stop evidence hashes pass. Final56-file manifest final-evidence-sha256.json.gz is3129 bytes, SHA256 ef6c31c9ba30aeff2b023ecf70352edc395561c4fa7da76ab565278a6d82cbff. No source/media archive or duplicate gameplay dispatch is created.

Own box bx_z3sjmg5q is archived, expiry null, normally stopped at2026-11-12T20:34:16.477Z. Stop stop_23a417ef12c1f23f completed, forced false, error null. Both manager-parent and watchdog-parent actual waits return0 with stdout/stderr EOF. Initial expiry was22:32:40.310Z. No box is left running or resumed.

Next: restore stable shared disk headroom before a fresh allocation; then join provisioning and verify all remote hashes before the unchanged whole13 native Load. Confirm CPU/owning GL identity and a full native PAUSED frame, then use fresh visual review for one finite combat or guard-room cycle. No full27, parity, FPS, audio or general crash-free claim is made.