Original Neverhood continuation, November 17
Evidence: scratch/runs/20261117-neverhood-original-install/.
The November 16 dependency and controller investigations are retained rather
than repeated. Published c2e18a9e2/aa6be398e qualified genuine SETUPX and
DSETUP6E initialization/retirement; 2d3a248f3 qualified native BUTTON control,
thunks and sealed source/module admission. These are not installation proof.
Interrupted preparation
The old run ends with a successful Git-only compilation, a sealed holder record
and a generated original recipe. There is no retained original admission,
original-spawned.json, launch record, native PID, native log, screenshot or
native wait. The recorded holder PID 3647291/start token 288195132 is absent.
No old endpoint was contacted and no old process was signalled. The missing
holder closure and launcher/owner joins remain UNKNOWN. Absence of those
records does not prove a clean shutdown or justify reconstructing receipts.
Continuation
The controller now uses a distinct run directory and checks both old and new original-consumption markers before launch. Borrowed supervisor and preload bytes must equal published main before the Python helper is imported, preventing execution of another worker's uncommitted helper changes. Compilation freezes Git plus explicit owned patches; foreign shared-tree changes are excluded. The complete original CD and genuine dependency hashes are checked again.
The authorized original retains 2400 native seconds, an independently prearmed
2420-second watchdog, a 240-second Quit reserve, real clocks/defaults and
--iso-drive=D --iso-exe=SETUP95.EXE. Unsupported DirectXSetup still stops
before dispatch. Actual live BUTTON identity and label are mandatory for
installer/menu gestures. UNKNOWN closes the endpoint permanently.
The final default Win98 native seven-case controller test passes, including two real BUTTON modal generations, independent physical UP, native ExitProcess, repaint acceptance, focus/owner/modal-caption/child-caption/stale refusals and permanent UNKNOWN with no later HTTP. Sealed admission passes actual Node Worker/process inheritance and all seven negative recipes. Unit tests prove unpublished helpers refuse and the verified helper bytes execute without a second mutable-path import. The final canonical locked build passes.
An earlier canonical attempt refused a concurrent renderer lifetime hash; its owner repaired that gate. An earlier native test correctly refused my own runtime-source change made while it was running. Both failures are retained; the completed guard was frozen before the passing rerun. No original was used for either test. Completed genuine dependency/thunk investigations were not repeated.
Single original result
Material fix f6a959e51 was published before the original. Its prepared source
is main 001f59ebc9832f060771974881a02f0ef928b95e plus the two explicit owned
source patches. All 4572 source rows equal the passing final native fixture
inventory. The original module is
5c9f7126daff2e586685c0dd2ad46b79c5e43e8dbf569aea2919b733b075614a.
Independent descriptor/hash checks and the production admission's actual
Worker/process inheritance pass before runtime clocks begin. No concurrent
scene, renderer or NE-loader WIP was adopted.
One complete original launcher capture succeeded and was personally viewed:
gray launcher on a teal desktop, enabled Install and Exit, disabled Uninstall
and Play. The actual focused native BUTTON is HWND 0x10002, control ID 105,
generation 2, label &Install; no container surrogate was used. The selected
image is original/launcher.png in the run directory.
The single finite Install press was consumed, but the receipt's completion timestamp was 564.7 ms after intent start and its HTTP response 613.7 ms after start, exceeding the 500 ms confirmation limit. The independently prearmed release sent at 1401.6 ms and acknowledged physical UP at 1907.1 ms, exceeding 1750 ms. The release process joined with exit 0 and both pipes drained before permanent UNKNOWN was published. Effect-start time is not recorded; a late completion timestamp does not establish when effects began. No limit was extended and no successful finite-action completion is claimed.
The ledger has exactly four requests: capture, bind, the one input and its original independent release. There were no requests after UNKNOWN, no second capture, replay, rebind or second original. The frozen source and module were unchanged throughout the original.
The retained native log demonstrates new progress beyond the old SETUPX
dependency boundary: genuine DSETUPE's ThunkConnect32 returns 1, it resolves
iDirectXSetup, opens its real dialog, reads D:\setup\directx\directx.inf
and performs temporary DirectX file copies. It then traps with
UNIMPLEMENTED API: SMapLS_IP_EBP_12, EIP 0x006d4028, ESP
0x074fd44a, return address 0x006d074b. That exact imported API is absent
from the tested published API table. Existing LS32/FT/thunk qualification does
not establish this import family's ABI or mapped-pointer lifetime. The exact
unsupported unsuffixed DirectXSetup guard remains armed and was not reached.
No fabricated success, install files or registry state were introduced.
Native actual exit is 1, both log streams reached EOF, and the independent watchdog joined with exit 0 after the actual native wait; its deadline did not fire. A cancellation request written after the native exit caused no host signal. The supervisor and holder owners have actual exit-0 waits with both pipes drained, and the holder records its descriptors closed. Historical missing November 16 joins remain UNKNOWN.
Installed Play, first-room action and native Quit remain unproved. The concrete next work is real SMapLS_IP_EBP_12/matching unmap semantics and bounded input completion/release latency, qualified without replaying this original. Shared core files carrying foreign NE work were not changed for this task. No box or worker was created: box ID null, state NOT_CREATED, expiry null, stop receipt NOT_APPLICABLE.