What problem does it solve? End-to-end testing of a tmux-orchestrating CLI is risky: tests can leak tmux servers, touch host credentials, or pass without the intended action occurring. This Skill enforces a Docker-isolated E2E boundary so tmt and tmux are exercised for real without endangering the host environment. ## Core Features & Use Cases - Docker-isolated test execution: Run the real tmt CLI and a real tmux server inside a network-isolated container via the run-e2e.mjs wrapper, with Vitest as the scenario runner. - Deterministic mock agents: Drive mock agents inside tmux panes as deterministic peers, never invoking real AI models, credentials, or network services. - Quality gate enforcement: Apply rules for causal assertions, bounded polling, cleanup verification, negative-path coverage, and CLI selection validation. - Use Case: When adding a lifecycle or cleanup change to tmt, use this Skill to write a scenario that proves teardown is idempotent by running the Docker suite twice and verifying observable absence of leaked state. ## Quick Start Ask the agent to add a Docker E2E scenario for a tmt CLI behavior and run it through the repository's documented run-e2e.mjs command.