SystemOS Cartridge Switch Orchestrator
This commit is contained in:
@@ -0,0 +1,86 @@
|
||||
---
|
||||
id: PLN-0157
|
||||
ticket: system-os-cartridge-switch-orchestrator
|
||||
title: Introduce SystemOS Game Switch Target Contract
|
||||
status: open
|
||||
created: 2026-07-05
|
||||
ref_decisions: [DEC-0039]
|
||||
tags: [runtime, os, lifecycle, game, cartridge, architecture]
|
||||
---
|
||||
|
||||
## Briefing
|
||||
|
||||
DEC-0039 requires Game-to-Game switching under Home/Hub to be owned by SystemOS.
|
||||
Before destructive replacement can be implemented, Hub/Firmware/SystemOS need a
|
||||
small explicit contract for "launch this resolved Game target as a replacement"
|
||||
that is separate from direct boot and from loader internals.
|
||||
|
||||
## Objective
|
||||
|
||||
Introduce a SystemOS-owned Game switch request/target abstraction that can carry
|
||||
a resolved cartridge path or game-library entry from Hub/Home into the switch
|
||||
orchestrator without making the loader or userland the lifecycle authority.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- Source decision: DEC-0039.
|
||||
- Builds on DEC-0037 and DEC-0038 as already implemented.
|
||||
- Must be implemented before PLN-0158, PLN-0159, and PLN-0161.
|
||||
|
||||
## Scope
|
||||
|
||||
- Define a minimal Game switch target type, such as `GameSwitchTarget` or
|
||||
`CartridgeLaunchTarget`, in the SystemOS/Firmware boundary.
|
||||
- Route Hub game-library launch actions through that target contract instead of
|
||||
treating a path as an implicit lifecycle operation.
|
||||
- Keep direct boot/debug boot paths separate from SystemOS Game switching.
|
||||
- Add tests proving the target preserves cartridge identity/path without
|
||||
starting lifecycle replacement by itself.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not implement destructive replacement in this plan.
|
||||
- Do not add `.pmc`, final catalog UX, or a new launcher UI.
|
||||
- Do not change direct CLI/debug boot behavior.
|
||||
- Do not add background execution.
|
||||
|
||||
## Execution Method
|
||||
|
||||
1. Inspect `crates/console/prometeu-system/src/services/game_library.rs`,
|
||||
`crates/console/prometeu-system/src/programs/prometeu_hub/prometeu_hub.rs`,
|
||||
and `crates/console/prometeu-firmware/src/firmware/firmware_step_hub_home.rs`.
|
||||
2. Add a minimal launch target model at the SystemOS/Firmware boundary:
|
||||
- resolved cartridge path;
|
||||
- optional app_id/title metadata if already available;
|
||||
- no loader-owned lifecycle policy.
|
||||
3. Update Hub action plumbing so `SystemProfileAction::LaunchGame` carries the
|
||||
resolved target type or maps immediately into it at the firmware boundary.
|
||||
4. Add a placeholder SystemOS/Firmware entry point for Game switching that
|
||||
accepts the target but still delegates to the existing load path until
|
||||
PLN-0158 changes replacement behavior.
|
||||
5. Add unit tests for target construction and path propagation.
|
||||
6. Keep direct `BootTarget::Cartridge` behavior unchanged.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- There is an explicit type or function contract representing a resolved
|
||||
SystemOS Game switch target.
|
||||
- Hub/Home no longer treats a raw path as lifecycle authority.
|
||||
- The loader remains a materialization step, not the switch orchestrator.
|
||||
- Direct boot/debug boot code paths remain separate and behaviorally unchanged.
|
||||
- Tests prove target identity is carried without implicitly closing or loading a
|
||||
Game.
|
||||
|
||||
## Tests
|
||||
|
||||
- `cargo test -p prometeu-system`
|
||||
- `cargo test -p prometeu-firmware`
|
||||
- `cargo test -p prometeu-host-desktop-winit`
|
||||
- `cargo clippy -p prometeu-system -p prometeu-firmware -p prometeu-host-desktop-winit --all-targets -- -D warnings`
|
||||
|
||||
## Affected Artifacts
|
||||
|
||||
- `crates/console/prometeu-system/src/services/game_library.rs`
|
||||
- `crates/console/prometeu-system/src/programs/prometeu_hub/prometeu_hub.rs`
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware_step_hub_home.rs`
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware.rs`
|
||||
+98
@@ -0,0 +1,98 @@
|
||||
---
|
||||
id: PLN-0158
|
||||
ticket: system-os-cartridge-switch-orchestrator
|
||||
title: Terminate Resident Game Before Switching Cartridges
|
||||
status: open
|
||||
created: 2026-07-05
|
||||
ref_decisions: [DEC-0039]
|
||||
tags: [runtime, os, lifecycle, game, cartridge, architecture]
|
||||
---
|
||||
|
||||
## Briefing
|
||||
|
||||
DEC-0039 defines `Game A -> Home -> Game B` as destructive replacement. The
|
||||
current same-Game resume flow keeps the resident Game session alive; switching
|
||||
to a different Game must instead close/remove that resident session and create a
|
||||
fresh session for the new Game.
|
||||
|
||||
## Objective
|
||||
|
||||
Implement the SystemOS lifecycle/session operation that terminates the current
|
||||
resident Game before loading a different Game cartridge.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- Source decision: DEC-0039.
|
||||
- Requires PLN-0157 target contract.
|
||||
- Should be implemented before PLN-0159 and PLN-0161.
|
||||
|
||||
## Scope
|
||||
|
||||
- Add a controlled resident Game termination/replacement operation to SystemOS
|
||||
lifecycle/session services.
|
||||
- Optionally emit a cooperative terminate/close/save lifecycle event when the
|
||||
current event model can carry it, but do not block replacement on it.
|
||||
- Remove the previous Game from resident/resumable state.
|
||||
- Remove the previous Game VM session before activating the new Game.
|
||||
- Clear or reassign app-scoped state that cannot leak into the new Game:
|
||||
session VM, open handles, pending lifecycle state, input barrier/pending
|
||||
input, audio active app state, render ownership, telemetry/debug/crash state.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not preserve Game A for rollback.
|
||||
- Do not implement failed-load recovery beyond surfacing errors; that is
|
||||
PLN-0159.
|
||||
- Do not add background execution or multiple resident Games.
|
||||
- Do not build final launcher UX.
|
||||
|
||||
## Execution Method
|
||||
|
||||
1. Inspect lifecycle/session state in:
|
||||
- `crates/console/prometeu-system/src/os/lifecycle.rs`;
|
||||
- `crates/console/prometeu-system/src/os/facades/sessions.rs`;
|
||||
- `crates/console/prometeu-system/src/services/foreground`;
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware_step_hub_home.rs`;
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware_step_load_cartridge.rs`.
|
||||
2. Add a `replace_resident_game` or equivalent operation that:
|
||||
- finds the current resident Game;
|
||||
- marks its task/process closed or stopped according to existing lifecycle
|
||||
semantics;
|
||||
- removes the resident Game entry from foreground stack/lifecycle state;
|
||||
- removes its VM session.
|
||||
3. Ensure same-Game resume still bypasses replacement and remains governed by
|
||||
DEC-0037.
|
||||
4. Update game launch from Home so launching a different app_id triggers
|
||||
replacement before load.
|
||||
5. Ensure render ownership transitions away from the old Game before the new
|
||||
Game becomes foreground.
|
||||
6. Add focused tests for resident Game termination and session removal.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- Launching a different Game from Home closes/removes the resident Game rather
|
||||
than resuming it.
|
||||
- The previous Game VM session is absent before the new Game is made active.
|
||||
- Same-Game selection still resumes the existing resident Game.
|
||||
- A cooperative close/terminate event, if added, is non-blocking.
|
||||
- No previous Game VM, handle, lifecycle, render, or debug state is reused by
|
||||
the new Game.
|
||||
|
||||
## Tests
|
||||
|
||||
- `cargo test -p prometeu-system`
|
||||
- `cargo test -p prometeu-firmware`
|
||||
- `cargo clippy -p prometeu-system -p prometeu-firmware --all-targets -- -D warnings`
|
||||
- Add tests for:
|
||||
- different Game launch removes previous resident session;
|
||||
- same Game launch resumes existing resident session;
|
||||
- old Game task/process state is closed/stopped;
|
||||
- old Game session cannot be resolved after replacement starts.
|
||||
|
||||
## Affected Artifacts
|
||||
|
||||
- `crates/console/prometeu-system/src/os/lifecycle.rs`
|
||||
- `crates/console/prometeu-system/src/os/facades/sessions.rs`
|
||||
- `crates/console/prometeu-system/src/services/foreground`
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware_step_hub_home.rs`
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware_step_load_cartridge.rs`
|
||||
@@ -0,0 +1,86 @@
|
||||
---
|
||||
id: PLN-0159
|
||||
ticket: system-os-cartridge-switch-orchestrator
|
||||
title: Recover Failed Game Switches Back To Home
|
||||
status: open
|
||||
created: 2026-07-05
|
||||
ref_decisions: [DEC-0039]
|
||||
tags: [runtime, os, lifecycle, game, cartridge, architecture]
|
||||
---
|
||||
|
||||
## Briefing
|
||||
|
||||
DEC-0039 rejects preserving Game A after a switch begins. If Game B fails to
|
||||
load, the system must discard partial Game B state and return to Home/Hub with a
|
||||
diagnostic, not attempt rollback to Game A.
|
||||
|
||||
## Objective
|
||||
|
||||
Implement controlled failed-switch recovery to Home/Hub after destructive Game
|
||||
replacement begins.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- Source decision: DEC-0039.
|
||||
- Requires PLN-0157 target contract.
|
||||
- Requires PLN-0158 resident Game termination/session removal.
|
||||
|
||||
## Scope
|
||||
|
||||
- Detect load/init failure while switching to a different Game.
|
||||
- Discard any partial new Game task/session/window/render/input/audio state.
|
||||
- Return firmware/SystemOS to Home/Hub.
|
||||
- Log or expose a diagnostic that Home can surface or tests can assert.
|
||||
- Ensure previous Game is not restored after switch failure.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not implement transactional rollback.
|
||||
- Do not preserve the previous Game after switch begins.
|
||||
- Do not design final user-facing error UI.
|
||||
- Do not change direct boot failure behavior unless needed to keep paths
|
||||
separate.
|
||||
|
||||
## Execution Method
|
||||
|
||||
1. Inspect existing load failure flow in
|
||||
`crates/console/prometeu-firmware/src/firmware/firmware_step_load_cartridge.rs`.
|
||||
2. Add a switch-specific failure outcome or context flag that distinguishes
|
||||
SystemOS Game switching from direct boot load.
|
||||
3. On switch load failure:
|
||||
- remove partial new VM session/task/process if created;
|
||||
- clear partial cartridge-scoped state;
|
||||
- transition to `HubHome` instead of app crash when appropriate for switch
|
||||
recovery;
|
||||
- log a diagnostic containing target identity/path and failure summary.
|
||||
4. Preserve existing direct boot and explicit load failure tests unless a direct
|
||||
boot path intentionally still goes to crash.
|
||||
5. Add tests for bad Game B after Game A was already terminated.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- Failed `Game A -> Home -> Broken Game B` returns to Home/Hub.
|
||||
- Previous Game A is not resident, resumable, or restored.
|
||||
- Partial Game B VM session/task/process state is removed or closed.
|
||||
- A diagnostic is logged or otherwise observable.
|
||||
- Existing direct boot/debug boot failure semantics remain separate.
|
||||
|
||||
## Tests
|
||||
|
||||
- `cargo test -p prometeu-firmware`
|
||||
- `cargo test -p prometeu-system`
|
||||
- `cargo test -p prometeu-host-desktop-winit`
|
||||
- `cargo clippy -p prometeu-system -p prometeu-firmware -p prometeu-host-desktop-winit --all-targets -- -D warnings`
|
||||
- Add tests for:
|
||||
- switch failure returns Home;
|
||||
- old Game not restored;
|
||||
- partial new session cleanup;
|
||||
- direct boot failure path remains unchanged.
|
||||
|
||||
## Affected Artifacts
|
||||
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware_step_load_cartridge.rs`
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware_step_hub_home.rs`
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware.rs`
|
||||
- `crates/console/prometeu-system/src/os/facades/sessions.rs`
|
||||
- `crates/console/prometeu-system/src/os/lifecycle.rs`
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
id: PLN-0160
|
||||
ticket: system-os-cartridge-switch-orchestrator
|
||||
title: Add Dummy Boy Visual Switch Test Cartridge
|
||||
status: open
|
||||
created: 2026-07-05
|
||||
ref_decisions: [DEC-0039]
|
||||
tags: [runtime, os, lifecycle, game, cartridge, architecture]
|
||||
---
|
||||
|
||||
## Briefing
|
||||
|
||||
DEC-0039 requires minimum evidence using two distinct test cartridges. The
|
||||
existing stress cartridge proves execution/logging but is not visually distinct
|
||||
enough for switch validation. A second cartridge, `dummy-boy`, must render an
|
||||
oscillating-color square.
|
||||
|
||||
## Objective
|
||||
|
||||
Add a simple `test-cartridges/dummy-boy` cartridge that renders a visible square
|
||||
with changing colors so Game switching can prove visual/session identity.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- Source decision: DEC-0039.
|
||||
- Can be implemented independently of PLN-0157 through PLN-0159.
|
||||
- Required before PLN-0161 end-to-end validation.
|
||||
|
||||
## Scope
|
||||
|
||||
- Add `test-cartridges/dummy-boy/manifest.json`.
|
||||
- Generate or add `test-cartridges/dummy-boy/program.pbx`.
|
||||
- Add empty or minimal assets payload if the loader requires `assets.pa`.
|
||||
- Implement Dummy Boy behavior:
|
||||
- Game cartridge identity distinct from stress;
|
||||
- deterministic visible square;
|
||||
- color oscillates across frames;
|
||||
- no dependency on final launcher UX.
|
||||
- Add build/generation documentation or tests so the cartridge can be
|
||||
regenerated safely if needed.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not add final game content.
|
||||
- Do not add `.pmc`.
|
||||
- Do not depend on host screenshots for the first validation unless an existing
|
||||
harness already supports it.
|
||||
- Do not change stress cartridge behavior.
|
||||
|
||||
## Execution Method
|
||||
|
||||
1. Inspect the stress cartridge and any PBX generator tooling:
|
||||
- `test-cartridges/stress-console`;
|
||||
- `crates/tools/pbxgen-stress`;
|
||||
- bytecode assembler helpers in `crates/console/prometeu-bytecode`.
|
||||
2. Choose the smallest maintainable generator path:
|
||||
- extend existing PBX generator if appropriate; or
|
||||
- add a focused `pbxgen-dummy-boy` tool; or
|
||||
- add deterministic generated PBX with source instructions.
|
||||
3. Create `manifest.json` with unique `app_id`, title `Dummy Boy`, Game mode,
|
||||
and version.
|
||||
4. Generate `program.pbx` that renders the square and advances color over
|
||||
frames.
|
||||
5. Add tests or smoke checks that the cartridge is discoverable by games-root
|
||||
discovery.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- `test-cartridges/dummy-boy` exists and loads as a Game cartridge.
|
||||
- Dummy Boy has a unique `app_id` and title distinct from Stress.
|
||||
- Dummy Boy renders a visible square.
|
||||
- Square color changes deterministically over time.
|
||||
- Games-root discovery sees both Stress and Dummy Boy.
|
||||
- Existing stress cartridge remains unchanged.
|
||||
|
||||
## Tests
|
||||
|
||||
- `cargo test -p prometeu-hal`
|
||||
- `cargo test -p prometeu-system`
|
||||
- `cargo test -p prometeu-firmware`
|
||||
- Run any cartridge generator tests added by this plan.
|
||||
- Add or update tests for games-root discovery including Dummy Boy.
|
||||
|
||||
## Affected Artifacts
|
||||
|
||||
- `test-cartridges/dummy-boy/manifest.json`
|
||||
- `test-cartridges/dummy-boy/program.pbx`
|
||||
- `test-cartridges/dummy-boy/assets.pa` if required
|
||||
- `crates/tools/*` cartridge generator tooling if needed
|
||||
- `crates/console/prometeu-system/src/services/game_library.rs` tests if needed
|
||||
+93
@@ -0,0 +1,93 @@
|
||||
---
|
||||
id: PLN-0161
|
||||
ticket: system-os-cartridge-switch-orchestrator
|
||||
title: Validate Stress To Dummy Boy Game Switch End To End
|
||||
status: open
|
||||
created: 2026-07-05
|
||||
ref_decisions: [DEC-0039]
|
||||
tags: [runtime, os, lifecycle, game, cartridge, architecture]
|
||||
---
|
||||
|
||||
## Briefing
|
||||
|
||||
DEC-0039 requires proof that `Game A -> Home -> Game B` creates a fresh Game
|
||||
session and does not present stale state from Game A. The minimum evidence is
|
||||
switching from Stress to Dummy Boy.
|
||||
|
||||
## Objective
|
||||
|
||||
Add end-to-end validation for `Stress -> Home -> Dummy Boy` through the real
|
||||
Hub/Home flow, proving lifecycle, VM session, cartridge identity, and render
|
||||
ownership switch correctly.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- Source decision: DEC-0039.
|
||||
- Requires PLN-0157 target contract.
|
||||
- Requires PLN-0158 destructive replacement.
|
||||
- Requires PLN-0159 failed-switch recovery for negative path assertions.
|
||||
- Requires PLN-0160 Dummy Boy cartridge.
|
||||
|
||||
## Scope
|
||||
|
||||
- Add firmware/system tests that drive:
|
||||
- launch Stress from games root;
|
||||
- request Home;
|
||||
- launch Dummy Boy;
|
||||
- assert Stress session is gone;
|
||||
- assert Dummy Boy session is active;
|
||||
- assert cartridge identity and render ownership belong to Dummy Boy.
|
||||
- Add a negative end-to-end test for broken Game B returning to Home if not
|
||||
already covered by PLN-0159.
|
||||
- Use existing test platform/render submission inspection where possible.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not require final launcher UX.
|
||||
- Do not add screenshot-based host automation unless existing test utilities
|
||||
make it cheap and deterministic.
|
||||
- Do not implement additional Game-to-Game variants beyond Stress to Dummy Boy.
|
||||
|
||||
## Execution Method
|
||||
|
||||
1. Inspect existing firmware tests in
|
||||
`crates/console/prometeu-firmware/src/firmware/firmware.rs`.
|
||||
2. Reuse existing `TestGameRoot` or games-root helpers to expose Stress and
|
||||
Dummy Boy.
|
||||
3. Drive input through Hub/Home selection rather than calling cartridge load
|
||||
directly when possible.
|
||||
4. Assert lifecycle/session invariants:
|
||||
- old task closed/stopped;
|
||||
- old VM session removed;
|
||||
- new VM session created;
|
||||
- foreground owner is new Game;
|
||||
- current cartridge identity is Dummy Boy.
|
||||
5. Assert render invariants:
|
||||
- render ownership epoch belongs to Dummy Boy app identity;
|
||||
- stale Stress submissions are not accepted after switch;
|
||||
- latest observable Game frame comes from Dummy Boy when render inspection is
|
||||
available.
|
||||
6. Add a focused test for failure path if missing after PLN-0159.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- End-to-end test proves Stress can be replaced by Dummy Boy from Home.
|
||||
- Stress is not resumable after switching to Dummy Boy.
|
||||
- Dummy Boy receives a fresh VM session.
|
||||
- Cartridge identity and active render ownership are Dummy Boy after switch.
|
||||
- Failure path returns Home and does not restore Stress.
|
||||
- Tests are deterministic and do not rely on manual host interaction.
|
||||
|
||||
## Tests
|
||||
|
||||
- `cargo test -p prometeu-firmware`
|
||||
- `cargo test -p prometeu-system`
|
||||
- `cargo test -p prometeu-host-desktop-winit`
|
||||
- `cargo clippy -p prometeu-system -p prometeu-firmware -p prometeu-host-desktop-winit --all-targets -- -D warnings`
|
||||
|
||||
## Affected Artifacts
|
||||
|
||||
- `crates/console/prometeu-firmware/src/firmware/firmware.rs`
|
||||
- `crates/console/prometeu-system/src/services/game_library.rs`
|
||||
- `test-cartridges/dummy-boy`
|
||||
- Host/render test utilities if needed
|
||||
+93
@@ -0,0 +1,93 @@
|
||||
---
|
||||
id: PLN-0162
|
||||
ticket: system-os-cartridge-switch-orchestrator
|
||||
title: Specify Game Switch Contract And Direct Boot Separation
|
||||
status: open
|
||||
created: 2026-07-05
|
||||
ref_decisions: [DEC-0039]
|
||||
tags: [runtime, os, lifecycle, game, cartridge, architecture]
|
||||
---
|
||||
|
||||
## Briefing
|
||||
|
||||
DEC-0039 must be reflected in the canonical runtime specs after the operational
|
||||
contract is implemented or alongside implementation. The spec must distinguish
|
||||
same-Game resume, Game replacement under SystemOS, and direct boot/debug boot.
|
||||
|
||||
## Objective
|
||||
|
||||
Update the canonical runtime documentation to describe SystemOS Game cartridge
|
||||
switching and to keep direct boot/debug boot separate from Home/Hub-driven Game
|
||||
replacement.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- Source decision: DEC-0039.
|
||||
- Can be implemented before code if the spec is written as intended behavior.
|
||||
- Should be reconciled after PLN-0157 through PLN-0161 if implementation names
|
||||
differ from initial plan names.
|
||||
|
||||
## Scope
|
||||
|
||||
- Update relevant files under `docs/specs/runtime/`, especially:
|
||||
- `12-firmware-pos-and-prometeuhub.md`;
|
||||
- `13-cartridge.md`;
|
||||
- `14-boot-profiles.md`;
|
||||
- `09-events-and-concurrency.md` if lifecycle events need mention;
|
||||
- `10-debug-inspection-and-profiling.md` if debugger separation needs note.
|
||||
- Document:
|
||||
- SystemOS authority for Game switching;
|
||||
- destructive replacement semantics;
|
||||
- optional non-blocking terminate/save event;
|
||||
- fresh VM session for new Game;
|
||||
- failed switch recovery to Home/Hub;
|
||||
- direct boot/debug boot separation;
|
||||
- test cartridge evidence requirement.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not document `.pmc` or final catalog UX as required.
|
||||
- Do not specify background execution.
|
||||
- Do not revise DEC-0037 or DEC-0038 semantics.
|
||||
- Do not write lesson material; housekeeping will decide lessons after
|
||||
execution.
|
||||
|
||||
## Execution Method
|
||||
|
||||
1. Read the runtime spec files listed in scope.
|
||||
2. Add a Game switching section in the most appropriate canonical spec file.
|
||||
3. Cross-reference existing Home/Hub, cartridge, boot profile, and debug boot
|
||||
sections.
|
||||
4. Ensure language is English and normative enough for future implementers:
|
||||
`MUST`, `MUST NOT`, `MAY`, `SHOULD`.
|
||||
5. Verify no non-English agenda language leaks into specs.
|
||||
6. Run docs grep checks for the newly introduced terms.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- Specs explicitly distinguish:
|
||||
- same-Game pause/resume;
|
||||
- Game A to Game B destructive replacement;
|
||||
- direct boot/debug boot.
|
||||
- Specs state that SystemOS owns Game switching policy.
|
||||
- Specs state that a new Game gets a fresh VM session.
|
||||
- Specs state that failed switch returns Home/Hub and does not restore the old
|
||||
Game in v1.
|
||||
- Specs mention Dummy Boy or equivalent two-cartridge evidence only as test
|
||||
evidence, not as runtime feature.
|
||||
- Documentation is English.
|
||||
|
||||
## Tests
|
||||
|
||||
- `rg -n "Game switch|destructive replacement|direct boot|Dummy Boy|VM session" docs/specs/runtime`
|
||||
- `discussion validate`
|
||||
- Run code tests only if this plan is implemented together with code changes:
|
||||
`cargo test -p prometeu-system -p prometeu-firmware`
|
||||
|
||||
## Affected Artifacts
|
||||
|
||||
- `docs/specs/runtime/12-firmware-pos-and-prometeuhub.md`
|
||||
- `docs/specs/runtime/13-cartridge.md`
|
||||
- `docs/specs/runtime/14-boot-profiles.md`
|
||||
- `docs/specs/runtime/09-events-and-concurrency.md`
|
||||
- `docs/specs/runtime/10-debug-inspection-and-profiling.md`
|
||||
Reference in New Issue
Block a user