AoWII native production probe: original canceled during startup
Evidence: scratch/runs/20261118-aow2-native-ground-production-causal-repair/.
The requested terrain repair and precise native producer attribution remain
unachieved. The sole fresh original was canceled by the predeclared disk
headroom guard during startup, before menu admission, input or terrain
observation. No renderer, interpreter, guest, registry, configuration or media
change was made. No new army movement or ordinary original Quit is claimed.
The preceding two-move result and black-source observations remain historical
evidence in aow2-worker-identity-boundary-map-progress-20261118.md.
Sealed graph and bounds
The original used the published Git graph
0b55b3c2f1be569f8799ee1390ebfd8c620cb39b, reconstructed in memory without
foreign working-tree overlays. Both the retained module and actual debugger
extraction hash to
a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8.
All 1,083 media pins were checked, including real Borland DLL/BPL and MSS PE
bodies. There were no empty required-library responses or intercepted bodies.
Startup 900 seconds, total 1,800 seconds, Quit reserve 180 seconds and cleanup 1,820 seconds were declared before launch. Controller idle was 600 seconds. No in-flight bound was extended. A 10-second CDP allowance was declared before the fresh successful authored control and before the original; the initial authored control's 3-second timeout remains a separate closed failure.
The original's actual guest Worker target was
11A887FDB1254596CCB6798B411A127B, debugger session
EFDABED4E71B846A429FAFBB842C6BD1. Its instantiated module was extracted.
The observer was installed before execution through a separate actual session.
Startup ended before the pure slot/endpoint read and complete actor binding;
slot, endpoint and native surface generations therefore remain unqualified.
No historical surface, target or endpoint identity was substituted.
Prepared observation and authored controls
The run-local observer wraps the existing synchronous dx_trace and
gpu_stream_kick imports. It copies bounded native points, descriptors,
format/palette/owner metadata and source/destination contracts for Lock,
Unlock, Blt/BltFast, color fill and Texture::Load, keeping at most 16 records
for each of at most 128 candidate surface slots. Natural Device7 state selects
which histories to return. The Device7 discriminator uses the current call
shape rather than a historical return PC. No full-frame or stream bundle is
retained, and the observer adds no guest calls, writes or forced fences.
Actual native Device7 covering/noncovering geometry controls passed, with seven whole-memory hash comparisons across passive observations. Additional authored import-contract controls retain a known CPU point change, reject another CPU slot and distinguish a recycled allocation generation. Those latter checks invoke the diagnostic import contract directly; they are not an original Lock/Unlock writer attribution or an instruction-level store trace.
The initial browser control closed on a 3-second pure Worker-read timeout.
The next control exposed an inherited startup admission race: a visible
window could precede the GPS bridge matching its live port. The run-local
controller now waits for that relationship before binding. Neither closed
scope was queried again. A subsequent control visibly changed its white
window to a yellow triangle on maroon after independently released Space,
but the independent disk-floor guard canceled it before Quit; its later Quit
submission was refused locally before an endpoint request.
That canceled control lost its driver's wait and two EOF receipts when the
native custodian was killed after its cleanup grace. Its native-supervisor
and enclosing waits survive; the missing driver receipts remain explicit.
After verifying every recorded descendant absent and the retained screenshots'
hashes, the leftover owned /dev/shm profile was removed separately.
The final fresh authored control completed the same reviewed Space transition
and ordinary Escape reached retained ExitProcess(0). Its process, Chrome,
watchdog, owner and enclosing child waits and both EOFs are retained. These
controls qualify the prepared observation/input harness, not a terrain repair
or the cause of the initial timeout.
Original closure and limits
The original ran from 09:46:13.685 to 09:47:15.779 UTC. Its outer custodian requested cancellation at 09:47:15.429 with 1,636,896,768 bytes free, below its predeclared 1.65 GB headroom threshold. The outer guard's observed minimum was 1,631,911,936 bytes; the native watchdog's minimum was 1,632,972,800 bytes. The native supervisor returned exit 1, no leak and no polling error. All real child/enclosing waits and EOFs were retained and the owned profile was removed. The earlier authored control did cross the 1.5 GB floor before its independent guard reacted (minimum 1,487,085,568); this limit violation is retained rather than described as compliant headroom.
No original readiness receipt, menu screenshot, input command, movement PNG, terrain PNG or native producer receipt exists. There are 363 authenticated original body-consumer completions, not a completed application startup. After cancellation there were no further original endpoint requests, bound extensions or original replay. Cleanup is not ordinary guest Quit.
Consequently valid black source, missing geometry, producer conversion,
overwrite and wrong owner remain unresolved. The next useful original still
requires enough stable shared disk headroom to reach the native production
boundary; this run does not justify a graphics or asset fix or a Windows
behavior claim. No Wine reference, agents, workers, boxes, deployment or held
title action was used. Box ID null, state NOT_CREATED, expiry null, stop
receipt null. Artifact hashes and recovery instructions are sealed before
result.json, which is written last.
Validation: the run-local native Device7/producer controls passed, as did
node test/test-d3dim-gpu-points.js and the locked full build. The shared-tree
build includes foreign overlays and is separate from the immutable original
module. An attempted historical test/test-d3dim-draw-trace.js invocation
failed because that file no longer exists; its failure log is retained and
is not counted as a passing check. Only this report is committed.