mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-02 12:11:34 +00:00
* fix(agents): make global loop breaker reachable Record loop-detector vetoes as typed no-progress outcomes so repeated blocked calls continue the existing streak without colliding with plugin or approval denials. Extract streak accounting into its own owner module and keep completed veto records out of argument reconciliation.\n\nFixes #109435. * test: harden isolated project routing Route registry-sensitive UI tests through the isolated project for both focused and broad runs, centralize the isolated file list, and register the Codex prewarm test in the full extension shard. * test(qa): prove global loop breaker runtime Drive 31 identical read attempts through the real QA Gateway agent loop and verify the typed veto streak reaches the global circuit breaker before the turn returns a final marker. * test: keep isolated UI files out of shared runs Always exclude registry-sensitive files from the shared UI project and reject broad watch targets that would span shared and isolated projects.
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 suiteis the executable frontier subset / regression loop.qa manualis the scoped personality and style probe after the executable subset is green.qa coverageprints the scenario coverage inventory from scenario YAML.
Operator workflows:
- Use the
openclaw-qa-testingskill 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.