Half-Life: continuation stopped on an unknown media upload

Run scratch/runs/20261112-halflife-paused-combat-2055/, with lifecycle evidence in sibling -control/. This attempt encounters a distinct transport blocker before original launch. Combat and living guard-room progress remain unfinished.

The repaired native Pause proof in halflife-native-pause-20261112.md (ae83f8d55 / ea06ee5e4) and the2045 hold (9ca2c6ffe) were read. All929 inherited runtime pins pass locally. The final browser, finite cycle, input, transport and semantic ACK selector remain byte-identical by SHA; solved control matrices and the old renderer arm were not rerun. The staged browser import check passes locally.954 frozen files were selected for upload; no remote all-hash pass is claimed.

The exact original1825 whole13 source remains758472 compressed bytes, SHA256 df8d61b2fcdd285a6a28e2e180930e6ee60eff388cd9bf31c557d3409dd18e51. All13 records decode and hash correctly, totaling2342063 bytes. Existing mount inputs pass their inherited hashes. The original export and mounts remain unchanged. Git SHA, relevant binary diff and owned new helper patches are retained locally; no source or media archive is made.

Actual /home capacity passes the1500000000-byte gate before create and before upload authorization; preallocation free is1538252800 bytes. Local capacity remains above the floor in all recorded upload samples. This is neither2035's resource refusal nor2045's local hold. Root's catalog RAM setup and reserve remain untouched; no RAM or old allocation-arithmetic gate applies.

An independent observable two-hour watchdog is armed and observed alive before creating private box bx_qwekfmpb, initial expiry 2026-11-12T22:59:46.924Z.707 individual uploads finish. The ordinary valve/pak0.pak PUT then times out during body write at30.000812 seconds, after13631488 bytes of complete chunks. The uploader reports UNKNOWN remote effects; no retry, joins its workers and exits1. Its actual parent wait and both pipe EOFs are retained. No upload, provisioning or launch is retried. provision-blocker.json, provision.stderr, the local disk samples and -control/api-events.jsonl preserve the failure and its scope.

No remote shell command or original browser is submitted. There is no fresh CPU/owning GL/full22, native Load, PAUSED frame, current health, movement, attack, hit, kill, guard consequence, death, Save or successor checkpoint. The prior native PAUSED proof remains historical evidence. No production defect is established, so no source repair, locked build or new gameplay qualification is claimed.

Only immutable input uploads reached the box; no unique remote gameplay log, capture or module was generated. Unique local failure evidence is hash-verified before requesting delegated normal shutdown. The box is now archived, expiry null, stopped 2026-11-12T21:02:48.634Z. Stop stop_361519b9f33a7197 completed, forced false, error null. Manager and watchdog each have actual parent wait0 and separate stdout/stderr EOF evidence. No inherited box was resumed or deleted.

Next: resolve the bounded media-transfer blocker in a fresh watched attempt, without replaying this UNKNOWN PUT, then require joined provisioning and all remote hashes before normal03:18 Load and a full native PAUSED review. Continue one reviewed finite combat or doorway cycle at a time. No full27, parity, FPS, audio or general crash-free claim follows. Older parent review state is left to the coordinator.