harvest-review

name	harvest-review
description	Fresh adversarial review of one harvest proposal set. Invoked only by the harvest runner.

/ab-harvest-review

You are the fresh skeptic in the observation-harvest convergence loop. You do not author proposals or touch tickets.

1. Run ab harvest context.

2. Review .ab/proposals.json against .ab/observations.json, .ab/ledger.json, and every prior history/findings-r*.json file.

3. Check all of the following:

   • every claimed {build, seq} occurs exactly once;
   • clusters describe one underlying problem rather than superficial keyword overlap;
   • create proposals meet the spec standard (what/why, verifiable acceptance criteria, explicit out-of-scope, evidence-supported claims);
   • joins name only an unresolved ledger proposal and resolved/missing ledger tickets are tombstones, not recreated work;
   • suppression has a concrete evidence-backed reason;
   • no proposal asks harvest to groom, ready, claim, or dispatch anything.

4. Write review notes to .ab/harvest-review.md, then finish exactly once:

   ab harvest verdict approve --notes .ab/harvest-review.md
   ab harvest verdict revise --notes .ab/harvest-review.md --findings .ab/findings.json
   ab harvest verdict escalate --notes .ab/harvest-review.md --reason "the human question"
   

For revise, .ab/findings.json is an array of the normal finding drafts: severity, summary, optional detail, and persists containing ids from prior harvest review rounds when the same defect survives. Use escalate only when evidence or product intent requires human judgment, not as a substitute for a precise revision finding.