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
@@ -326,6 +326,17 @@ wall-clock timeout.
the number of firmware ticks spent advancing one logical frame. Its limit is
tooling policy, not a guest cycle budget, runtime fault, or wall-clock
performance requirement.
- If a successful memcard bootstrap still blocks the active VM on its queued or
running native publication, the headless owner coordinates lane progress outside
machine ticks, in requested waits of at most 5 ms. The same advance retains its
request and a single 2 s outer deadline from first wait admission; wakes/reentry
do not reset it. Native 500 ms cancellation and 1 s escalation remain authoritative.
A native action-required boundary takes precedence; unresolved IO at the outer
deadline returns a memcard `restart_required` host error with a native snapshot.
Every return pauses execution and clears the host's step request. IO-only polls
and waits do not add guest ticks/frames, enlarge the 100,000 firmware-tick
watchdog, rerun bootstrap, or synchronize unrelated gameplay commits. Waiting
does not establish IO cessation or permit release of worker-owned resources.
- `capture_frame()` returns an owned clone of the canonical frame paired with
the latest successful advance. The explicit `{logical_frame_index, FrameId}`
pair is authoritative; no numeric equality or fixed offset is implied.