feat(studio): integrate memcard persistence and headless controls
Persist cartridge identity and slot configuration, add MemcardBoot and the MemcardBuffer SDK, and consume the runtime's negotiated memcard host controls with protected teardown. Qualify save/reopen and version upgrades through distinct configured runtime processes. Include specs, examples, regression evidence and the consolidated discussion lesson.
This commit is contained in:
@@ -411,4 +411,12 @@ effects. Fatal traps/host failures and unfinished fuel exhaustion fail the
|
||||
session, block gameplay and retain the existing crash envelope, without retry,
|
||||
rollback or compensation. HALT is OS termination, not successful hook return.
|
||||
Existing capability/service rules apply, without auto-save, flush, disk wait,
|
||||
transition veto or reason argument. MemcardBoot and persistence are separate.
|
||||
transition veto or reason argument. MemcardBoot and persistence follow the dedicated memcard chapter.
|
||||
|
||||
|
||||
## Memcard integration
|
||||
|
||||
The [Memcard Bootstrap and SDK contract](<26. Memcard Bootstrap and SDK Specification.md>)
|
||||
defines the additional [MemcardBoot] marker, exact signature, neutral once-only
|
||||
bootstrap, project identity/slot validation and complete installed mem ABI.
|
||||
Its requirements apply in addition to this chapter; pause/resume remain independent.
|
||||
|
||||
Reference in New Issue
Block a user