Merge main into feature 57's release branch, so it merges cleanly into main: playbooks 07 and 08 take main's #374 (feature 57)

Merge pull request 'Feature 57 (config and provisioning): designs, playbooks and glossary words into the release branch' (#373 ) from 57-config-and-provisioning into feat/57-config-and-provisioning
Feature 57 (config and provisioning): the record of its designs, playbooks and glossary words, synced with main
2026-10-16 08:22:43 +00:00 · 2026-10-16 07:35:26 +00:00 · 2026-10-16 07:22:11 +00:00 · 2026-10-13 23:56:11 +00:00 · 2026-10-13 23:53:25 +00:00 · 2026-10-13 23:45:31 +00:00
1 changed files with 0 additions and 14 deletions
@@ -4,7 +4,6 @@ status: in-progress
 code: [mesh-controller, mesh-catalog modules/mesh-delivery]
 updated: 2026-10-16
 decisions:
-  - "ADR 0395"
  - "ADR 0382"
  - "ADR 0350"
  - "ADR 0335"
@@ -390,19 +389,6 @@ only once it is built.
 A group's state is derived from its members and its composed check, and is shown, never stored apart from
 them.

-
-## A move of the trunk asks every check again
-
-*ADR 0395, changing ADR 0323 §4.* When the forge's holder hears a repository's trunk move, mesh-delivery asks the
-check of every active open pull request into that trunk against its new head at once, so a verdict is current by
-the time anyone looks. A pull request whose head no longer merges cleanly into the new head is not checked: the
-forge says so without a builder, its statuses fail naming the conflict, and it is told once on the pull request;
-its author's next push asks its check. A pull request has at most one check at a time: a check against an older trunk commit,
-waiting or running, is dropped or ended when a newer one is asked for it, as a new head already ends its old head's
-check (issue 726). The build queue keeps delivery builds first; then checks of pull requests marked ready, then the
-rest, the most recently pushed first. A pull request with no push and no ready mark for 7 days is left out until a
-push, a ready mark or a recheck wakes it. A recheck also takes a delivery that is still proposed (issue 888).
-
 ## What every transition does

 In this order, each by its owner:
Author	SHA1	Message	Date
mesh-tools	4ebbefa3fc	Merge main into feature 57's release branch, so it merges cleanly into main: playbooks 07 and 08 take main's #374 (feature 57) mesh/merge-gate head 4ebbefa3fcad merged into trunk 110bb7d1d7e1 — pass: [release feat/57-config-and-provisioning, judged by its controller 6a6628a76961] t… Details mesh/repo-check head 4ebbefa3fcad merged into trunk 110bb7d1d7e1 — pass: [release feat/57-config-and-provisioning, judged by its controller 6a6628a76961] i… Details mesh/delivery stopped: the pull request closed unmerged Details	2026-10-16 08:22:43 +00:00
mesh-tools	110bb7d1d7	Merge pull request 'Feature 57 (config and provisioning): designs, playbooks and glossary words into the release branch' (#373 ) from 57-config-and-provisioning into feat/57-config-and-provisioning mesh/merge-gate head 110bb7d1d7e1 merged into trunk c22b58143b74 — fail: head 110bb7d1d7e1 does not merge cleanly into trunk c22b58143b74: in conflict 00-M… Details mesh/repo-check head 110bb7d1d7e1 merged into trunk c22b58143b74 — fail: head 110bb7d1d7e1 does not merge cleanly into trunk c22b58143b74: in conflict 00-M… Details mesh/delivery-group group feat/57-config-and-provisioning rejected: a member's own check failed Details mesh/delivery stopped: the pull request closed unmerged Details	2026-10-16 07:35:26 +00:00
mesh-tools	6be8f6eada	Feature 57 (config and provisioning): the record of its designs, playbooks and glossary words, synced with main mesh/merge-gate head 6be8f6eada67 merged into trunk b7e22be7f55f — pass: [release feat/57-config-and-provisioning, judged by its controller cf897e89fe31] t… Details mesh/repo-check head 6be8f6eada67 merged into trunk b7e22be7f55f — pass: [release feat/57-config-and-provisioning, judged by its controller cf897e89fe31] i… Details mesh/delivery delivered Details	2026-10-16 07:22:11 +00:00
mesh-admin	b7e22be7f5	Merge pull request '57/F4: The glossary gains the words of config and provisioning (issue 653)' (#351 ) from pkg/57-f4-glossary-config-words into feat/57-config-and-provisioning	2026-10-13 23:56:11 +00:00
mesh-adminandClaude Opus 5.5	21508a7348	Answer review 237 of hq#351 (issue 653) mesh/merge-gate head 21508a73483a merged into trunk fc9edd5c75b3 — pass: the change touches no module of the mesh's graph Details mesh/repo-check head 21508a73483a merged into trunk fc9edd5c75b3 — pass: its merge-check.sh passed Details mesh/delivery delivered Details The controller holds no config value (ADR 0348 section 9), so the record mirror and the assignment no longer say it does. Name issue 683 for the Not: line, quote the old word, add the alias identifiers, define trusted, and add the homonym rows for managed and trusted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 23:53:25 +00:00
mesh-adminandClaude Opus 5.5	1f6d1b3005	Give the glossary the words of config and provisioning (issue 653) mesh/merge-gate head 1f6d1b30053b merged into trunk fc9edd5c75b3 — pass: the change touches no module of the mesh's graph Details mesh/repo-check head 1f6d1b30053b merged into trunk fc9edd5c75b3 — pass: its merge-check.sh passed Details mesh/delivery superseded: a newer head of the same pull request Details ADR 0348 makes config a domain of its own and ADR 0349 makes every value a module needs a provision placed by mesh-provisioner, but the glossary had no word for a config value, a predefined key, the provisioner client, a collection or who owns a placed file. Add them in their domains, move preference under Config, and use config value where the glossary itself said setting. "setting" is not put on a Not: line: 67 documents in force still use it in running prose, so retiring it now would fail words.py on all of them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 23:45:31 +00:00
mesh-admin	fc9edd5c75	Open the integration branch of release 57 (config and provisioning) So the packages of design 57 meet here, reviewed one by one, and reach main as one delivery group.	2026-10-13 23:39:25 +00:00