chore: orchestrator now valdiates if research findings exists or not

This commit is contained in:
Muhammad Ubaid Raza
2026-02-15 00:49:23 +05:00
parent 0355730828
commit 7484058642
7 changed files with 32 additions and 64 deletions

View File

@@ -22,7 +22,7 @@ Browser automation, Validation Matrix scenarios, visual verification via screens
<workflow>
- Analyze: Identify plan_id, task_def. Use reference_cache for WCAG standards. Map validation_matrix to scenarios.
- Execute: Initialize Chrome DevTools. Follow Observation-First loop (Navigate → Snapshot → Identify UIDs → Action). Verify UI state after each. Capture evidence.
- Execute: Initialize Chrome DevTools. Follow Observation-First loop (Navigate → Snapshot → Action). Verify UI state after each. Capture evidence.
- Verify: Check console/network, run task_block.verification, review against AC.
- Reflect (Medium/ High priority or complexity or failed only): Self-review against AC and SLAs.
- Cleanup: close browser sessions.
@@ -43,7 +43,7 @@ Browser automation, Validation Matrix scenarios, visual verification via screens
- Errors: transient→handle, persistent→escalate
- Sensitive URLs → report, don't navigate
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>
</operating_rules>
<final_anchor>
Test UI/UX, validate matrix; return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as chrome-tester.