fix(headless): wait for memcard bootstrap IO progress
Intrepid/Prometeu/Runtime/pipeline/head There was a failure building this commit

Coordinate bounded native publication progress during frame advance while preserving watchdogs, guest budgets and resource ownership. Add controlled and packaged reopen regressions, clarify the runtime specs, and retain qualification evidence.
This commit is contained in:
2026-11-10 23:26:40 +00:00
parent 49d7fca0b7
commit c3589be1ad
34 changed files with 5904 additions and 5 deletions
@@ -371,6 +371,21 @@ and an explicit player policy through `boot_with_memcard_choice`. Its boot loop
waits for actual worker progress with a bounded watchdog timeout; frame execution
remains independent of real-time pacing.
During a headless frame advance, a successful bootstrap hook may still depend on
its native presentation publication. Only while that dependency blocks the active
VM and the corresponding IO remains queued or running, the host owner waits on
the shared lane's progress signal, outside firmware/VM ticks. Each requested wait
is at most 5 ms. Polling preserves the request's original 500 ms cancellation and
1 s stop/escalation deadlines. A single additional 2 s owner deadline starts on
first entry to this wait within an advance and never resets on wake or reentry.
It does not extend the native deadlines. Native media action stops the advance
with exact progress; if the dependency outlives the owner deadline without a
terminal boundary, it returns a native `memcard_error` for `advance` with reason
`restart_required` and the current media state. Neither outcome confirms IO
cessation or releases worker-owned buffers, media or locks. An ordinary gameplay
commit that does not block the VM does not activate this wait. Pure IO polling
and waiting do not advance guest counters or input and do not pace game frames.
Before guest boot, firmware presents persistent, fresh-memory-only and (when
available) existing-save-memory-only choices. Choosing no card does not bypass
snapshot reservation. Leaving a resident game with dirty RAM requires an explicit