Stronghold landed startup original: native coverage still unavailable
The one authorized original reached the title dialog, main menu, Choose Type and Custom Game hover through ordinary controls. At command 10, before Custom Game DOWN, the native attachment check failed with continuous coverage unavailable. The run stopped at that first failure and Chrome closed normally. Setup, world, movement and hostile engagement remain unreached. No retry ran.
This assignment continues the owner-authorized original gameplay lane from
startup repair dd0f27e878db016965e823ec920dc51ef3434ed6, integrated by
3b66c1c39a9ffa9435e3fea182585187deb06a1f. The accepted offline native coverage
repair is prerequisite evidence, not original gameplay, and was not rerun to
requalify the same revision. Historical failures remain unchanged.
Evidence lives in scratch/runs/20261105-stronghold-landed-startup-original/.
Assignment input was 681702a73dd3abd04a17afb34a6dee421e746203; source recovery
uses Git SHA plus relevant binary diff and owned new-file patches. Existing
media/modules are referenced by canonical paths and SHA-256, without source
archives, media-tree copies or module copies. All 1,856 canonical media rows
matched before any launch, including the installed original EXE SHA-256
9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f
at test/binaries/candidates/stronghold-crusader-demo/installed/App_Executables/Stronghold Crusader multiplayer demo.exe.
Preparation stayed scratch-only until CPU1120 FINAL at 12:26:47Z, ReturnFire1020 FINAL at 12:52:32Z and Lords1105 FINAL at 13:07:49Z. The independent 13:13Z gate verified 102 original process identities absent, 21 normal Return Fire Chrome exits, absent profiles, 43 refused ports, four free locks, no heavy runtime and 9.78 GB free disk. Lords' recovered Browser.close resolved but its normal exit code is unavailable after caller exit143; only resource absence is independently proved for that browser. No normal-exit acceptance is inferred.
The two owned shared files refresh the explicit dated fresh binding and its actual-entry contract. Current published source amendments and existing build hashes are named individually; the immutable original manifest, old saved fresh binding, accepted historical binding and offline no-launch binding stay closed. The current CPU, Return Fire and Lords release order is checked, including Lords' recorded LOCALHEAVY claim. The task cleanup deadline is 17:00Z; the 720-second original, 60-second bootstrap, 40-second command/review bounds and native/input/pixel/readiness guards retain their prior limits.
The new actual composed-entry preflight passes all 2,429 filesystem/HTTP rows
and 48 negative controls with zero real Chrome spawns or original executions.
Its mock launch sentinel and normal server closure prove the selected entry
wiring, not startup or gameplay. The full flock /tmp/wine-build.lock bash tools/build.sh passes. The
default connected contract passes, and the published-source actual-entry
qualification repeats all 2,429 rows and 48 negatives without a real Chrome.
The binding code/test commit is b4198ff6fa68977ebbb7bfb034221967cc9994f8,
published immediately with origin pull/push and explicit pinned-key SSH URL
pull/push. Origin fetch remained HTTPS despite its command-line URL override;
the explicit SSH URL pull/push subsequently passed. The original pins bind
that exact published Git SHA, empty relevant diff and no owned new source files.
The existing modules used by the original, reproduced by the full build, are:
| Existing path | SHA-256 |
|---|---|
build/wine-assembly.wasm |
bc4cabf7745ac4644c3d8cc1f5b70d798277c2a4525e3c665b98d08d6577894b |
build/wine-assembly.compat.wasm |
b1f38f1543731c349edaa5d2ae29e4ff0e42b82edd859ce7201de49f1ab278f7 |
The prepared operator returns the exact pending image for personal inspection, then requires an explicit matching live review receipt. Every capture must be inspected before further input; multiple reviews within one pending command remain distinct from its ACK. The single original ran after these prerequisites; its first real failure ended it. The production observer's conservative scope never grants preset/Start readiness from a diagnostic observation.
The original browser ran from 13:16:57Z to 13:23:09Z. Startup reached the title dialog at step 8,448. Ordinary Enter reached the main menu at 8,576; Crusader move/down/up reached Choose Type at 8,768, and Custom Game hover reached 8,832. There are 138 exact 64-step ACKs, drained input, null active/last input and zero mouse-button mask. All eight requested personal reviews met the unchanged deadlines; the smallest remaining margin was 12.496 seconds. All 21 captures were personally inspected. The last capture was inspected after closure only and supplied no input permission. No Custom Game DOWN, route arrival, preset, Start, world movement or combat command executed.
The native report retains the exact owning target/session and module, profile
2, image base 0x400000, epoch 346889932 and callback ABI version 1. It
reports reason 5 at depth 1: unsupported callback/unwind/coverage. Its history
contains a baseline and command-begin annotation, zero observed native blocks
and no native receipt. The host report contains zero publication records.
These records prove the unmet continuous-coverage prerequisite; zero observer
blocks do not mean startup never executed. The first invalidation site and
time are not retained, so neither a particular remaining callback nor a
regression in the accepted repair is established. No speculative emulator
repair, guard change, scheduling/time/presentation workaround or second
original is supplied. Accepted offline repair coverage remains distinct.
The immutable raw first-failure SHA-256 is
ef1dd1759a92f887773fd21abf5e0a2ecb78352882d65b2deeae44a6b14aecf4.
The terminal evidence seal is
f1a59ad7362c9c09cf60f2cc9fd26555cbb4ab085ef7e4d45595d2068dab2940.
It binds the failure, final state, native/host reports, original binding,
review chronology, all captures and cleanup. All 44 historical input hashes
remain unchanged, including the previous first-failure and terminal seal.
final-cleanup.json independently verifies eight recorded process identities
absent, Chrome PID 2868915's actual normal exit code 0/signal null, the owned
profile removed after confirming no users, four refused ports, four free
locks, no heavy runtime and more than 9.7 GB free disk. No watcher was launched.
All 2,429 runtime rows remain unchanged. The handled harness exit code 0 is
cleanup evidence and does not indicate successful gameplay.
The next prerequisite is evidence locating the first native reason-5 invalidation in actual startup history, before considering a warranted repair. This assignment ends with the exact missing prerequisite and no further original authorization.
No box is assigned (ID/state/expiry N/A); coordinator owns lifecycle. No SSH, subworkers or deployment are used.