agh-qa-bootstrap

Bootstrapping an isolated deterministic local QA lab requires generating a scenario workspace with durable runtime paths, ports, and Unix sockets. This approach enforces provider-home isolation and runtime config correctness to guarantee reproducible verification environments.

A canonical bootstrap manifest is a contract artifact written under the qa/ directory that serves as the single source of truth for downstream QA skills. It defines the runtime configuration and evidence scaffolding required for real-scenario QA execution.

You can seed a QA workspace with a predefined playbook by providing the playbook parameter during bootstrap. This materializes playbook-defined workspaces, knowledge files, agents, and an open task tree, replacing any legacy skeleton charter.

Yes, workspace isolation strictly requires provider-home configuration. The bootstrap process enforces provider-home isolation and validates runtime config correctness to ensure the local-first QA environment remains completely isolated and reproducible.

Downstream real-scenario QA execution requires specific evidence scaffolding including a scenario contract, behavioral charter, journey log, and provider attempt. These artifacts are generated alongside the bootstrap manifest to enforce verification standards.

You should avoid using a deterministic QA bootstrap if your local testing does not require downstream real-scenario evidence contracts or continuation-safe reuse. It is specifically designed for workflows needing strict provider-home isolation and reproducible verification.