Stronghold quiet-RPC original, 2026-11-04

Evidence: scratch/runs/20261104-stronghold-quiet-rpc-original-gameplay/. Input repair: d223b191ce637894f82d2d470c2a5d60c6cdee43; cause and original observation. The actual launch Git SHA, relevant binary diff, media/module path hashes and served pins are retained in the run. No source snapshots or media/module copies were made.

The quiet-RPC repair passed its first actual obstacle. The original Custom Game gesture completed in 960 steps, including drained mouse release. The continuous owning native history observed setup return at boundary 23,329,935, callback return and Custom Game path completion at 23,336,762. Previously these returns were missing at the 40-second command timeout. This demonstrates progress in this run, not a controlled browser timing comparison.

Exact entry and dependency

The local contract now binds this stronghold-quiet-rpc-original-gameplay-2230 assignment and the actual mdk2-medium-release-gameplay-2210 dependency: current OWN 22:12:29Z, LOCAL HEAVY RELEASE 22:20:20Z and file RELEASE 22:26:57Z. Both release kinds must follow ownership; missing, foreign, quoted, stale, future and assignment-suffix records reject. Offline fixtures never produce an actual runtime release.

Before Chrome, the exact composed fresh-directory entry traversed all 2,429 pins, process binding, private ancestor flock, filesystem writes, lifecycle installation and real HTTP server creation with the real dependency gate. A plain browser mock threw at the launch wrapper, independently prohibited child spawns remained zero, and the server closed. The intended six startup commands passed actual composed-command/transport replay: unique capture names, 8,448 steps, 132 ACKs. Caller actions and fields were preflighted separately. The existing diagnostic route's lack of preset/Start readiness was explicit. All 1,016 HTTP content, cache and isolation checks passed.

The unchanged modules are normal 78a0b1d61b23428a1ae909d739440ae0de059bbbd84a69a2ad3e4c37471ad664 and compatibility 99b579cd17b57f94145df92ae6d28110f24fc284d13a1b2c0ebe3596bd10a77f. All 1,856 original media pins match. No guest code/configuration was edited.

One original and first fault

I personally viewed the complete fresh selector and startup checkpoints, the title at step 8,448, the main menu at 8,576, Crusader hover at 8,640, ChooseType at 8,768 and Custom Game hover at 8,832 before authorizing the corresponding ordinary controls. Startup step 6,400 showed Firefly Studios in this run. Personal observations and capture hashes are retained; the earlier run's logo timing is not substituted.

Custom Game's balanced gesture ACKed at 9,728. Arrival observation 256 ACKed at 9,984 with the old hover still displayed. Command 13's next 256-step observation captured a partial setup transition at 10,240 and failed at 22:38:55.233Z with first unexpected natural scene: unknown. The whole image visibly includes numbered 1/2/3 presets and “Not available in the demo” over a partially drawn setup and sword/shield background. It is not a completed setup or readiness proof. No preset selection, Start, world or ordinary gameplay is claimed.

There are 160 complete 64-step ACKs at the original 16ms, one continuous native history with 40,092,338 boundaries, 41 records, 32,268 bytes, no observer fault and no pending callback frames. Terminal input queue is empty, active/last input are null and mouse mask is zero. Native setup/callback returns and physical release drainage are established separately from visual readiness.

Offline repair and limits

The prior recognizers know only retained complete and intermediate frame identities. The new partial frame has a different full-game RGBA hash: 741b136a33e205825f23e70af83059d82dfe3b625bd869c321198ba16dec2e5c. The local helper now recognizes exactly those opaque pixels in the existing 860×668 game region of a 1200×900 capture as setup-transition-observation. Known scene identities retain precedence. Only bounded natural arrival observation admits this label; it grants no complete-layout, preset, Start or world readiness. Other unseen transition frames still reject. This is a narrow tested repair for the observed recognition fault, not a general fade classifier.

The offline regression executes the composed capture and arrival functions against the retained actual image/state. OLD returns unknown and rejects; NEW identifies the exact observation and retains arrival continuation. Pixel changes across text, presets, background and edges, other scenes, alpha and geometry reject; browser toolbar changes are irrelevant. Unknown frames, the 3,072 arrival cap, scene20 no-readiness guard and actual terminal mailbox still reject. The regression also verifies actual native returns, drained input and the unchanged boundary limit. A fresh composed entry with post-fault pins again passes the real dependency gate, plain browser mock and independent spawn prohibition with zero Chrome. Those pins are separately named and never replace the actual launch manifest.

All existing finite history, 50M-boundary/360s observer, byte/record, owner, nesting, input, ACK, aggregate-step, command/review and native readiness guards remain. No budget resets or cap raises occur. Only 9,907,662 native boundaries remain relative to the retained terminal history; subsequent progress within the original limits is unproved. Browser/bootstrap/command/cleanup remain 720/60/40/180 seconds with earlier hard cutoffs 23:40Z/23:43Z.

Focused local-contract, real-original initializer (both modules), title and route-recognition tests pass. The full flocked build passes. Three individually needed archived JSON inputs were restored with gzip -dk and verified using the released-headroom maps; the run records their original hashes. Large new released diagnostics are gzip compressed with SHA roundtrip mappings.

Closure and handoff

The first fault automatically requested normal Browser.close; Chrome 1298153, start ticks 187889108, exited code 0/signal null at 22:38:55.345Z. Node 1298132/start 187889027, external flock 1297730 and wrapper 1297739/start 187888478 are absent; wrapper exit is 0. HTTP 42225, DevTools 36237 and prelaunch mock HTTP 43613 refuse connections. The exact owned profile was removed after verifying no process used it; external flock was free at 22:39:02Z. Assignment-bound LOCAL HEAVY RELEASE was posted at 22:39:17Z. No further runtime command or second Chrome followed.

Box ID/state/expiry are NA; coordinator retains shutdown ownership. Stop after testing and publishing this repair. A separately authorized successor must preflight its own exact dependency and entry, then establish later rendering and native-budget progress before any preset/Start/world claim.