jochen
3677af6079
mesh/merge-gate pass: builds claude-code → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh, merge-check-typescript.sh): main's version judged it; the change's judges the pull r…
mesh/delivery superseded: a newer head of the same pull request
On the nodes where the agent runs as the operator, the home scope wrote the operator's own ~/.claude, whose rules and skills load in every session, and any node's tool could be addressed from another (hq issue 340). Take it only for the serving node, where its home is an agent account's own; never place a bus item in the operator's home. Ignore the built binary.
13 lines
522 B
Plaintext
13 lines
522 B
Plaintext
node_modules/
|
|
dist/
|
|
|
|
# Go tool bundles built in place (go build in a module's cmd/<name>-tools) are build output.
|
|
modules/slack/cmd/slack-tools/slack-tools
|
|
modules/jetbrains-toolbox/cmd/toolbox-tools/toolbox-tools
|
|
modules/messenger/cmd/messenger/messenger
|
|
modules/mesh-watcher/cmd/mesh-watcher/mesh-watcher
|
|
modules/claude-code/cmd/claude-code/claude-code
|
|
# ...and the same built from the module's root (go build ./cmd/<name>), which names it after the module.
|
|
modules/messenger/messenger
|
|
modules/mesh-watcher/mesh-watcher
|