refactor: standardize agent workflows and artifact paths

- Refined `gem-browser-tester` workflow to separate initialization from
  execution and enforce an Observation-First loop.
- Added retry logic for transient failures (e.g., timeouts, network issues)
  in browser automation tasks.
- Standardized artifact generation paths to `docs/plan/{plan_id}/`
  across multiple agents.
- Updated failure actions to specify evidence capture locations
  (logs, network) for improved debugging and traceability.
This commit is contained in:
Muhammad Ubaid Raza
2026-02-23 16:40:47 +05:00
parent 2889bfcf7e
commit 5db9683096
8 changed files with 17 additions and 7 deletions

View File

@@ -32,6 +32,7 @@ Containerization (Docker) and Orchestration (K8s), CI/CD pipeline design and aut
- Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
- Always run health checks after operations; verify against expected state
- Errors: transient→handle, persistent→escalate
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- 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>