Issue 361 (the control-node's agent account is never judged): a dated section in 01-diagnosis.md covering three things:
why the progress is now visible through the verdict and root-free (counts, times and mount points, never a path);
why a fresh search is a line at the controller's terminal (nox node setuid-search <node>) and not a verb;
the idea of judging only the setuid files the agent account can reach. This was considered and not built, with the reasons.
To-be 45's writers table gains the row a fresh setuid search asked of a machine. mesh-controller's writers test holds the same row.
Code: mesh-host #76, plus the mesh-controller companion PR. All four checks pass locally.
Issue 361 (the control-node's agent account is never judged): a dated section in `01-diagnosis.md` covering three things:
- why the progress is now visible through the verdict and `root-free` (counts, times and mount points, never a path);
- why a fresh search is a line at the controller's terminal (`nox node setuid-search <node>`) and not a verb;
- the idea of judging only the setuid files the agent account can reach. This was considered and not built, with the reasons.
To-be 45's writers table gains the row `a fresh setuid search asked of a machine`. mesh-controller's writers test holds the same row.
Code: mesh-host #76, plus the mesh-controller companion PR. All four checks pass locally.
Deliverynovox/hq@2d0a6ba4bc2f — delivered since 2026-10-10T00:06:58Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-10 00:00 (new) → proposed (announced): novox/hq#265's head announced
2026-10-10 00:00 proposed → checked (checked): the verdict names this commit
2026-10-10 00:00 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 00:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-10 00:06 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@2d0a6ba4bc2f` — **delivered** since 2026-10-10T00:06:58Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 00:00 (new) → proposed (announced): novox/hq#265's head announced
- 2026-10-10 00:00 proposed → checked (checked): the verdict names this commit
- 2026-10-10 00:00 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 00:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-10 00:06 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.
Issue 361 (the control-node's agent account is never judged): a dated section in
01-diagnosis.mdcovering three things:root-free(counts, times and mount points, never a path);nox node setuid-search <node>) and not a verb;To-be 45's writers table gains the row
a fresh setuid search asked of a machine. mesh-controller's writers test holds the same row.Code: mesh-host #76, plus the mesh-controller companion PR. All four checks pass locally.
Delivery
novox/hq@2d0a6ba4bc2f— delivered since 2026-10-10T00:06:58ZDelivery 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.