Found on mesh-catalog #170: adding uses: [operator-channel] fails mesh/merge-gate (the touched manifest alone goes through module check, so the router's declaration is not seen), while mesh/repo-check over every manifest passes. The command's own documentation says such a seat is a note; the code refuses it. No module can become an asker without touching the router's manifest.
Located in mesh-controller (check.go, builder/check.go); fix in mesh-controller fix/364 (PR linked there). records/index/cycle/words pass.
Found on mesh-catalog #170: adding `uses: [operator-channel]` fails `mesh/merge-gate` (the touched manifest alone goes through `module check`, so the router's declaration is not seen), while `mesh/repo-check` over every manifest passes. The command's own documentation says such a seat is a note; the code refuses it. No module can become an asker without touching the router's manifest.
Located in mesh-controller (check.go, builder/check.go); fix in mesh-controller fix/364 (PR linked there). records/index/cycle/words pass.
Deliverynovox/hq@7b096f247100 — delivered since 2026-10-10T02:05:22Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-10 01:54 (new) → proposed (announced): novox/hq#269's head announced
2026-10-10 01:55 proposed → checked (checked): the verdict names this commit
2026-10-10 01:55 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 02:05 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 02:05 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@7b096f247100` — **delivered** since 2026-10-10T02:05:22Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 01:54 (new) → proposed (announced): novox/hq#269's head announced
- 2026-10-10 01:55 proposed → checked (checked): the verdict names this commit
- 2026-10-10 01:55 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 02:05 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 02:05 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.
Found on mesh-catalog #170: adding
uses: [operator-channel]failsmesh/merge-gate(the touched manifest alone goes throughmodule check, so the router's declaration is not seen), whilemesh/repo-checkover every manifest passes. The command's own documentation says such a seat is a note; the code refuses it. No module can become an asker without touching the router's manifest.Located in mesh-controller (check.go, builder/check.go); fix in mesh-controller fix/364 (PR linked there). records/index/cycle/words pass.
Delivery
novox/hq@7b096f247100— delivered since 2026-10-10T02:05:22ZDelivery 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.