novox/mesh-catalog
9
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

claude-code: read and remove the person's own home items through the mesh #108

Merged
mesh-admin merged 2 commits from feat/claude-code-home-show-remove into main 2026-10-07 17:48:06 +00:00
Conversation 3 Commits 2 Files Changed 6
+825 -4
mesh-admin commented 2026-10-07 17:39:42 +00:00
Contributor
Copy Link
Copy Source

The operator's hand-written items in an account's ~/.claude (HAL-era rule files among them) could only be read or removed over a shell on the machine. Two tools, per node (like claude_code_config_status and _import):

  • claude_code_home_show {kind, name} — one home item in full: skill (every file), agent, command, output-style, instructions (a rule file), or memory (~/.claude/CLAUDE.md, name absent). Says whether the mesh placed it.
  • claude_code_home_remove {kind, name, why} — removes one item the person made, on their word. why required. Refuses what the mesh placed (points at claude_code_<kind>_unregister) and symbolic links (the item, a folder on its way, or inside a skill). Copies the item first to <state>/removed-from-home/<YYYY-MM-DD>/<HHMMSS>-<kind>-<name>/<path in home> with a removal.json, reads the copy back, checks the item did not change meanwhile, then deletes and appends to <state>/removed-from-home/removed.log; logs to stderr too. Answers keptAt and an undo line. If a home registration of the same name was held back by the person's file, the answer says it is placed at the next render.

claude_code_config_status now also lists the home's memory (kind: memory).

Stance (hq ADR 0216 rules 5–6): removing the original stays the person's act — this tool is that act made explicit, called only on the person's word. Rule 5's "It writes, changes and removes only those" (what it placed) needs an hq amendment to say the module also removes the person's own item when the person asks through claude_code_home_remove.

Tests: home_test.go (show every kind, reason required, copy + log + no overwrite of an earlier copy, skill modes kept, memory, mesh-placed refused, symlinks refused); manifest tool list test passes. merge-check.sh run locally: Go tests pass under -race; manifest check left to the gate (no controller locally).

The operator's hand-written items in an account's `~/.claude` (HAL-era rule files among them) could only be read or removed over a shell on the machine. Two tools, per node (like `claude_code_config_status` and `_import`): - `claude_code_home_show {kind, name}` — one home item in full: skill (every file), agent, command, output-style, instructions (a rule file), or `memory` (`~/.claude/CLAUDE.md`, name absent). Says whether the mesh placed it. - `claude_code_home_remove {kind, name, why}` — removes one item the person made, on their word. `why` required. Refuses what the mesh placed (points at `claude_code_<kind>_unregister`) and symbolic links (the item, a folder on its way, or inside a skill). Copies the item first to `<state>/removed-from-home/<YYYY-MM-DD>/<HHMMSS>-<kind>-<name>/<path in home>` with a `removal.json`, reads the copy back, checks the item did not change meanwhile, then deletes and appends to `<state>/removed-from-home/removed.log`; logs to stderr too. Answers `keptAt` and an undo line. If a home registration of the same name was held back by the person's file, the answer says it is placed at the next render. `claude_code_config_status` now also lists the home's memory (`kind: memory`). Stance (hq ADR 0216 rules 5–6): removing the original stays the person's act — this tool is that act made explicit, called only on the person's word. Rule 5's "It writes, changes and removes only those" (what it placed) needs an hq amendment to say the module also removes the person's own item when the person asks through `claude_code_home_remove`. Tests: `home_test.go` (show every kind, reason required, copy + log + no overwrite of an earlier copy, skill modes kept, memory, mesh-placed refused, symlinks refused); manifest tool list test passes. `merge-check.sh` run locally: Go tests pass under -race; manifest check left to the gate (no controller locally).
mesh-admin added 1 commit 2026-10-07 17:39:42 +00:00
claude-code: read and remove the person's own home items through the mesh
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)
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery superseded: a newer head of the same pull request
Details
03728728c3 
Hand-written items in an account's ~/.claude could only be removed over a
shell on the machine. claude_code_home_show reads one in full (memory,
~/.claude/CLAUDE.md, included); claude_code_home_remove removes one on the
person's word, with a required reason, refusing what the mesh placed and
symbolic links, keeping a dated copy in the module's state and logging it.
mesh-admin commented 2026-10-07 17:40:32 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-catalog@a0deb9074122 — delivered since 2026-10-07T17:54:58Z

Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step

  • tier 0: claude-code
  • ace: receives claude-code
  • g14: receives claude-code
  • novox: receives claude-code
  • shanks: receives claude-code
  • claude-code keeps data (ADR 0233): what it holds is backed up before it moves

