Status: 180.C.16.11 scripted demo and acceptance-criteria catalog.
Implementation date: 2026-04-23.
This note turns the MVP alpha demo language from ADR-0005 into explicit release scripts. The scripts are the release-evidence checklist for internal MVP alpha signoff, not just descriptive prose.
Sources Reviewed#
docs/domains/bellona/extras/remote-control/adr/ADR-0005-mvp-release-artifact-and-gates.mddocs/domains/bellona/extras/remote-control/mvp-alpha-release-gate.mddocs/domains/bellona/extras/remote-control/mvp-alpha-operations-runbooks.mddocs/domains/bellona/extras/remote-control/operator-workflow-blender-browser-mvp.mddocs/domains/bellona/extras/remote-control/blender-read-only-mvp-second-macbook.mddocs/domains/bellona/extras/remote-control/blender-safe-mutation-mvp-closure.mddocs/domains/bellona/extras/remote-control/unreal-readonly-safe-mutation-mvp-closure.mddocs/domains/bellona/extras/remote-control/deployment-smoke-test-plan.mddocs/domains/bellona/extras/remote-control/network-impairment-test-plan.mddocs/domains/bellona/extras/remote-control/security-regression-test-plan.md
Script Catalog#
testing/bellona/remote-control/mvp-alpha-demo-scenarios.ts exposes
createRemoteControlMvpAlphaDemoPlan() with three scripted release-evidence
scenarios:
MVP-DEMO-01solo-creator two-Mac LAN happy pathMVP-DEMO-02reference cloud gateway pathMVP-DEMO-03safety and resilience evidence pack
Primary MVP Demo#
The primary narrative for MVP alpha signoff is MVP-DEMO-01.
It scripts the exact flow requested by 180.C.16.11:
- pair the second MacBook and prove the no-inbound topology
- query Blender scene info
- create one Blender primitive with rollback evidence
- navigate the managed browser path and capture a screenshot artifact
- approve the work and replay/export the session evidence
The committed commands for that script are:
pnpm nx remote-mac:no-inbound-smoke @bellona/mcp-gateway --skip-nx-cache --verbosepnpm nx blender:scene-info-remote-smoke @bellona/remote-host --skip-nx-cache --verbosepnpm nx blender:create-primitive-remote-smoke @bellona/remote-host --skip-nx-cache --verbosepnpm nx browser:managed-remote-smoke @bellona/remote-host --skip-nx-cache --verbosepnpm nx e2e @bellona/control-room --skip-nx-cache --verbose
Acceptance Criteria#
The primary scenario is complete only when all of the following are attached:
- paired device capability report and no-inbound topology proof
- Blender scene-info result plus gateway audit/timeline records
- Blender primitive mutation before/after output, undo checkpoint, and rollback note
- browser screenshot artifact, managed profile path, and localhost CDP proof
- operator approval record, audit export bundle, and replay artifact or transcript reference
The supporting scenarios add:
- one reference cloud deployment smoke and cloud-agent path
- the security regression output
- the network impairment output with explicit TURN limitation note
- the MVP alpha release-gate output against the assembled evidence snapshot
Release-Evidence Bundle#
The scripts are intended to produce one release-evidence bundle containing:
- command outputs and smoke logs
- audit export bundle
- timeline or replay artifact references
- approval records
- deployment health and gateway log evidence
- security and network hardening outputs
- release-gate output
Verification#
The committed automated verification is:
pnpm exec vitest run --config vitest.config.ts tests/mvp-alpha-demo-scenarios.test.ts --reporter=verbose
pnpm nx run-many -p @bellona/remote-control-testing -t lint,typecheck,test,build --skip-nx-cache --verbose
The first command proves the scripted scenarios, commands, and acceptance criteria. The second command keeps the catalog buildable in the shared remote-control testing package.