Files
prometeu-runtime/discussion/lessons/DSC-0072-headless-memcard-reopen-io-progress/evidence/qualification/qualification-context.json
T
bquarkz c3589be1ad
Intrepid/Prometeu/Runtime/pipeline/head There was a failure building this commit
fix(headless): wait for memcard bootstrap IO progress
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.
2026-11-10 23:26:40 +00:00

14 lines
1.1 KiB
JSON

{
"sourceHead": "49d7fca0b725a0a261cda09bf5e924102c84fe31",
"decision": "DEC-0071",
"plan": "PLN-0202",
"owner": "runtime/headless",
"baselineProbe": "../baseline/review-summary.json",
"originalRuntimeOnlyBoundary": "Studio consumer source/build/tests and Zelda pilot are owned by the Studio AI. No consumer checkout is a provider fixture.",
"redEvidence": "red-controlled-release.log",
"redOutcome": "Old optimized host returns FrameAdvanceWatchdogExpired while channel-controlled presentation is held. Debug timing can allow IO completion before its tick watchdog.",
"controlledTest": "Channel entry milestone proves pending publication; controller observes owner response for 300 ms then permits IO, below the native 500 ms cancellation threshold.",
"hostTimerTest": "Explicit instants prove a shared 2 s outer timer across wakes/reentry; native 1 s escalation takes precedence in an actually blocked storage integration.",
"machineCounters": "Neutral presentation reader completes first frame at logicalFrameIndex=1/tickIndex=2; ticks depend on the fixture, not the Zelda reproduction."
}