Issue 339: the merge order against mesh-host #61, used-as-found as a behaviour change, the review's follow-ups #236

Merged

mesh-admin merged 4 commits from issues/339-review-follow-ups into main 2026-10-08 23:55:40 +00:00

Conversation 1 Commits 4 Files Changed 2

+106 -6

mesh-admin commented 2026-10-08 22:29:19 +00:00

Contributor

Copy Link

Copy Source

Follow-up to #234. Do not merge without review.

• Merge order corrected. The diagnosis said either PR could merge first. It now says that holds for the two PRs of this issue, but not against mesh-host #61: #63 merges first, then #61 is rebased onto it, drops its own guard, and carries its below-home rules (an archive or a file written into, below a root: never home) into #63's placement_guard.go.
• Behaviour change recorded: a directory found on a machine is now used as found. That is a new quiet failure (a module that cannot write its data directory) until the node-engine follow-up lands, and the record names the first cases that would hit it.
• The review's follow-ups are listed: the controller PR (step-ca root only, every line end, more system paths) and the node-engine PR (WARNING, an unhealthy directory resource that raises the module's condition and holds the walk's gate, mesh-host hand-over, and the guard's new paths).
• The report's line on PEM blocks now says that only step-ca's root may hold lines.

All four checks pass locally with the catalogue's word list.

Follow-up to #234. Do not merge without review. - **Merge order corrected.** The diagnosis said either PR could merge first. It now says that holds for the two PRs of this issue, but not against `mesh-host` #61: #63 merges first, then #61 is rebased onto it, drops its own guard, and carries its below-home rules (an archive or a file written into, below a `root: never` home) into #63's `placement_guard.go`. - **Behaviour change recorded:** a directory found on a machine is now used as found. That is a new quiet failure (a module that cannot write its data directory) until the node-engine follow-up lands, and the record names the first cases that would hit it. - **The review's follow-ups are listed:** the controller PR (step-ca root only, every line end, more system paths) and the node-engine PR (WARNING, an unhealthy `directory` resource that raises the module's condition and holds the walk's gate, `mesh-host hand-over`, and the guard's new paths). - The report's line on PEM blocks now says that only step-ca's root may hold lines. All four checks pass locally with the catalogue's word list.

mesh-admin added 1 commit 2026-10-08 22:29:19 +00:00

Issue 339: name the merge order against mesh-host #61, record used-as-found as a behaviour change, and the review's follow-ups ab027691e1

mesh-admin commented 2026-10-08 22:29:47 +00:00

Author

Contributor

Copy Link

Copy Source

Delivery novox/hq@1d9d53591230 — delivered since 2026-10-08T23:55:56Z

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

Transitions

• 2026-10-08 23:43 (new) → proposed (announced): novox/hq#236's head announced
• 2026-10-08 23:44 proposed → checked (checked): the verdict names this commit
• 2026-10-08 23:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-08 23:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-08 23:55 published → delivered (done): nothing for a walk to move

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

<!-- mesh-delivery:view --> **Delivery** `novox/hq@1d9d53591230` — **delivered** since 2026-10-08T23:55:56Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 23:43 (new) → proposed (announced): novox/hq#236's head announced - 2026-10-08 23:44 proposed → checked (checked): the verdict names this commit - 2026-10-08 23:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 23:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 23:55 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben added 1 commit 2026-10-08 22:55:57 +00:00

Issue 339: the gate reads a directory used as found as a wait for a person; the trust anchors are the terminal's 5fbd89c062

jschoubben added 1 commit 2026-10-08 23:24:16 +00:00

Issue 339: the terminal's settings are derived from what a module serves and which files it trusts; a found directory is its own condition the gate never reads as a fault 5d054b722d

jschoubben added 1 commit 2026-10-08 23:42:53 +00:00

Issue 339: an unmarked file counts as trusted, and the rollback hazard of the trusted field and its fix 1d9d535912

mesh-admin merged commit 4b6642de5e into main 2026-10-08 23:55:40 +00:00

mesh-admin deleted branch issues/339-review-follow-ups 2026-10-08 23:55:40 +00:00

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

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#236