Local QA Command Surface Verification
Script: scripts/qa/verify_command_surface.py
The command-surface verifier guards the local testing harness itself. It checks
that the public test-local.sh usage text, unified local-validation.sh
runtime, retained lower-level local-validation/qa.sh scopes, key testing docs, and
evidence-summary report groups stay aligned.
Command
./scripts/local-validation/qa.sh test command-surface
This scope is also part of:
./scripts/local-validation/qa.sh test governance
What It Checks
- canonical
test-local.shcommands are listed in usage text - canonical
local-validation.shcommands and smoke scopes are listed in usage text - retained lower-level
local-validation/qa.shsmoke and test scopes are listed in usage text - the low-memory
./scripts/test-local.sh no-heavylane remains documented - core local testing commands are documented in the testing docs
- evidence-summary report groups include the required local QA batteries
- workflow contracts, staging/local parity, stub scenario, and seed-to-workflow coverage scopes stay wired into the low-memory command surface
It intentionally includes ./scripts/local-validation/qa.sh test docs-index,
./scripts/local-validation/qa.sh test docs-render, and
./scripts/local-validation/qa.sh test web-route-coverage so new QA docs, route-level
manual coverage gates, and docs build/render wiring remain visible in the
command surface.
The low-memory local QA fidelity scopes are:
./scripts/local-validation/qa.sh test workflow-contracts
./scripts/local-validation/qa.sh test staging-parity
./scripts/local-validation/qa.sh test stub-scenarios
./scripts/local-validation/qa.sh test seed-workflow-coverage
The high-fidelity PR QA runtime commands are:
./scripts/local-validation.sh full
./scripts/local-validation.sh up
./scripts/local-validation.sh smoke all
./scripts/local-validation.sh rebuild merchant-api
./scripts/local-validation.sh ports
full is the one-command Linux-local validation surface. It runs automated
checks, boots the stack with duplicate boot smoke suppressed, runs deep smoke,
writes JSON/Markdown summaries under .dev-logs/full-local-validation/, and
prints ports for manual QA.
Boundary
This proves that QA command/document/report wiring is internally consistent. It does not prove that the underlying product behavior tests pass.