What problem does it solve? A screenshot of a launched window only proves an app drew once, not that its message bus, orchestrator, and input pipeline are alive. This Skill prevents false "build complete" claims by requiring a proven end-to-end interaction round-trip before an Ordo app can be reported as done. ## Core Features & Use Cases - Launch Verification: Starts the built binary, confirms it runs without panicking, and captures startup output plus a screenshot of the Tauri/React studio UI. - Round-Trip Proof: Drives a real UI interaction through a Tauri invoke command or HTTP control API and captures evidence that the runtime resolved it and the UI re-rendered. - Debt Gate Enforcement: Blocks completion until the deferred-debt list is empty, all COUPLE markers are removed, and the code compiles clean under -Dwarnings. - Use Case: As the final step of an Ordo build pipeline, run this gate before telling a user their app is finished, ensuring "complete" means "runs" rather than "drew once." ## Quick Start Run the Ordo launch proof on the finished build and confirm the app launches, one real UiInput round-trip completes with captured evidence, and no deferred debt or COUPLE markers remain.
