Caesar III retained status observation and fresh native route — 2026-11-12
RESULT
The actual status-observation blocker was repaired and causally exercised: command 20049 (software-north-back-2) encountered TimeoutError: API absolute deadline on its status GET, retained its acknowledged process/command/start identity, then observed that same command exit 0 with complete output and a positive native ACK. No command POST or physical input was replayed and no second browser was opened. Later ordinary inputs remained usable only after that authoritative completion. Evidence: scratch/runs/20261112-caesar3-controller-deadline-food-1310/actual-deadline-recovery-20049.json and the API journal.
Assignment 2 food was not reached. This fresh route ended at a full captured 122 residents, December 500 BC, Pleasing the Gods tutorial (final-native-growth). There was no new Victory, promotion, Assignment 2 entry, granary, wheat delivery or saved continuation. The earlier accepted native Victory → Clerk → Assignment 2 / Senate 30-of-30 result in caesar3-compact-senate-jobs-20261112.md remains intact and is not attributed to this run.
Transport change and controls
Repair commit 89f32287b on main adds opt-in retain_status=True to tools/api_command_custody.py. Previously the requester marked the transport terminal on the first observation failure; its bounded recovery could then read remote exit 0 but still rejected continuation. The opt-in path records recoverable GET failures without releasing custody, observes only the same acknowledged command identity, and permits later commands only after authoritative successful terminal output. It retains the original absolute completion bound, allows at most three additional failed status reads, and keeps unresolved custody closed to new commands. Unknown/mismatched POST acknowledgement, identity mismatch, unknown/nonzero/signalled/OOM/truncated terminal output and native ACK failure remain refusals. POST is never retried. Request runtime is validated as an integer from 1 through 600 seconds, independently of the 55-minute sandbox lease.
The run's actual requester adds a durable command-pending.json before submission, replacing it with the acknowledged identity and removing it only after matching completion. Observation failure does not authorize another local requester to submit gameplay. This wiring is run-specific; the transport feature remains opt-in for other callers.
Validation before allocation: 13 focused transport tests; actual emitted command-file/consumer controls for delayed status, unknown POST, and rejected native ACK; actual extracted browser action controls for released input, unknown release/no later capture, and wrong owner/no input; actual startup/mount/complete staged closure preflight. The final focused test strengthens delayed status with a byte-dribbling response that avoids idle timeout but triggers the exact API absolute deadline. All 13 tests passed again. Locked flock /tmp/wine-build.lock bash tools/build.sh passed twice. Logs: transport-tests-final.log, emitted-controls.log, actual-emitted-controls.json, actual-input-controls.json, startup-test.log, build.log, build-final.log.
Native observations
Used one ordinary fresh compact route on the frozen module. Reserved the Senate footprint and protection frontage before initial housing. Fire and collapse caused real capacity losses before the engineering unlock. Rebuilt both prefectures, built two engineer posts, and completed the Senate on its reserved starter-road site for 200 denarii after clearing the actually refused footprint cells. No road warning/staffing panel was captured for this new Senate; earlier 30/30 staffing is not carried forward.
Cleared twelve additional plots individually, reviewed each full fresh frame, and built all twelve for 120 denarii. Ordinary immigration then produced the native October population milestone at exactly 100, followed by 102 in November. Built six connected western branch road cells and five accepted branch housing plots. Remaining cleared branch cells were not built before cleanup. The final live interval reached 122 and the Gods tutorial. The immediate native route still required further protected occupied capacity and promotion; this run does not isolate an immigration formula or establish a game/emulator food blocker.
No population, resources, food, clock, configuration or media writes, forced guest calls, DemoSave enablement or fabricated continuation were used. Construction refusals were not counted as successful inputs. Browser owner and released-input guards remained enforced.
RECOVERY and newly exposed cleanup blocker
Box bx_mve4ehkm was created privately at 13:14:59Z with an independently prearmed immutable 55-minute watchdog; original expiry was 2026-11-12T14:09:58.738Z. Provision's actual parent joined. All 690 frozen runtime files were reverified after browser shutdown. Module remained 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17; original EXE remained d7c73f21d3837b1fc465a6035f4fea6ab5a7eddf62907c72c4dd076a5193d236, with the DLL112data installation closure unchanged.
The gameplay reserve correctly refused the first normal-quit request before any POST at 14:07:14Z. A separately authorized cleanup-only quit was submitted once as command 49485, then authoritatively exited 1: native command-186-failure.json says assert(Date.now()<deadline-30000) at browser action(). The cleanup command was not replayed. The browser's gameplay action deadline also gates quit, consuming the cleanup reserve instead of permitting normal closure. The browser's finally path nevertheless closed Chrome with code 0 / no signal; its actual parent joined with code 1, both output EOFs. Process absence, removed profile and closed server port were independently verified. This is a precise new lifecycle blocker; it is not a successful browser-owner exit claim.
After that terminal refusal, a separate disposal-only transport performed runtime verification, output compression/retrieval and normal box stop. It did not reset gameplay custody or emit game input. Retrieved and hash-verified 1,240 unique output files, referring to 372 already recovered raw/compressed capture paths. Output-only transfer SHA-256: 7620105a07e27f739b48228d75d0703673e19e555b0c2186474f894d02b75fd3. No source/media archive was made. retrieval-verified.json, final-remote-summary.json, closed-inspection.txt, and the recovered native failure/wait files preserve the distinctions above.
Normal stop receipt stop_95067746785b4dde completed at 14:08:33.551Z, forced:false, error:null; final state archived, archiveAfter:null (no remaining expiry). stop-confirmed.json records this. Independent watchdog actual wait returned 0 with both EOFs. The outer local start execution returned 143 and did not write manager-parent-wait.json; that missing actual-parent receipt must not be fabricated or described as passed.
Disk headroom fell below the 1.5 GB floor during final output recovery. Verified duplicate raw PNGs were removed, retaining exact compressed originals. All 186 closed unique compressed captures were losslessly consolidated into unique-captures.xz (157,717,320 bytes); every member was reread and hash-verified before its individual compressed duplicate was removed. unique-captures.json maps exact member paths and hashes; extract that container under the run directory before opening those frames. This is a recorded floor breach, not compliance evidence. Source recovery uses the recorded Git base and binary patches, never a source-tree snapshot.
Next work: separate lifecycle quit from the gameplay action deadline while keeping all owner/release/unknown-input guards; ensure the outer parent can actually join throughout the lease; then use the repaired requester for the still-unfinished native Assignment 2 granary/wheat objective. Do not restart from an invented save or claim this run supplied A2 food.