Part of hq issue 346 (hq PR #246), approved by the coordinator: the stop-gap until settings are typed and quoted.
Why.user-dirs.dirs was marked "trusted": false, so the settings verb could set desktop-dir, publicshare-dir and videos-dir. The controller pastes a value raw, and the file is shell assignments meant to be sourced by a shell: $HOME/x"; <command>; X=" (or $(…) inside the quotes) adds a command for any shell that sources it.
What changes.
module.json: "trusted": false removed from the user-dirs resource; the three folders are the controller's terminal's alone again.
New test TestTheFoldersFileStaysTrustedUntilSettingsAreQuoted fails if the resource carries any trusted marking, naming issue 346. It failed before the change and passes after.
README: a paragraph saying why.
What merging does. The rendered file on g14 and shanks is the same; only who may change the settings changes. The module check now gives the expected warning that the file is unmarked and so trusted.
Checks.merge-check.sh on the merge result with origin/main 7339ce8, controller from mesh-controller main 4d60628: words, paths, module check (xdg: ok), health 70 as kept, go vet/go test -race: pass.
Part of hq issue 346 (hq PR #246), approved by the coordinator: the stop-gap until settings are typed and quoted.
**Why.** `user-dirs.dirs` was marked `"trusted": false`, so the `settings` verb could set `desktop-dir`, `publicshare-dir` and `videos-dir`. The controller pastes a value raw, and the file is shell assignments meant to be sourced by a shell: `$HOME/x"; <command>; X="` (or `$(…)` inside the quotes) adds a command for any shell that sources it.
**What changes.**
- `module.json`: `"trusted": false` removed from the `user-dirs` resource; the three folders are the controller's terminal's alone again.
- New test `TestTheFoldersFileStaysTrustedUntilSettingsAreQuoted` fails if the resource carries any trusted marking, naming issue 346. It failed before the change and passes after.
- README: a paragraph saying why.
**What merging does.** The rendered file on g14 and shanks is the same; only who may change the settings changes. The module check now gives the expected warning that the file is unmarked and so trusted.
**Checks.** `merge-check.sh` on the merge result with origin/main `7339ce8`, controller from mesh-controller main `4d60628`: words, paths, module check (`xdg: ok`), health 70 as kept, `go vet`/`go test -race`: pass.
user-dirs.dirs is shell assignments meant to be sourced by a shell, and a setting is pasted into it as
it is, so a folder of $HOME/x"; <command>; X=" set through the verb would add a command of the
caller's. With the file trusted again, the three folders are set at the controller's terminal alone
until settings are typed and quoted at render.
Deliverynovox/mesh-catalog@a588eb598390 — superseded since 2026-10-09T10:51:35Z
Covered: delivered after its walk was superseded: the walk plan-1791543095118060540, which took its walk plan-1791543061772804015 over, ended done
Delivery plan — builds xdg → g14, shanks; no bus step
tier 0: xdg
g14: receives xdg
shanks: receives xdg
Machines
picom on g14: judging — 0 healthy judging(s) so far
xdg on g14: judging — 0 healthy judging(s) so far
Transitions
2026-10-09 10:40 (new) → proposed (announced): novox/mesh-catalog#158's head announced
2026-10-09 10:41 proposed → checked (checked): the verdict names this commit
2026-10-09 10:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 10:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 10:51 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-09 10:51 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@a588eb598390` — **superseded** since 2026-10-09T10:51:35Z
**Covered**: delivered after its walk was superseded: the walk plan-1791543095118060540, which took its walk plan-1791543061772804015 over, ended done
**Delivery plan** — builds xdg → g14, shanks; no bus step
- tier 0: xdg
- g14: receives xdg
- shanks: receives xdg
**Machines**
- picom on g14: judging — 0 healthy judging(s) so far
- xdg on g14: judging — 0 healthy judging(s) so far
**Transitions**
- 2026-10-09 10:40 (new) → proposed (announced): novox/mesh-catalog#158's head announced
- 2026-10-09 10:41 proposed → checked (checked): the verdict names this commit
- 2026-10-09 10:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 10:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 10:51 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-09 10:51 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: xdg)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds xdg → g14, shanks; no bus step
tier 0: xdg
g14: receives xdg
shanks: receives xdg
Run by the build seat on ace as build-1791542418601568338 (builds --log build-1791542418601568338).
--- the gate: xdg
xdg: ok, 5 tool(s); WARNING: user-dirs ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z
modules the change moves:
- xdg (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): xdg
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 34109 strings of 603 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.009s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/xdg
ok xdg/cmd/xdg-tools 1.056s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `a588eb59`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: xdg)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds xdg → g14, shanks; no bus step
- tier 0: xdg
- g14: receives xdg
- shanks: receives xdg
Run by the build seat on ace as `build-1791542418601568338` (`builds --log build-1791542418601568338`).
```
--- the gate: xdg
xdg: ok, 5 tool(s); WARNING: user-dirs ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z
modules the change moves:
- xdg (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): xdg
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 34109 strings of 603 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.009s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/xdg
ok xdg/cmd/xdg-tools 1.056s
--- its merge-check-typescript.sh (typescript toolchain)
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of hq issue 346 (hq PR #246), approved by the coordinator: the stop-gap until settings are typed and quoted.
Why.
user-dirs.dirswas marked"trusted": false, so thesettingsverb could setdesktop-dir,publicshare-dirandvideos-dir. The controller pastes a value raw, and the file is shell assignments meant to be sourced by a shell:$HOME/x"; <command>; X="(or$(…)inside the quotes) adds a command for any shell that sources it.What changes.
module.json:"trusted": falseremoved from theuser-dirsresource; the three folders are the controller's terminal's alone again.TestTheFoldersFileStaysTrustedUntilSettingsAreQuotedfails if the resource carries any trusted marking, naming issue 346. It failed before the change and passes after.What merging does. The rendered file on g14 and shanks is the same; only who may change the settings changes. The module check now gives the expected warning that the file is unmarked and so trusted.
Checks.
merge-check.shon the merge result with origin/main7339ce8, controller from mesh-controller main4d60628: words, paths, module check (xdg: ok), health 70 as kept,go vet/go test -race: pass.Delivery
novox/mesh-catalog@a588eb598390— superseded since 2026-10-09T10:51:35ZCovered: delivered after its walk was superseded: the walk plan-1791543095118060540, which took its walk plan-1791543061772804015 over, ended done
Delivery plan — builds xdg → g14, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
a588eb59mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: xdg)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds xdg → g14, shanks; no bus step
Run by the build seat on ace as
build-1791542418601568338(builds --log build-1791542418601568338).