Stronghold original: timely reviews, native attachment prerequisite stop
One separately authorized fresh original reached Choose Type and Custom Game
hover using ordinary controls and timely personal review. At command 11,
before the Custom Game press, the owning observer rejected attachment as
unsupported-or-unobservable: continuous profile/image/epoch coverage was
unavailable. The harness closed normally at that first missing prerequisite.
No retry occurred; subsequent setup, native/copy/publication provenance and
gameplay remain unqualified. The connected runtime originated at
fc1a543015dba43b060f6943ba42eeb46a0ac8fd; this task's binding is published at
8c55c7f215b1cc79ee3055acf283e7e9fdf4b479. The previous original's command-6
review failure and historical closures remain immutable.
Evidence is in scratch/runs/20261105-stronghold-prompt-review-gameplay/.
Source recovery uses Git SHA plus relevant binary diff and new-file patches.
Existing media and modules are referenced by path and SHA; no source archive,
media copy, module copy, guest write, or forced presentation is introduced.
Scratch preparation began at 08:50Z and remained source-only until the exact
ordered releases from D3D7 depth consistency (e708ba0f72) and Return Fire
optional-404 cancellation (7b958cd967). The independent release gate checks
59 absent process identities, seven normal Chrome exits, absent profiles,
fourteen refused ports, both free locks, no heavy runtime and >1.5 GB free disk.
Shared ownership was claimed at 09:32:38Z, after that gate.
The named fresh binding refreshes only task authorization, ordered predecessors, the published D3D7 core hash and the actual current build hashes. Historical accepted-runtime rejection, original manifest seal, native history/lifetime, route/input/pixel guards, 720-second total duration, 40-second command/review deadlines and 64-step ACKs retain their existing bounds. Diagnostics alone grant no pixels, input readiness or gameplay.
The per-capture workflow was prepared before launch: return the exact pending image directly, personally inspect it, immediately acknowledge the exact live request, then poll again before source/log/report work. Multiple requests can occur within one pending command. Review never replaces command ACK. The scratch operator's synthetic offline checks cover read-only polling, exact receipt fields, multiple requests, ACK separation, foreign hash/request, expiration and closure refusal. No automatic acknowledgements are used.
The actual composed-entry offline preflight passes all 2,429 filesystem/HTTP
rows and 44 negative controls with zero Chrome spawns and normal server closure.
Both-module native/copy/publication fixtures, the full owning callback observer,
natural input dependencies and the diagnostic consumer pass. The required
flock /tmp/wine-build.lock bash tools/build.sh passes normally and reproduces
the exact named current modules:
| Existing path | SHA-256 |
|---|---|
build/wine-assembly.wasm |
05f4f99c47f46138bc599e0b588d0ab29ef87a5c8c0e22ded9e3ac9ac3fd3ffb |
build/wine-assembly.compat.wasm |
67b702236abced4946b31906c901440f0d0607b99f74cd4b327a6dd0c9a18ca6 |
The original EXE stays at its existing installed path with SHA-256
9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f.
All 1,856 media rows and 35 historical inputs/seals are unchanged. Immediate
origin pull/push and explicit pinned-key strict SSH pull/push passed. The
published actual-entry qualification repeats all 2,429 filesystem/HTTP rows and
44 negatives without Chrome. The original runtime pins bind the exact published
commit, an empty relevant diff and no uncommitted owned new files; later note
publication does not amend that sealed binding.
The single original ran from 09:36:54Z to 09:42:01Z. Startup reached the title dialog at step 8,448. Ordinary Enter down/up reached the main menu at 8,576; guarded move/down/up reached Choose Type at 8,768; the Custom Game hover reached 8,832. There are 138 exact 64-step ACKs, drained input, null active/last input and zero mouse-button mask. No Custom Game press, route-arrival command, preset, Start or gameplay command executed.
All eight requested personal reviews were delivered before their existing
deadlines, including both title-enter reviews in command 6 and both menu reviews
in command 7. The main-menu review had 14.9 seconds remaining; the menu-hover
review had 12.6 seconds remaining. All 22 captures were personally inspected.
The last capture, route-native-boundary-5.png, was inspected after closure
and explicitly recorded as inspection only, supplying no permission.
The immutable first-failure.json has SHA-256
ee7426e75089303d14cc4799c46daf0561d584c45bb2537c65a6935cdafffe72.
terminal-evidence-seal.json binds the raw first-failure line, failed reply,
native/host reports, final state, lifecycle, original pins and review chronology.
The first observer report retains a baseline and host annotation, zero native
blocks, null native receipt and the fault
Stronghold continuous profile/image/epoch coverage unavailable.
The host report has zero publication records and grants neither readiness nor
pixels. These facts preserve the exact unmet prerequisite; successful offline
fixtures do not supply original native coverage. No deeper root cause or
complete native-cycle/copy/compositor/capture join is claimed.
final-cleanup.json independently verifies ten recorded own process identities
absent, Chrome PID 2622398's actual normal exit (code 0, signal null), own profile
removed only after normal exit and no profile users, eighteen refused ports,
both free locks, no heavy runtime, stopped own tail watcher, unchanged 2,429
runtime rows and 35 historical inputs, and >11 GB free disk. The handled
original harness exits normally with code 0; that is cleanup evidence, not a
successful gameplay result.
Next work is offline qualification/repair of the continuous native profile, image and epoch prerequisite against this immutable failure. Any later original requires separate authorization and a fresh binding. This task stops without another original, guest writes, forced presentation/time/scheduling, deadline extension or guard relaxation.
No box is assigned (ID/state/expiry: N/A); coordinator retains shutdown ownership.