build: generate work-record index from staged sources
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
This commit is contained in:
parent
70ff24197a
commit
8a7275c65f
4 changed files with 29 additions and 0 deletions
13
SCOPE.md
13
SCOPE.md
|
|
@ -355,3 +355,16 @@ The checked-in definition remains disabled pending workstation/hub acceptance,
|
|||
owner activation and the first unassisted fire. This source integration does
|
||||
not establish an active automation. Consumers can reuse the existing schedule,
|
||||
execution queue and profile contract rather than add another scheduler.
|
||||
|
||||
|
||||
## Staged work-record generator adoption
|
||||
|
||||
The tracked `.generated-work-records.json` opts this repository into the shared
|
||||
pre-commit generation lane. `make generated-work-records` uses the isolated
|
||||
`.generated-work-records.mk` recipe and the Custodian adapter to render from
|
||||
staged Markdown with the existing State Hub renderer. `make
|
||||
generated-work-records-check` verifies the staged result without writes.
|
||||
Unstaged source edits are preserved; unstaged generated-file edits and unresolved
|
||||
conflicts stop the commit. The existing generated-only guard and secret scan
|
||||
remain in place. This adoption covers WORK-RECORDS.md only; other owner indexes
|
||||
retain their own generators. It makes no schedule or public-release change.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue