novox/hq ADR 0152, design 34. The runtime's mesh serve, started by the mesh on the credential it sealed to the machine: invokes: ["*"], listens from: machine, no state. Checked with module check before registration (issue 148).
Merge after mesh-controller (its manifest says invokes) and mesh-tools (its base).
novox/hq ADR 0152, design 34. The runtime's `mesh serve`, started by the mesh on the credential it sealed to the machine: `invokes: ["*"]`, listens `from: machine`, no state. Checked with `module check` before registration (issue 148).
Merge after mesh-controller (its manifest says `invokes`) and mesh-tools (its base).
The tool runtime's own client, mesh serve, started by the mesh on the credential it sealed to the
machine (novox/hq ADR 0152, design 34): invokes every tool, listens from the machine only, holds no
state. Checked with module check before it was ever registered (hq issue 148).
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.
novox/hq ADR 0152, design 34. The runtime's
mesh serve, started by the mesh on the credential it sealed to the machine:invokes: ["*"], listensfrom: machine, no state. Checked withmodule checkbefore registration (issue 148).Merge after mesh-controller (its manifest says
invokes) and mesh-tools (its base).