Registers issue 358 (status: open), the follow-up the confirmation review of issue 356 asked for. Number 358 checked free across main and every open branch right before the commit (357 is taken).
Issue 358: the node-engine gives an ordinary mesh directory outside a home its mode and owner by path (chmodDirPath, own → os.Chmod, os.Chown), following any link in a parent at the moment of use. Found by reading the code; nothing was run against a node. Left out of issue 356's fix on purpose, because it changes every placement on every node.
Issue 356's diagnosis, § What remains: a handed-over directory now goes through no link on every apply, not only the first (mesh-host #74, head 9a807de), and the general gap is tracked by issue 358.
merge-check.sh passes locally (records, index, cycle, words, with the catalogue's copy compared). Not merged.
Registers issue 358 (status: open), the follow-up the confirmation review of issue 356 asked for. Number 358 checked free across main and every open branch right before the commit (357 is taken).
- **Issue 358:** the node-engine gives an ordinary mesh directory outside a home its mode and owner by path (`chmodDirPath`, `own` → `os.Chmod`, `os.Chown`), following any link in a parent at the moment of use. Found by reading the code; nothing was run against a node. Left out of issue 356's fix on purpose, because it changes every placement on every node.
- **Issue 356's diagnosis, § What remains:** a handed-over directory now goes through no link on every apply, not only the first (mesh-host #74, head 9a807de), and the general gap is tracked by issue 358.
`merge-check.sh` passes locally (records, index, cycle, words, with the catalogue's copy compared). Not merged.
The confirmation review of issue 356 found that the by-path chmod and chown of an ordinary mesh directory outside a home follows any link in its path. Issue 356 closed it for a handed-over directory, on every apply; the general gap is older and wider, and is recorded here rather than fixed in passing.
Deliverynovox/hq@e68d0ffa1d7c — delivered since 2026-10-09T18:08:14Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-09 17:59 (new) → proposed (announced): novox/hq#258's head announced
2026-10-09 17:59 proposed → checked (checked): the verdict names this commit
2026-10-09 17:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 18:08 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 18:08 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@e68d0ffa1d7c` — **delivered** since 2026-10-09T18:08:14Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-09 17:59 (new) → proposed (announced): novox/hq#258's head announced
- 2026-10-09 17:59 proposed → checked (checked): the verdict names this commit
- 2026-10-09 17:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 18:08 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 18:08 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`.
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.
Registers issue 358 (status: open), the follow-up the confirmation review of issue 356 asked for. Number 358 checked free across main and every open branch right before the commit (357 is taken).
chmodDirPath,own→os.Chmod,os.Chown), following any link in a parent at the moment of use. Found by reading the code; nothing was run against a node. Left out of issue 356's fix on purpose, because it changes every placement on every node.merge-check.shpasses locally (records, index, cycle, words, with the catalogue's copy compared). Not merged.Delivery
novox/hq@e68d0ffa1d7c— delivered since 2026-10-09T18:08:14ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.