Stronghold repaired bypass original, 2026-11-05
The tested binding reached the actual original native draws: two refresh-zero
bypasses preserved the timestamp and returned normally, alongside one ordinary
late-clock draw. The sole original then stopped at its first concrete fault:
command 14, route-arrival, rejected first unexpected natural scene: unknown
at 03:16:49.948Z. The fresh image shows a setup layout; its complete readiness
was not accepted. No preset, Start, world control, command 15 or second original
followed. Gameplay remains unproved.
Source-only preparation preceded all shared mutation. ReturnFire0215 FINAL
c617c4255bafca2e71a28bef0ce54de607035669 and MDK0235 FINAL
cd4b2e74174231b62ab3aa0affc2d1b1bb077efd provided runtime AND file RELEASE
ALLBUILDSFINISHED before the binding amendment. Independent verification at
03:09:22Z confirmed six exact PID/start-tick pairs absent, all five ports
refused, both profiles removed, no local heavy process, both runtime/build
locks free, and over 1.5 GB free on /home. The prerequisite cutoff is 06:50Z;
runtime cutoff 07:30Z, cleanup 07:33Z, finish 07:50Z.
The published repair is ac635964f52d222b99d04b0750601a2eee081f44.
The specifically accepted old observer is
a931b3dc3656e4409de1748d0a0557fff9b70914e23f04067961fa41fbc282bd;
the repaired observer is
0329fc2adcc573e78072beb390de4b08fed721722062e2457da04d35a9c153f1.
The amendment changes only that named observer binding, its
provenance ledger, current assignment, absolute deadlines and exact predecessor
names. Historical manifests remain intact. All relative limits and control,
ACK, capture, first-failure, native-history and readiness behavior remain intact.
The preceding native qualification executes both original bypass windows in both shipped modules, with 14 draws and 30 negative controls per module. Its success does not establish game readiness. The actual command-14 branch in the prior original remains unknown because its native fault report was not recovered. That historical branch remains unknown even though this assignment's new original independently demonstrates two refresh-zero bypasses.
The focused local-runtime suite passes 44 authorization/identity/deadline
negatives, passive capture/fault and review/ACK lifecycle cases, and the actual
full composed entry with 2,429 filesystem pins and 2,429 HTTP responses.
Plain Puppeteer injection and independent public/native spawn prohibitions
prove zero Chrome. Five additional actual composed-main negatives reject wrong
binding, the old observer binding, a missing file, expired deadline and the
old assignment before runtime initialization; nine public preparation negatives
also pass. Seven capture/fault/composition/review/ACK/normal-close functions
match published 60c888e0492b08bdaac640fae3a900a35eb6fe6a exactly. The required
flock /tmp/wine-build.lock bash tools/build.sh passes and reproduces both
existing modules:
build/wine-assembly.wasm:e620f3adfc2850580004e204bc1fea495844e942806866f8ada24c215212e412build/wine-assembly.compat.wasm:66b37bd76da5a7b49c063b4eb0d44c898aaf00ff41e000a6fbd87c01edc136c8
The current closure retains 2,429 rows and all 1,856 media rows. Its five
explicit historical amendments remain the raster source, both modules, observer
and local helper; binding-ledger.json names historical, prior binding and
current hashes. runtime-pins.json, existing-inputs.json, composition evidence
and tested-inputs.json retain helper/source/media paths and SHA-256 values.
No unnamed dependency was rehashed into acceptance. The existing executable is
test/binaries/candidates/stronghold-crusader-demo/installed/App_Executables/Stronghold Crusader multiplayer demo.exe,
SHA-256 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f.
Fresh independent preflight preceded exclusive runtime-flock acquisition at
03:11:40Z. All 26 captures were personally viewed. Successful review/ACK order
was preserved through title entry, Crusader, route installation, ChooseType,
Custom Game hover and its balanced gesture, followed by bounded input-free
arrival observations. The 167 complete contiguous 64-step ACKs end at step
10,688 with frozen 16ms cadence. All 1,058 actually served responses match
their pins; compiled and slot-0-delivered WASM match the canonical e620f3…
module. Final queue is empty, active input null, buttons zero.
Native history retains 105 prefix-preserving reports through 43,338,271
boundaries, with no native fault. The original callback/request-20/setup-return
chain completes. Three draws complete: one late-clock draw stores timestamp
165952, then two refresh-zero draws witness the comparison at 42976a, native
successor 429af5 (JE at 429770), preserved timestamp 165952, epilogue and
saved caller/ESP return. Neither bypass contains a fabricated late-clock event.
A fourth draw remains pending; completed draws do not establish readiness.
The 50M/360s/2048-record/1MB limits and other relative caps remain unchanged.
Four ordinary host-frame capture brackets are retained. The first host report
is running with capture deferred at frame zero; the terminal report is
first-command-failed, with fault null. No forced render/timer/load or unique
operation-to-upload identity was introduced. These records establish ordinary
capture flow, not game readiness or gameplay pixels.
The final fresh capture, browser/route-native-boundary-9.png, is at step
10,688, SHA-256
89bb4fe560a2f8cb79b64091597f98c3be9694ea128ec05ee423715a89f37d1f.
It visibly shows Human/Lord Crusader, a map, Deathmatch Game, 10000/10000 and
a Crusader Demo row. The unchanged recognizers return unknown. The preceding
step-10,432 image is only partial setup with colored 1/2/3 buttons. An initial
inspection annotation accidentally described that preceding image for the last
capture; an explicit append-only correction retains the accurate final review.
Neither image authorizes setup controls. The next prerequisite is bounded
qualification of this fresh setup layout and its control readiness, preserving
all guards, before any separately authorized original.
The first failure is queryable in browser/reply-14.json and
browser/first-failures.jsonl; final state, native attachment reports and host
terminal evidence are retained. native-original-verification.json checks
the two actual bypass returns, no late-clock event in those draws, exact limits,
empty input and no command 15. actual-evidence-summary.json audits capture
reviews, ACK order, native prefixes, served pins and compiled module identity.
Normal Browser.close was requested at 03:16:49.956Z; Chrome
1807789/startticks 189550958 exited 0/null at 03:16:50.126Z. Independent cleanup
at 03:17:09.718Z verifies Chrome, Node 1807762/startticks 189550739 and flock
1807761/startticks 189550739 absent, HTTP 39747 and DevTools 34879 refused,
the exact profile unused and removed, and runtime/build locks free. No runtime
box was used, stopped, deleted or resumed. Shutdown ownership remains with the
coordinator. This assignment ends after tested publication and final runtime
AND file RELEASE ALLBUILDSFINISHED.
Evidence: scratch/runs/20261105-stronghold-repaired-bypass-original/.
Recovery uses Git SHA plus relevant binary diff and owned new-file patches;
existing helpers, media and modules are referenced by path and SHA-256.
No source snapshots, archives or repeated media/module copies are created.
Box ID/state/expiry: N/A (local); the coordinator retains shutdown ownership.