Feature 57 (config and provisioning): release hq's record #376

Closed

mesh-tools wants to merge 6 commits from feat/57-config-and-provisioning into main

pull from: feat/57-config-and-provisioning

merge into: :main

:main

:test/ssh-proof-g14

:pb-cleanup-after-delivery

:design/36-items-the-mesh-did-not-place

:decision/0189-collects-again

:decision/0133-0134-migrations-and-deploy-facts

:issue/092-genesis-registry-trust

:issue/091-machine-ports-in-manifests

Conversation 3 Commits 6 Files Changed 91

+1629 -721

mesh-tools commented 2026-10-16 08:16:59 +00:00

Member

Copy Link

Copy Source

Feature 57's hq part (glossary words, release notes): the release branch feat/57-config-and-provisioning (reviewed and merged there: #373) into main. Delivery group 57 bundle A with mesh-sdk, mesh-host and mesh-controller.

Feature 57's hq part (glossary words, release notes): the release branch feat/57-config-and-provisioning (reviewed and merged there: #373) into main. Delivery group 57 bundle A with mesh-sdk, mesh-host and mesh-controller.

mesh-tools added 6 commits 2026-10-16 08:16:59 +00:00

Open the integration branch of release 57 (config and provisioning) ... fc9edd5c75

So the packages of design 57 meet here, reviewed one by one, and reach main as one delivery group.

Give the glossary the words of config and provisioning (issue 653) ... 1f6d1b3005

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>

Answer review 237 of hq#351 (issue 653) ... 21508a7348

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>

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 b7e22be7f5

Feature 57 (config and provisioning): the record of its designs, playbooks and glossary words, synced with main 6be8f6eada

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 110bb7d1d7

mesh-tools commented 2026-10-16 08:17:14 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 110bb7d1
Judged: head 110bb7d1d7e1 merged into trunk c22b58143b74

• mesh/merge-gate: FAIL — head 110bb7d1d7 does not merge cleanly into trunk c22b58143b: in conflict 00-META/process/07-feature-branches.md, 00-META/process/08-small-fixes.md
• mesh/repo-check: FAIL — head 110bb7d1d7 does not merge cleanly into trunk c22b58143b: in conflict 00-META/process/07-feature-branches.md, 00-META/process/08-small-fixes.md

Run by the build seat on novox as build-1792138628558944947 (builds --log build-1792138628558944947).

head 110bb7d1d7e1 does not merge cleanly into trunk c22b58143b74: in conflict 00-META/process/07-feature-branches.md, 00-META/process/08-small-fixes.md

**Merge check** at `110bb7d1` Judged: head `110bb7d1d7e1` merged into trunk `c22b58143b74` - `mesh/merge-gate`: **FAIL** — head 110bb7d1d7e1 does not merge cleanly into trunk c22b58143b74: in conflict 00-META/process/07-feature-branches.md, 00-META/process/08-small-fixes.md - `mesh/repo-check`: **FAIL** — head 110bb7d1d7e1 does not merge cleanly into trunk c22b58143b74: in conflict 00-META/process/07-feature-branches.md, 00-META/process/08-small-fixes.md Run by the build seat on novox as `build-1792138628558944947` (`builds --log build-1792138628558944947`). ``` head 110bb7d1d7e1 does not merge cleanly into trunk c22b58143b74: in conflict 00-META/process/07-feature-branches.md, 00-META/process/08-small-fixes.md ```

mesh-tools commented 2026-10-16 08:17:15 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/hq@110bb7d1d7e1 — stopped since 2026-10-16T08:27:25Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Group feat/57-config-and-provisioning, in order: novox/hq@110bb7d1d7 → novox/mesh-controller@6a6628a769 → novox/mesh-host@b546d4316c → novox/mesh-sdk@67ee945af5

• novox/mesh-controller@6a6628a769 before novox/mesh-host@b546d4316c: built by, over engine before controller
• novox/mesh-controller@6a6628a769 before novox/mesh-sdk@67ee945af5: built by

Transitions

• 2026-10-16 08:17 (new) → proposed (announced): novox/hq#376's head announced
• 2026-10-16 08:17 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-16 08:17 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
• 2026-10-16 08:27 rejected → stopped (closed): the pull request closed unmerged

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@110bb7d1d7e1` — **stopped** since 2026-10-16T08:27:25Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Group** `feat/57-config-and-provisioning`, in order: novox/hq@110bb7d1d7e1 → novox/mesh-controller@6a6628a76961 → novox/mesh-host@b546d4316c3b → novox/mesh-sdk@67ee945af5d1 - novox/mesh-controller@6a6628a76961 before novox/mesh-host@b546d4316c3b: built by, over engine before controller - novox/mesh-controller@6a6628a76961 before novox/mesh-sdk@67ee945af5d1: built by **Transitions** - 2026-10-16 08:17 (new) → proposed (announced): novox/hq#376's head announced - 2026-10-16 08:17 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 08:17 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-16 08:27 rejected → stopped (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools referenced this pull request 2026-10-16 08:22:54 +00:00

Bring main's playbooks 07 and 08 (#374) into feature 57's release branch, so it merges into main #377

mesh-tools commented 2026-10-16 08:24:55 +00:00

Author

Member

Copy Link

Copy Source

Closed, with #377: feature 57's release goes from branch release/57-config-and-provisioning (the release branch merged with main, tree 280fca3b, reviewed in #377), as one commit on top of main.

Closed, with #377: feature 57's release goes from branch release/57-config-and-provisioning (the release branch merged with main, tree 280fca3b, reviewed in #377), as one commit on top of main.

mesh-tools closed this pull request 2026-10-16 08:24:56 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#376