Adopt staged WORK-RECORDS generation and catch the index up.

The generated index had drifted from the workplan files. The opt-in lets
the pre-commit hook rebuild WORK-RECORDS.md in the same commit as the
workplan it indexes.

Assistant: grok
Assistant-Session: 01a17f9d-fe9d-7d72-9a22-6304f1a2a790

SCOPE.md

@@ -377,6 +377,18 @@ tests, image construction, and Forgejo image publication.
 - activity-core **ACT-ADR-005** — `ops_run` is the fleet ops claim queue; not issue-core
 - `workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md` — Forgejo-only + projection boundary
 
+## Generated work-record index
+
+This repository opts into staged-source WORK-RECORDS.md generation through
+`.generated-work-records.json` and the isolated `.generated-work-records.mk`
+recipe. `make generated-work-records` reuses the State Hub renderer through
+the Custodian adapter; `make generated-work-records-check` verifies byte-exact
+agreement with staged Markdown. The pre-commit hook uses the isolated recipe,
+preserves unstaged index edits by refusing them, and retains the generated-only
+commit guard. It does not contact the hub, alter workplan statuses, or grant
+deployment authority. This consumes shared tooling; it does not make this
+repository the provider of the generator capability.
+
 ## Local orientation brief policy — 2026-10-21
 
 `.custodian-brief.md` is a local, ignored State Hub orientation snapshot. Refreshing