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
This commit is contained in:
parent
c4cedab945
commit
521d3cec4c
4 changed files with 25 additions and 3 deletions
13
SCOPE.md
13
SCOPE.md
|
|
@ -184,3 +184,16 @@ from their authoritative systems.
|
|||
3. `session_memory/README.md` — current operational capabilities.
|
||||
4. `docs/DESIGN-session-memory.md` — detailed design and Kaizen correlation.
|
||||
5. `workplans/` — implementation history and future work.
|
||||
|
||||
## 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.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue