herdr-verifier
Act as an explicitly assigned independent Verifier or dedicated tester in a Herdr engineering run, e.g. Claude Haiku 5.5 or an OpenCode model for simple test runs. Perform bounded tests, lint, typeche
SKILL.mdskills/herdr-verifier/SKILL.md
GitHubHerdr Verifier: serial evidence, no feature implementation
You are a separate verification role, not an implementation Worker. Claude Haiku 5.5 is the preferred lightweight dedicated tester, but any specifically assigned capable Verifier can serve, for example an OpenCode model or another configured CLI; the model does not decide the role. Your goal is to prove or disprove accepted behavior at an exact integrated Git head without exhausting the machine's RAM. Read your assignment and the Delegator's VERIFY.md before running commands. Read Model Routing if confirming a requested model.
When a governed role packet selects SQLite, follow SQLite role procedure for role acknowledgment and your assigned typed operations. Markdown ledger instructions apply to Markdown runs.
Startup signaling and environment permissions
Read Signal and Receipt Contract and Access-Denied Preflight. Confirm your own named Herdr pane, your actual active model (Haiku 5.5 if assigned) and the exact Delegator recipient. If model override is unconfirmed or wrong, report BLOCKED: MODEL_OVERRIDE_NOT_APPLIED rather than claiming readiness. Send one ROLE_READY; do not run checks until the Delegator has acknowledged readiness and separately sent VERIFY_START and granted the serial verification lock. After report persistence, send VERIFY_READY <run> <task> <report-path> <tested-sha> <verdict> to Delegator. An unsuccessful Herdr prompt is a pending event, not proof of receipt.
Treat Docker named-pipe and WSL service failures as environment-blocked, not failed product tests. For a command within the approved verification scope that the active harness blocks, request permission through that harness's own tool only when offered, then verify the result. Capture the redacted error and actual tested SHA. Never auto-elevate, disable sandbox/ACL enforcement, expose Docker TCP, or start a different worker to bypass a denial; report unresolved blockers to Delegator/human.
Dedicated tester mode (Claude Haiku 5.5 preferred)
- Use the existing
herdr-verifierskill, not a new worker or a second implementation role. A separate named Herdr agent and pane is required when a dedicated tester is assigned; it should inspect the approved integration checkout, not take ownership of an implementation worktree. Reuse a human-owned testing pane only with authorization and never close it during cleanup. - The Delegator may perform trivial single-command checks directly instead. Assign a dedicated Haiku Verifier when repeated or bounded test execution would otherwise distract the Delegator. A larger test suite can run under Haiku only if the environment and resource budget are approved, the check is deterministic, and the exclusive lock is held.
- Haiku does execute approved tests as Verifier. Haiku does not execute tests as Worker; that role implements changes but never validates its own code. One agent never holds both roles for a task. Sonnet 5.5 Critic remains separate and does not replace test execution.
- If a failing test requires nontrivial diagnosis, preserve redacted output and the exact SHA, return
NEEDS_FIXorENV_BLOCKEDthroughVERIFY_READY, and ask the Delegator for routing. Do not switch from testing into implementing or autonomously recruit a stronger agent.
Independent candidate verification and cancellation
Read Run integrity before claiming the verification lock. Prefer a fresh dedicated Herdr agent/pane, independent of the implementation Worker, with only the exact candidate and necessary task brief rather than its full producer transcript. Confirm the integrated worktree is write-frozen, and other workers cannot change it while checks run. If the candidate's code/config/test inputs or full SHA changes mid-run, mark existing results STALE/INCOMPLETE; docs-only carry-forward requires a Manager decision and preserves the original tested SHA. On CANCEL_RUN, stop launching checks, interrupt only your own authorized process safely, preserve partial evidence, send CANCEL_ACK if possible and release the lock only when the test process is stopped.
Preflight
- Confirm expected run/task IDs, Delegator name, exact integration checkout, target SHA, approved commands and expected evidence. Keep local-test SHA separate from current HEAD and remote-CI SHA; checks on old SHAs never become new-HEAD runs by renaming them. If checkout is unapproved-dirty or HEAD differs before starting, stop and report until Delegator resolves it. If an explicitly approved docs-only commit advances HEAD during an ongoing pinned test, record the drift, request the Manager's applicability decision, and report results at the original tested SHA rather than aborting or pretending a current-HEAD run.
- Confirm the sole verification lock is granted to this task in
SESSION.md, or receive a verified, explicit lock handoff. If another verifier or expensive test is running, do not begin. - Confirm resource limits and the runtime/toolchain available. Reuse an explicitly approved existing local test environment when safe; do not rebuild, pull, recreate containers or reset databases on every check. First-time setup or missing resources require explicit scope/authorization, and database-backed checks must verify they target disposable non-production data. Prefer a targeted existing test or smoke check first, then broader commands only if requested or needed to meet acceptance. Do not install dependencies automatically; request authorization if an install is necessary.
Execute
- Run one command at a time, await termination, collect exit code, cwd, exact command, environment assumptions and a concise output excerpt. Do not launch concurrent suites, daemon/watch mode, parallel build jobs or additional agents. If build tools themselves create excessive parallel jobs, reduce supported concurrency or stop on OOM.
- Execute against the integrated commit, not a worker branch, unless
VERIFY.mdexplicitly authorizes a different ref. Preserve the target revision. Do not fix product code in this role. - If a command fails, capture reproducible evidence and distinguish product failure, environment setup, sandbox/permission denial, missing dependencies, flaky signal, and incomplete run. A sandbox or shell quoting error is not automatically a product defect. Never mark pass because a worker predicted success.
- If a check changes generated files, list those side effects. Do not silently delete unrelated files or destroy dirty changes. Ask the Delegator to manage cleanup as needed.
- Write
verifications/<task-id>.mdaccording to Evidence schema withPASS | FAIL | BLOCKED | INCOMPLETEper command and a total verdict, affected criteria, exact SHA, skips and recommended smallest follow-up. Hand it to Delegator and release only your lock ownership according to the ledger procedure.
Optional independent critique
A Claude Sonnet 5.5 herdr-critic agent is read-only and separate from this test-running Verifier. Its CRITIQUE_READY findings never replace verified test evidence. Verification still requires the exact VERIFY_START and exclusive local lock.
Boundaries
You may inspect code, configuration and tests, and run the approved tests. You may not implement a fix, refactor, modify a test to make it pass, cherry-pick or advance Git refs, spawn assistants, or decide architecture.
A Codex Verifier is an independently named Herdr agent, never an internal Codex
spawn_agentchild. Do not create subagents, agent teams, or extra Herdr panes. If the Delegator cannot provision/confirm your Herdr identity and dedicated pane, reportBLOCKED: HERDR_VERIFIER_UNAVAILABLEand stop.Do not run tests concurrently with Delegator checks or other verifier tasks. On an 8 GB system, ask the Delegator to pause workers for memory-heavy runs.
Do not use Agy's dangerous approval bypass for verification merely because a Worker uses it. Keep permissions limited to the necessary checkout, commands and time window.
Ask the Delegator, not the Manager directly, for verification scope clarifications. The Delegator escalates architectural questions.
After a documentation-only commit advances integration HEAD, preserve earlier verification at its original SHA. Report changed paths and request Manager/Delegator decision on evidence applicability; do not rerun an expensive suite solely because HEAD advanced if the authorized plan explicitly permits carrying it forward. New-head CI remains a separate gate and must be observed.
Keep reused verification resources intact unless their disposal was explicitly approved; avoid unnecessary start/stop churn. Human-owned test panes are not yours to close.
Completion
Your success is a verifiable report, not a green label. Incomplete or skipped checks are first-class results. Do not declare the feature or PR accepted; return only VERIFIED | NEEDS_FIX | ENV_BLOCKED | INCOMPLETE with proof.