openclaw/qa
Peter Steinberger 5c449ecaef
refactor(matrix): unify message action parsing (#143759)
Keep public action fields and context in the existing lazy runtime owner. Preserve validation order, account selection, read authorization, media scope and provider lifecycle; reject inherited permissions operation names with the existing unsupported-operation diagnostic.
2026-09-10 04:25:33 -07:00
..
convex-credential-broker chore(deps): refresh four seven-day-cooled packages (#140732) 2026-09-06 21:45:52 -07:00
scenarios refactor(matrix): unify message action parsing (#143759) 2026-09-10 04:25:33 -07:00
frontier-harness-plan.md
maturity-scores.yaml fix(maturity): land Windows, ChromeOS, and durable-work corrections (#142066) 2026-09-08 15:39:21 -07:00
README.md
scenarios.md

QA Scenarios

Seed QA assets for the private qa-lab extension.

Files:

  • scenarios/index.yaml - canonical QA scenario pack, kickoff mission, and operator identity.
  • scenarios/<theme>/*.yaml - one runnable scenario per YAML file.
  • frontier-harness-plan.md - big-model bakeoff and tuning loop for harness work.
  • convex-credential-broker/ - standalone Convex v1 lease broker for pooled live credentials.

Key workflow:

  • qa suite is the executable frontier subset / regression loop.
  • qa manual is the scoped personality and style probe after the executable subset is green.
  • qa coverage prints the scenario coverage inventory from scenario YAML.

Operator workflows:

  • Use the openclaw-qa-testing skill for QA Lab live lanes, Convex credential pool operations, and WhatsApp live credential setup/replacement.

Keep this folder in git. Add new scenarios here before wiring them into automation.