diff --git a/.generated-work-records.json b/.generated-work-records.json new file mode 100644 index 0000000..9f787ac --- /dev/null +++ b/.generated-work-records.json @@ -0,0 +1 @@ +{"version":1,"repo_slug":"activity-core"} diff --git a/.generated-work-records.mk b/.generated-work-records.mk new file mode 100644 index 0000000..f185845 --- /dev/null +++ b/.generated-work-records.mk @@ -0,0 +1,8 @@ +# Explicit opt-in recipe; no environment files or external make includes. +CUSTODIAN_SOURCE ?= /home/worsch/the-custodian +GENERATED_REPO_SLUG ?= activity-core +.PHONY: generated-work-records generated-work-records-check +generated-work-records: + python3 "$(CUSTODIAN_SOURCE)/scripts/generate_staged_work_records.py" --repo . --repo-slug "$(GENERATED_REPO_SLUG)" +generated-work-records-check: + python3 "$(CUSTODIAN_SOURCE)/scripts/generate_staged_work_records.py" --repo . --repo-slug "$(GENERATED_REPO_SLUG)" --check diff --git a/Makefile b/Makefile index 82cda4b..4275631 100644 --- a/Makefile +++ b/Makefile @@ -127,3 +127,10 @@ agents-update: ## Update agents via kaizen-agentic agents-validate: ## Validate agents via kaizen-agentic @echo "Validating agents..." @kaizen-agentic validate agents/ + +# CUST-WP-0079-T05: staged-source generation; hook uses the isolated recipe. +.PHONY: generated-work-records generated-work-records-check +generated-work-records: + $(MAKE) --no-print-directory -f .generated-work-records.mk generated-work-records +generated-work-records-check: + $(MAKE) --no-print-directory -f .generated-work-records.mk generated-work-records-check diff --git a/SCOPE.md b/SCOPE.md index e37ce20..78f9266 100644 --- a/SCOPE.md +++ b/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.