fix(headless): wait for memcard bootstrap IO progress
Intrepid/Prometeu/Runtime/pipeline/head There was a failure building this commit
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:
@@ -320,6 +320,22 @@ as a game frame. Idle IO polling leaves guest counters/input unchanged. Reconcil
|
||||
accepts no replacement path, validates expected identity before changes, preserves
|
||||
RAM/continuation/original retained results and does not rerun initialization.
|
||||
|
||||
When successful bootstrap remains blocked by its pending native publication, the
|
||||
owner coordinates lane progress within the same advance, outside machine ticks,
|
||||
with requested waits of at most 5 ms. This does not apply to an unrelated gameplay
|
||||
commit. Native deadlines remain 500 ms for cancellation and 1 s for stop/escalation,
|
||||
measured from the original request admission. One additional 2 s deadline from
|
||||
first wait entry in an `advance_frame` does not reset on wake/reentry or extend
|
||||
those deadlines. Existing native action-required/fault boundaries take precedence.
|
||||
If the dependency remains pending at the outer deadline without such a boundary,
|
||||
the advance returns `stop:host_error`, exact known `completed` progress, and
|
||||
`error.code:memcard_error` with `details.operation:advance`,
|
||||
`details.reason:restart_required` and `details.state` holding the native snapshot.
|
||||
The guest finishes paused with the host step request cleared. This preserves
|
||||
worker ownership until actual cessation, the 100,000-tick frame watchdog, transport
|
||||
responsiveness and cancellation between frames; it introduces no intraframe
|
||||
cancellation, guest fault, simulated progress, command replay or new protocol shape.
|
||||
|
||||
Runtime qualification uses neutral PBX/ABI fixtures, real distinct processes and
|
||||
an isolated extracted distribution. It proves SUCCESS, termination, exact readback
|
||||
without resave and stable appId across cartridge versions. Consumer source-language
|
||||
|
||||
Reference in New Issue
Block a user