birdhouse-agentic-tests

List the markdown test files in the tests directory, pick the target environment (sandbox1 by default), perform the sandbox ownership preflight, then follow the test's browser-driven steps. Each run produces a verdict, video recording, screenshots, and a run directory of artifacts.

Copy tests/template.md to a new file, fill in every section with browser-achievable steps and UI-verifiable pass criteria, then run it standalone once to confirm it is followable before committing. Tests must consume runner-provided values rather than hardcoding ports or paths.

The test runner lives in the production Birdhouse environment, separate from the sandbox under test, so direct agent tool calls would hit production instead of the sandbox. Every test must interact with the sandbox exclusively through the browser UI.

sandbox1 (port 50200) is the default persistent environment, sandbox2 (port 50220) is used only when explicitly requested, and isolated runs create a fresh disposable instance via the isolated-birdhouse-web-testing skill. The choice depends on whether you need a shared stateful environment or a clean one.

A run fails if the video recording is missing, zero bytes, or structurally invalid, since recording integrity is verified before declaring success. Runs also fail if any pass criterion in the test file is not met or a fail criterion is triggered.