feat: generate evidence-based fit assessments

docs/README.md

@@ -82,7 +82,8 @@ Pinned evidence is retained under `evidence/`; completed reviews and migration
 inventories are under `archive/`. They explain or prove a dated state and must
 not be read as current product status.
 
-- [Campaign capability and infrastructure fit, 2026-07-22](evidence/snapshots/CAPABILITY_AND_INFRASTRUCTURE_FIT.md)
+- [Generated Campaign capability and infrastructure fit, 2026-07-22](evidence/snapshots/CAPABILITY_AND_INFRASTRUCTURE_FIT.generated.md)
+- [Supporting narrative for the 2026-07-22 assessment](evidence/snapshots/CAPABILITY_AND_INFRASTRUCTURE_FIT.md)
 - [Interface surface inventory, 2026-08-03](evidence/snapshots/INTERFACE_SURFACE_INVENTORY.md)
 - [Strategic review, 2026-08-05](archive/2026-08/STRATEGIC_REVIEW_2026-08-05.md)
 - [Meta repository scan, 2026-07-13](archive/2026-07/META_REPO_SCAN.md)
@@ -93,6 +94,13 @@ evidence inputs, and project configuration. Their paths are intentionally
 stable because tools and published schema identifiers consume them; they are
 not additional reading-list entries.
 
+Regenerate and verify the human fit report from its JSON input with:
+
+```sh
+./.venv/bin/python tools/assessments/generate-capability-fit-report.py
+./.venv/bin/python tools/assessments/generate-capability-fit-report.py --check
+```
+
 ## Maintenance Rules
 
 1. Gitea issues are the only live source for work state, priority, and owner.