Connected Stronghold original: mandatory review deadline stop
One original execution reached the Stronghold Crusader Demo main menu using ordinary Enter down/up. I missed the required live main-menu screenshot review deadline at step 8,576; command 6 failed and the harness closed normally. No setup or gameplay was reached, and there was no retry. Offline qualification of the connected transaction does not qualify original native/copy/presentation provenance, pixel acceptance, or input readiness beyond that observed boundary.
The connected implementation is published in
23d773990dcedcdf2df551f1e105ec39f529a045; this task’s fresh binding and tests
are published in fc1a543015dba43b060f6943ba42eeb46a0ac8fd.
Evidence is in scratch/runs/20261105-stronghold-connected-original-gameplay/.
The original media, historical runtime manifests, helper closures and first
failures remain unchanged. No held MDK investigation is part of this task.
Ordered release and cleanup
Preparation stayed in assigned scratch until D3D7strided0635 published
4683c73ca889ff4f84d809e2fb7fd3d06432f7c3, then ReturnFire0730 published
fb7f45c7305bd8ba38188d39bb1a956db9895159, each with explicit
FINAL runtime AND file RELEASE and ALLBUILDSFINISHED.
The independent release-gate.json checks 29 absent exact PID/start identities,
both actual normal Chrome exits (code 0, signal null), absent profiles,
four refused HTTP/DevTools ports, both free locks, no heavy runtime and over
12 GB free disk. Shared ownership followed that gate at 08:26:30Z.
The first preparation-only checker accidentally matched release wording quoted inside OWN rows. Its output is retained with a correction; no admission or shared execution occurred. Actual admission requires the worker's FINAL token at its exact position, current ownership order, and independent cleanup.
Separate named binding
tools/stronghold-local-runtime.cjs retains its immutable original-manifest
digest and historical acceptedRuntimePins() rejection. The separate
freshRuntimePins() path explicitly names the current source/module hashes
and their published provenance. It checks the complete 2,429-row closure,
including all 1,856 unchanged media rows, original manifest digest, task name,
current Git SHA, relevant git diff --binary digest and owned-new-file patch
identities. Verification recomputes the whole binding and rejects drift.
Both modules stay at their existing build paths:
| Path | SHA-256 |
|---|---|
build/wine-assembly.wasm |
3361c1289e540ba1107c788905ab5a70ace7f4d003cfd05e1264c54bfc65267b |
build/wine-assembly.compat.wasm |
d33d98564db864ce8a1a7a4abad0554c4934331b36074bdb854c1ab96e458008 |
The existing original EXE remains
test/binaries/candidates/stronghold-crusader-demo/installed/App_Executables/Stronghold Crusader multiplayer demo.exe,
2,699,264 bytes, SHA-256
9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f.
Source recovery uses Git SHA plus binary diff and new-file patches only;
no source snapshots, archives, module copies or repeated media are created.
The assignment-specific authorization, ordered predecessors and wall-clock
cutoff/cleanup identities are refreshed. The 720-second runtime duration,
40-second command deadlines, 64-step ACKs, navigation/route/arrival limits,
native profile/history/lifetime guards, input readiness, personal review,
and normal-closure requirements retain their original bounds.
No screenshot whitelist is added. A joined setup diagnostic still reports
readinessGranted=false, pixelsAccepted=false, gameplay=false.
Executed offline qualification
test-stronghold-connected-runtime-binding.js explicitly exercises the fresh
binding under the actual runtime flock and actual predecessor release rows.
It checks 44 negative cases, unchanged historical media/manifests, wrong or
missing source/module/process/nonce/deadline/closure data and release reclaims.
It executes the actual composed bootstrap's filesystem writes and single-entry
latch, then the actual composed server/entry with Chrome spawning forbidden.
All 2,429 actual HTTP responses match their pinned bytes with required isolation
and no-store headers; the server closes and no Chrome child exists.
The same fixture executes actual command/transport functions: terminal host reports prevent command, native step and every mouse delivery; missing, malformed and colliding capture names reject before any step. The complete planned startup batch performs 8,448 fixture steps in 132 exact 64-step ACKs, preserving pre-step checks and the navigation count. This is offline input contract evidence, not ordinary original input readiness.
Both-module test-stronghold-native-copy-publication.js passes actual native
profile-2 and composed copy/publication/capture positive and negative fixtures.
The full test-stronghold-owning-callback-observer.js passes owning-Worker
callback/branch/setup/draw and full memory/register/command parity fixtures.
test-stronghold-natural-setup-dependency.js passes the intact gate/reset and
actual fallback contracts; the local-runtime observation consumer rejects
image-only/incomplete provenance. All are synthetic/offline evidence.
connected-first.log/json preserves the first fixture error: a second VM
evaluation reused its lexical save declaration. A fresh VM scope now reaches
and rejects the actual single-original-entry guard. The corrected test exits
normally, code 0 and signal null. No original attempt was consumed or retried.
Both full flock /tmp/wine-build.lock bash tools/build.sh runs pass; the final
build reproduces both existing module hashes. The final edited tests and
published-commit composed-entry qualification pass before original execution.
The code commit was immediately pulled/pushed, including an explicit pinned-key
strict SSH pull/push. runtime-pins.json binds the original to that exact
fc1a543015dba43b060f6943ba42eeb46a0ac8fd Git SHA, an empty relevant binary diff
and no uncommitted owned new files. Later documentation commits do not amend
that immutable original binding.
Single original and first missing prerequisite
The single attempt ran from 08:36:21Z to 08:40:21Z. The actual composed entry
served 1,038 matching responses and compiled the canonical 2,159,303-byte module
with SHA-256 3361c1289e540ba1107c788905ab5a70ace7f4d003cfd05e1264c54bfc65267b.
Actual module-delivery events for Worker slots 0–2 were observed. Six startup commands reached step 8,448;
ordinary Enter down/up in command 6 reached step 8,576. The trace contains
134 exact 64-step ACKs. Final input queue is empty, active and last input are
null, and mouse button mask is zero.
Ten screenshots were personally inspected: the selector, six startup captures
and three title-boundary captures. They show the original loading/splash,
Enter Your Title dialog and then the demo main menu. The title-boundary-0
live review was delivered at 08:39:55.924Z. The main-menu review was requested
at 08:39:57.254Z, SHA-256
250cc818265722bc46825b0b7d3f06d0c8586b67410b4b9c6f68f5d0289f533e.
The fixed command deadline expired at 08:40:20.872Z; the preserved failure at
08:40:21.010Z is Error: command/review deadline, command index 6.
I did not acknowledge the required main-menu review in time. The final two
screenshots were inspected after closure; those inspections cannot supply the
missing live review or authorize subsequent input. There is no command 7.
first-failure.json seals that first missing prerequisite, with SHA-256
65d1eaaf2d6a5054308840e74624c5e2246a2fdcff4bf7f5f23ac801cccbc55d.
terminal-evidence-seal.json binds the raw first-failure line, reply, pending
review, final state, browser closure and process receipts. original-audit.json
and personal-capture-inspections.jsonl retain the capture/input chronology.
This is a worker review-deadline failure; the available evidence does not
attribute it to guest execution or the connected native route.
No route/preset command or setup attachment started. Consequently actual original setup, joined native-cycle → selected copy → compositor → capture provenance, accepted pixels, subsequent input readiness and gameplay remain unqualified. The route diagnostics and successful offline fixtures grant none of these claims. All guards, caps and review requirements remain intact.
Normal cleanup and handoff
cleanup-verification.json independently confirms all 15 exact owned runner,
Node and Chrome PID/start identities absent. Chrome PID 2555210 exited normally,
code 0, signal null, at 08:40:21.132Z; the owning Node and wrapper also exited
normally. The profile was removed only after that normal exit and verification
of no profile users. Six HTTP/DevTools ports refuse connections, both build and
runtime locks are free, all 32 recorded historical inputs remain unchanged,
and free disk exceeds 12 GB. The tail-only board watcher was stopped separately;
it is not represented as a normal browser exit. No box was assigned
(ID/state/expiry N/A); coordinator retains shutdown ownership.
The evidence remains in the assigned ignored run, with Git SHA, binary diff and owned-new-file patches for source recovery. No candidate-corpus entry exists for this Stronghold investigation, so no unrelated candidate or dashboard result is invented. The run summary identifies the review failure and honest limits.
Next work requires a separately authorized fresh original attempt with prompt live review under the same deadlines and guards. This task stops at its first evidenced blocker; no additional original, held MDK investigation, guest write, forced presentation/time/scheduling, or guard relaxation was performed.