Phase 11 turned testing and demonstration into related but distinct systems. Scenario definitions describe behavior, fixtures provide safe deterministic data, and a Debug-only runner drives the production interface through named checkpoints.
The same scenario can support assertions, screenshots, or a paced preview without placing fixture controls in the Release build. A passing scenario can prove that a button appeared, state changed, or a task was stored, but it cannot prove that real people understand or prefer the interface.
Later working-tree evidence expands this approach across unit tests, scenario smoke tests, accessibility checks, strict-concurrency builds, Release builds, widget builds, visual regression, monetization invariants, and privacy audits.
Physical speech, widget taps, background audio, Reminders, live StoreKit behavior, accessibility review, and real-human observation remain distinct evidence types and outside the automated launch claim.
← Back to SayList