coulomb/whynot-design
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Adopt staged WORK-RECORDS generation and catch the index up.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
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:
tegwick 2026-10-28 00:31:32 +01:00
parent a79a4d803e
commit f351d46d81
4 changed files with 26 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
.generated-work-records.json Normal file
View file

@ -0,0 +1 @@
{"version":1,"repo_slug":"whynot-design"}

8
.generated-work-records.mk Normal file
View file

@ -0,0 +1,8 @@
# Explicit opt-in recipe; no environment files or external make includes.
CUSTODIAN_SOURCE ?= /home/worsch/the-custodian
GENERATED_REPO_SLUG ?= whynot-design
.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

13
SCOPE.md
View file

@ -33,3 +33,16 @@ whynot-design exists to provide the capability described in INTENT.md.
- Start with: INTENT.md
- Agent instructions: AGENTS.md
- Workplans: workplans/
## 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.

4
WORK-RECORDS.md
View file

@ -10,6 +10,7 @@
| --- | --- | --- | --- | --- |
| workplan | WHYNOT-WP-0001 | finished | — | workplans/WHYNOT-WP-0001-statehub-bootstrap.md |
| workplan | WHYNOT-WP-0002 | finished | — | workplans/WHYNOT-WP-0002-designbook-stack-adapters.md |
| workplan | WHYNOT-WP-0004 | finished | — | workplans/WHYNOT-WP-0004-forgejo-npm-migration.md |
| task | WHYNOT-WP-0001-T01 | done | — | workplans/WHYNOT-WP-0001-statehub-bootstrap.md |
| task | WHYNOT-WP-0001-T02 | done | — | workplans/WHYNOT-WP-0001-statehub-bootstrap.md |
| task | WHYNOT-WP-0001-T03 | done | — | workplans/WHYNOT-WP-0001-statehub-bootstrap.md |
@ -24,4 +25,7 @@
| task | WHYNOT-WP-0002-T09 | done | — | workplans/WHYNOT-WP-0002-designbook-stack-adapters.md |
| task | WHYNOT-WP-0002-T10 | done | — | workplans/WHYNOT-WP-0002-designbook-stack-adapters.md |
| task | WHYNOT-WP-0002-T11 | done | — | workplans/WHYNOT-WP-0002-designbook-stack-adapters.md |
| task | WHYNOT-WP-0004-T01 | done | — | workplans/WHYNOT-WP-0004-forgejo-npm-migration.md |
| task | WHYNOT-WP-0004-T02 | done | — | workplans/WHYNOT-WP-0004-forgejo-npm-migration.md |
| task | WHYNOT-WP-0004-T03 | done | — | workplans/WHYNOT-WP-0004-forgejo-npm-migration.md |
| intake | WHYNOT-IN-0001 | open | yellow | intakes/intakes.md |