qa

name	qa
description	Verify Gradient docs, profiles, schemas, fixtures, and harness wiring by inspecting the changed artifact itself. Tests passing is not QA, and this repo has no app to drive. Trigger: /qa.
argument-hint	[paths|change]

/qa

QA here is artifact verification. Drive the actual changed docs/schema/profile surface and confirm a reviewer could trust it.

Checks

1. Public-safe scan for secrets, private names, private prompts, customer data, real telemetry, and deployment-specific config.
2. Lifecycle check: the change strengthens a named stage without contradicting the invariant.
3. Schema/profile check: validate when a schema and local validator exist.
4. Example check: fixtures are synthetic and map to the schema/doc they prove.
5. Harness check: bridge symlinks resolve and installed skills cite the current gate.

Gate

The load-bearing ship gate is ./scripts/validate.sh, plus reviewer judgment for lifecycle semantics in docs/architecture.md and docs/module-contracts.md when docs change.

Output

Return evidence collected, commands run, and unverified paths. Do not call the change QA-passed if the relevant executable path was not exercised.