Uplink: rear panel destroyed, south/east corridor reached, native successor restored

Run: scratch/runs/20261112-halflife-authored-back-panel-passage-1825/, with -control/ for the fresh caller, blank control and lifecycle.

Fresh original whole12 native Load and movement now lead to visible removal of the separate wooden rear panel, passage south beyond the assembly, an eastward corridor and a visible headcrab encounter. A new native UPLINK03:18 save is exported as a complete thirteen-file set; move-away, native Load of that new slot and fresh movement pass. This advances the authored geometry investigation from static clearance to native consequence.

Panel contact and onward passage

n16-loadwait restores the original earned01:48/crowbar/100 health/0 armour view. n17-bound binds the living gameplay owner; both actual guest and owning renderer modules hash to 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17. The actual owning context reports software:true. n18-fresh-right visibly strafes, and n19-center-opening aligns with the damaged open front.

Ordinary standing forward movement in n20-enter-shell and n21-close-back enters the shell. Its rectangular rear face, torn front/side edges and ceiling match the original authored model45/entity147, material1, health50, four-unit-thick rear panel. This identity is a geometry/full-frame inference; there is no live entity-hit query or measured remaining-health claim.

The first two bounded Enter attack intervals (n22/n23) show no removal. After passive animation review, n25-back-range visibly approaches closer. n26-melee-back leaves a fresh dark impact mark at the center of the rear face. The next ordinary Enter interval, n27-back-hit, removes that face: the new full frame exposes grey wall, ceiling light and open floor beyond, with remaining roof and neighboring wood at the side. No runtime hit count or damage amount is inferred from physical hold duration.

n28-through-back visibly advances through the cleared opening. An early eastward look meets the concrete peninsula, so fresh frames guide a return to the south lane. n33-past-second advances farther south, then n34-corridor-east reveals the red-lit eastward connecting corridor. n35-corridor-passage moves down it to the bend. This is the route past the second crate, not destruction of every part of that second assembly.

Health drops to85,75 and then lower during the corridor observations. The initial damage source is off-frame. n44-move-away shows a headcrab at the bottom of the corridor; n51-restored-freshmove shows its full nearby lunge. An enemy kill, next door traversal or safe onward checkpoint is not claimed. The small foreground crate was already gone and is not attacked. No crouch/push loop, console, guest-state/AI/position/clock/memory write or original EXE/PAK/config change supplies this outcome.

Complete earned successor and native restore

The original1635 export independently re-verifies at649713 compressed bytes, SHA256 f523dfeaf57ef0f4d4c470965d4f036b3e67affde4498f203f55650db204d809: 12 strict-base64/size/SHA-checked files totaling2006166 decoded bytes. Fresh original VFS verification matches that entire set before native Load.

Only after destruction and corridor passage does the worker open native Save/load. Two early acknowledged Escape intervals still show gameplay; the longer fresh n39-open-save visibly opens the menu. n42-native-save uses Current / New Saved Game, and its full frame displays Saved… at health40/armour0. The native list later shows the new UPLINK03:18 slot.

Successor property Value
Artifact earned-native-save-n43-earned-export.json.gz
Compressed bytes 758472
SHA256 df8d61b2fcdd285a6a28e2e180930e6ee60eff388cd9bf31c557d3409dd18e51
Complete set 13 files /2342063 decoded bytes
New slot c:\valve\save\half-life-005.sav,336143 bytes
New slot SHA256 5d02d6bc10c55a7502acf69a83f7bde3b6aab8fe9c07e728d562dc83ab6b7bdb

All older .sav files and hldemo1 auxiliaries remain identical. The native save updates hldemo2.hl1/.hl2 and adds005; no auxiliary member is borrowed from another checkpoint. Preserve all thirteen exported members together.

n43 exports that complete set read-only. n44 visibly moves away; n47 shows the newest03:18 slot selected. n48 requests native Load and n49 confirms the native current-game exit dialog. n50-restored-settle restores the saved corridor/crowbar view, distinct from the moved-away view; n51 visibly strafes and witnesses the headcrab. Fresh damage is already occurring after restore: the frame shows30 then20 health, not a safe save.

The closing export contains the same thirteen exact file records and data. Its gzip SHA is 06a3ac8be6496ad34db2f6525d33eccaec51559b970751f519b4009fa8e6c18a: native Load changes enumeration order, placing005 before the auxiliary files. The byte-identical member set, rather than compressed container identity, is verified explicitly. The original n43 artifact above remains authoritative.

Controls, evidence and shutdown

All646 predecessor pins match locally; the fresh676-file runtime manifest and staged imports pass locally and remotely. The eight input/readiness/ capture/delivery helpers are byte-identical to the final1730 controls. Their existing actual Chrome/emitted-consumer/independent per-key release reports are reused by SHA, without repeating the unchanged expensive matrix. New caller paths, syntax and compact manifest check pass before allocation.

An independent observable two-hour watchdog is armed and observed alive before the single creation POST. The fresh sandbox's actual Chrome blank endpoint, CDP, full-PNG and clean-close control passes first; its23 unique recovered references hash-check and130/130 custody tasks reap, with actual outer wait0 and both EOFs. The original then starts once in that same sandbox.

terminal-verification.json checks586 recovered references, 52 full PNGs with CRC and all22 before/after identity fields, 35 gameplay captures against the living owner,185 HTTP pins,42 balanced acknowledged input pulses (24 key pairs and18 click pairs),102 trusted events and52 numbered ACKs. Release attempts occur0..2ms after their planned times. All admissions use fresh reviewed full captures; there is no UNKNOWN/replay or terminal failure. The first verifier assumed a different ACK filename convention; it was fixed to inspect actual numbered reply files. Its second overstrict container-hash check exposed the close export's enumeration-order difference described above. The corrected checks pass against the retained actual artifacts.

Ordinary quit n52 acknowledges18:38:48Z. Original Chrome exits0/signalnull; its actual outer parent waits0, both EOF threads join, and367/367 custody tasks reap with no remaining/unreaped tasks or cancellation. All unique evidence is recovered and SHA-verified before delegated normal sandbox stop.

bx_6dvqbyyb is archived, expiry null. Initial expiry20:25:29.519Z. Normal stop receipt stop_6e1f4baf830d4480 completes18:39:41.988Z, forcedfalse/errornull. The actual local manager and watchdog both join0 with both EOFs. No box is deleted, resumed or left billing idle.

Initial actual available disk is1518510080 bytes; after the coordinator's separate closed-transcript offload, preallocation is1846132736. All54 owned disk samples remain above1.5GB, minimum1721409536; samples do not establish continuous compliance. No reserve change or RAM gate is applied.

Git is the source archive: original preparation records 5ed39acacdf6a48e2eda7e2efb864f5e229d1aac, relevant binary diff and small run-helper patches. Evidence stays in the run; exact compression journals retain raw size/SHA and roundtrip checks. No source/media archive, production code change, production build, deployment, other workers, parity, FPS, audio or full27 claim. Parent full artifact review remains pending.

Next: retain the complete13 set and address the active headcrab from the earned03:18 corridor checkpoint, then continue around the bend toward the next authored doorway. Rear-panel destruction and this passage no longer need another unchanged attempt.