What problem does it solve? Unit tests often miss bugs that live in wiring, serialization, subprocess handling, paths, locks, or persisted state. This Skill validates behavior that only appears when real project boundaries meet, such as CLI plus store, filesystem behavior, config loading, migrations, or process/supervisor interactions, while keeping tests isolated and repeatable. ## Core Features & Use Cases - Real boundary testing: Exercise the actual CLI, store, filesystem, or process path under test instead of mocking the boundary itself. - Isolation discipline: Build temp roots, temp config/home paths, unique ports, and deterministic clocks so tests never touch the operator's live state. - Dual evidence modes: Emit a qa-result profile for executed QA checks or a production-handoff profile when adding or changing production integration tests. - Use Case: After changing how the CLI writes to the message store, run an integration check against a temp store root to prove the CLI-plus-store contract holds, then report the exact command, result, and covered ref as qa-result evidence. ## Quick Start Ask the agent to run an integration test of the CLI and store boundary using an isolated temp root and report the executed command and result as qa-result evidence.
