Caesar III current local native route — 2026-11-17
Evidence: scratch/runs/20261117-caesar3-current-native-assignment2-food/.
An authored native fixture reproduced a permanent-binding defect before any
original was launched. A finite left press was consumed and its independent
release changed the main caption to UP after DOWN. A new complete capture
and fresh review then attempted the ordinary Escape route. The next intent
was cancelled before its handler with owner/epoch/queue/device/window changed,
despite the same live HWND generation, process and thread. The permanent native
owner lease incorrectly retained the first caption.
test/run.js now compares native owner identity independently of that caption
for the native-reviewed-context-v1 binding. Each intent still verifies the
complete fresh captions, controls, focus, modal, native identities and mapping;
pending delivery still verifies its full context. The older strict scene route
retains its original comparison. No guest or renderer semantic was changed.
tools/caesar3-current-native.py reads published compiler/runtime/controller
helpers from exact Git objects and seals the source and compiled module before
qualification and any game clock. Its authored controls include fullscreen
mapping, actual native dialog buttons, native keyboard consumption, independent
physical release, caption transition followed by fresh review and native Quit,
and actual late capture with terminal refusal of every later request. Synthetic
fixture attestations do not authorize an original-game action.
The original option permits one local registered caesar3_demo invocation at
default game speed with real ticks, a 2400-second native limit, independently
prearmed 2420-second watchdog and 240-second Quit reserve. Every input requires
one personally reviewed full image and nonce. Confirmation, independent UP and
complete observation retain 500/1750/3000 ms limits and 5/30-second game/menu
freshness. A returned capture is only an observation for personal inspection,
never an automatically inferred objective. UNKNOWN closes the invocation with
no later interactive request, replay, rebind or second original.
Repair c3ad88c572a088d5ed32a68212fea22286766ed5 was published on main after corrected authored qualification and a successful locked build with an actual parent wait and both EOFs. An earlier build tool session returned 143 before finishing; its cause and explicit parent EOFs are unknown. It is not the build pass. The final exact published Git-only qualification then passed again, with sealed source, module and child/Worker inheritance. The retained module is cff5da9a64e3df960918df28ae7e06bd1db7cfae49d189f4281d82ea09e7f274.
Original first boundary
Exactly one fresh local original was launched. Its personally inspected complete
800×600 frame showed the Roman title background, black margins and a blank
central plate. The sole intended action was a neutral title-dismiss left click
at 400,500. The frame was 14.9 seconds old at DOWN, within the unchanged
30-second menu limit. The permanent bind succeeded. The host handler applied
the press, but native consumption was not confirmed within 500 ms: the guard
returned CANCELLED, reason immutable deadline expired, consumed:false and
nativeMessage:null. This supplies no proof that the guest handled the press.
The independently prearmed physical UP returned successfully 1419.2 ms after the intent began, inside 1750 ms. Only then did the caller publish permanent UNKNOWN. The request log contains capture, bind, input and that independent release, with zero later requests. No rebind, replay, second original, gameplay test launch, native Quit attempt or speculative game repair followed. Assignment 1, Victory/Clerk, Assignment 2, granary, wheat and food consequences were not reached. Historical promotion evidence remains separate.
The supervisor sent SIGTERM for host cleanup. Native OS wait was 0 with both
EOFs, but the native exit recorder explicitly says cancelled: SIGTERM and
there is no normal native exit callback. This is not native Quit. The
independent watchdog and outer parent each actually joined 0 with both EOFs;
descriptors closed, the owned runtime PIDs were absent and port 41263 closed.
No box was created: ID null, state NOT_CREATED, expiry null, stop receipt N/A.
The existing full local installation supplied all 112 mounted data files plus
the original EXE and DLL. EXE SHA-256 remained
d7c73f21d3837b1fc465a6035f4fea6ab5a7eddf62907c72c4dd076a5193d236.
The launcher's direct-directory inventory hashed and rechecked 38 files; it
did not recursively inventory the other 76 Wavs files before the clock. The
final evidence records all 114 files, with that timing limitation explicit.
No media/configuration/clock/state edit or invented save was used. Evidence
retains exact Git identity, relevant excluded worktree diff, helper patches,
module, logs, waits and only four named selected full screenshots; no source,
media or capture archive was made. /home stayed above the 1.5 GB floor at
the recorded checks; no RAM gate or workers were used.
Next work is authored qualification of this original's native consumer timing under the unchanged 500 ms contract, and a recursive preclock media inventory. This original is permanently closed and supplies no saved continuation or authorization for another original invocation.