57/K2: The controller reads, judges against and keeps the catalogue's list of predefined keys (issue 661) #323

Merged

mesh-admin merged 6 commits from pkg/57-k2-predefined-keys into feat/57-config-and-provisioning 2026-10-14 06:52:25 +00:00

Conversation 4 Commits 6 Files Changed 22

+1189 -37

6 Commits

Author	SHA1	Message	Date
mesh-adminandClaude Opus 5.5	197e60c97b	List the K2 store tests again, apart from the integration branch's new lines ... Placed above the lines both branches added at the end of the file, so the pull request merges into feat/57-config-and-provisioning without a conflict and the merged list is the union of both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 06:42:51 +00:00
mesh-adminandClaude Opus 5.5	e75c376a7d	Take the integration branch's store-test list before merging it ... The two lists added lines at the same place; taking the integration branch's here lets it merge cleanly, and the K2 store tests are listed again right after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 06:41:52 +00:00
mesh-adminandClaude Opus 5.5	fbcf44702c	Prove the list is read strictly and judges module check, the gate and registration ... Part 4: the tests of the list's reading and of the controller's commands on it (hq ADR 0348 clause 7, issue 661). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 05:48:49 +00:00
mesh-adminandClaude Opus 5.5	2941ef3695	Read the list of predefined keys strictly, and prove the build, check, gate and registration on it ... Part 3: the list's own reading (catalogue/predefined.go) and the tests of the build, module check, merge gate and registration (hq ADR 0348 clause 7, issue 661). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 05:47:44 +00:00
mesh-adminandClaude Opus 5.5	9f2e16ff70	Keep the newest trunk build's list of predefined keys, and prove each refusal ... The list itself, read strictly (catalogue/predefined.go); the controller keeps a catalogue trunk build's list in its store when its commit's generation is larger than the one kept (migration 0098), so an older build's list heard later never replaces a newer one, and loads it with its store (hq ADR 0348 clause 7, issue 661). Part 2 of 2: the new files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 05:46:49 +00:00
mesh-adminandClaude Opus 5.5	c0bee5d042	Judge every manifest against the list of predefined keys of its tree, and carry the list from a build ... Mesh and node config may hold values only for keys on a fixed, reviewed list (hq ADR 0348 clause 7, design 57 package K2, issue 661). A build reads predefined.json at the root of the repository at the commit it builds and carries it with the commit's generation; module check and the merge gate read it from the tree. (Part 1 of 2: the changes to existing files.) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 05:45:48 +00:00