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:
@@ -234,6 +234,16 @@ Reset leaves the runtime unbooted and clears its capture. It does not implicitly
|
||||
boot the cartridge again. A subsequent explicit boot may reuse the session's
|
||||
known build cartridge; an invalidated process requires an explicit new session.
|
||||
|
||||
Memcard use negotiates the provider's protocol 1.1 extension explicitly. The
|
||||
adapter projects mount/choice/state/reconcile/RAM-continuation and protected
|
||||
teardown as specified in [Project-local memcard integration](<8. Project-Local Studio State Specification.md#published-memcard-host-integration>).
|
||||
Native `memcard_error` refusal preserves structured state and the live channel;
|
||||
it does not trigger process termination or detach. `action_required` preserves
|
||||
known progress and becomes `ACTION_REQUIRED`, with the resident session retained.
|
||||
Human reclaim never supplies discard consent. Following a protected cleanup
|
||||
refusal, DEV offers a separate confirmed discard/retry action; canceling it
|
||||
preserves the process and control guard.
|
||||
|
||||
| Configurable, handshake-advertised limit | Default |
|
||||
| --- | --- |
|
||||
| Frames per advance | 600 |
|
||||
|
||||
Reference in New Issue
Block a user