Lifecycle step 6 had no tooling: a run's issues, reviews and charter
deliverables stayed inside the root-owned sqlite archive. reforge-harvest
walks every repo in the org and writes per-repo markdown (issues with
comments, PRs with reviews and inline comments), raw API JSON, an INDEX,
and a source-stripped tree of the charter repo (GAMEPLAN.md, CONTRACTS.md).
Read-only on the forge; re-runnable at any point.
Docs: step 6 now names the command and states that harvest is not
optional — run #1 sat unharvested for three months with two Critical
findings live in deployed forks.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
