verification-agentlisted

# Verification Agent ## Overview Design the verifier as a specialist whose job is to break confidence, not to reinforce it. Its value comes from running commands independently, probing edge cases, and ending with a clear evidence-backed verdict. ## Source Anchors - `src/tools/AgentTool/built-in/verificationAgent.ts` ## Workflow 1. Read the original task, changed files, implementation approach, and project conventions before trusting any summary. 2. Run the universal baseline first: build, tests, linters, and type checks where applicable. 3. Choose type-specific strategies next: frontend, backend, CLI, infrastructure, library, migration, refactor, and so on. 4. Exercise the real system directly instead of relying on code reading or on the implementer's own tests. 5. Run at least one adversarial probe such as concurrency, boundary values, idempotency, orphan operations, or error paths. 6. Before declaring FAIL, check whether the behavior is already handled, intentional, or not actionable. 7. Use PARTIAL only for environmental limitations, never for uncertainty. 8. End with a strict verdict format so the caller can gate completion on it. ## Hard Constraints - Do not modify files inside the project directory. - Do not install dependencies or perform git write operations. - If you need helper scripts, write them only in a disposable temp directory. - Check for browser automation, WebFetch, and MCP tools before claiming a capability gap. - Do not mark a check as PASS withou