Machines

  • claude-code on ace: passed — healthy 3 times over 2m34s
  • claude-code on the rest running it: sent

Transitions

  • 2026-10-07 17:44 (new) → proposed (announced): novox/mesh-catalog#108's head announced
  • 2026-10-07 17:46 proposed → checked (checked): the verdict names this commit
  • 2026-10-07 17:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-07 17:48 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-07 17:48 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
  • 2026-10-07 17:54 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@a0deb9074122` — **delivered** since 2026-10-07T17:54:58Z **Delivery plan** — builds claude-code → ace, g14, novox, shanks; no bus step - tier 0: claude-code - ace: receives claude-code - g14: receives claude-code - novox: receives claude-code - shanks: receives claude-code - claude-code keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - claude-code on ace: passed — healthy 3 times over 2m34s - claude-code on the rest running it: sent **Transitions** - 2026-10-07 17:44 (new) → proposed (announced): novox/mesh-catalog#108's head announced - 2026-10-07 17:46 proposed → checked (checked): the verdict names this commit - 2026-10-07 17:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 17:48 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 17:48 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-07 17:54 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin commented 2026-10-07 17:42:17 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 03728728

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code)
  • mesh/repo-check: PASS — its merge-check.sh passed

Change plan — builds claude-code → ace, g14, novox, shanks; no bus step

  • tier 0: claude-code
  • ace: receives claude-code
  • g14: receives claude-code
  • novox: receives claude-code
  • shanks: receives claude-code
  • claude-code keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791394807103270026 (builds --log build-1791394807103270026).

--- the gate: claude-code
claude-code: ok, 37 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable)
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:23:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-07T17:23:39Z

modules the change moves:
  - claude-code (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): claude-code
--- its merge-check.sh (go toolchain)
long-running resources without health: 70, as kept
testing modules/claude-code
ok  	claude-code/cmd/claude-code	1.079s
**Merge check** at `03728728` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Change plan** — builds claude-code → ace, g14, novox, shanks; no bus step - tier 0: claude-code - ace: receives claude-code - g14: receives claude-code - novox: receives claude-code - shanks: receives claude-code - claude-code keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791394807103270026` (`builds --log build-1791394807103270026`). ``` --- the gate: claude-code claude-code: ok, 37 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable) long-running resources without health: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:23:39Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-07T17:23:39Z modules the change moves: - claude-code (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): claude-code --- its merge-check.sh (go toolchain) long-running resources without health: 70, as kept testing modules/claude-code ok claude-code/cmd/claude-code 1.079s ```
jschoubben added 1 commit 2026-10-07 17:44:08 +00:00
claude-code: undo a home removal through the mesh
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)
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
a0deb90741 
A removal kept its copy but nothing could put it back without a shell on
the machine. claude_code_home_restore puts a kept copy back when nothing is
at its path and the copy matches the digests recorded at removal;
claude_code_home_removed lists what is kept.
mesh-admin commented 2026-10-07 17:46:52 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at a0deb907

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code)
  • mesh/repo-check: PASS — its merge-check.sh passed

Change plan — builds claude-code → ace, g14, novox, shanks; no bus step

  • tier 0: claude-code
  • ace: receives claude-code
  • g14: receives claude-code
  • novox: receives claude-code
  • shanks: receives claude-code
  • claude-code keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791395053897216770 (builds --log build-1791395053897216770).

--- the gate: claude-code
claude-code: ok, 39 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable)
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:23:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-07T17:23:39Z

modules the change moves:
  - claude-code (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): claude-code
--- its merge-check.sh (go toolchain)
long-running resources without health: 70, as kept
testing modules/claude-code
ok  	claude-code/cmd/claude-code	1.096s
**Merge check** at `a0deb907` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Change plan** — builds claude-code → ace, g14, novox, shanks; no bus step - tier 0: claude-code - ace: receives claude-code - g14: receives claude-code - novox: receives claude-code - shanks: receives claude-code - claude-code keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791395053897216770` (`builds --log build-1791395053897216770`). ``` --- the gate: claude-code claude-code: ok, 39 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable) long-running resources without health: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:23:39Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-07T17:23:39Z modules the change moves: - claude-code (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): claude-code --- its merge-check.sh (go toolchain) long-running resources without health: 70, as kept testing modules/claude-code ok claude-code/cmd/claude-code 1.096s ```
mesh-admin merged commit 3ad2235663 into main 2026-10-07 17:48:06 +00:00
mesh-admin deleted branch feat/claude-code-home-show-remove 2026-10-07 17:48:06 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#108