blacksmith-testbox

Remote CI-parity validation resolves GitHub Actions failures by running commands in a hosted Testbox that matches the CI environment, ensuring OS, dependencies, and injected secrets align. It warms a reusable Testbox ID and executes repo checks remotely.

Install and authenticate the Blacksmith CLI, run the warmup command from the repository root to get a reusable Testbox ID, then execute checks inside it. Running from the repo root preserves the workspace sync for consistent remote testing results.

You only need a remote Testbox for CI-parity checks requiring hosted services, injected secrets, or matching workflow images. Following repo guidance, you can avoid unnecessary remote runs and execute commands locally when parity or remote state is not required.

The Testbox uses a safe sync model with delta syncing and gitignore behavior. You must re-run install and build steps on the Testbox when repo changes require it, ensuring the remote workspace state matches your local development environment.

Non-interactive browser authentication allows automated agents to authenticate the Blacksmith CLI without manual intervention. This enables agent-triggered login to establish Testbox access for remote CI-parity execution in automated workflows.

Testbox workflow dispatch and artifact download require a warmed-up Testbox ID and CLI authentication. Limitations include the need to run from the repository root to maintain workspace sync and re-running build steps when delta syncing does not capture required state changes.