stage-09-verification-agent-setup

Automated PRD verification uses git-diff to compare builder output against an allowed baseline after each phase, generating per-phase checker configs and an Agent B configuration to enforce deterministic build scripts.

A two-strike retry policy allows an automated verification agent to fail builder output once, trigger a retry, and then halt the pipeline if the second automated check against the git-diff baseline still detects drift.

Setting up per-phase checkers requires providing stage inputs to generate phase-specific baseline, functional checks, and expected outcomes, preventing scope drift across subsequent build stages.

Yes, generating Agent B verification configuration requires inputs from stage 8, stage 7, and stage 0 to properly construct the per-phase checkers and manual preamble for Phase N+1.

Yes, two-stage verification supports both automated agent checks using git-diff ground-truth and a manual preamble configuration to guide Phase N+1 work.

Builder output drifts when phase-specific baseline and functional checks are missing, allowing unintended changes; applying per-phase checkers compares git-diff against allowed changes to prevent this.