jochen 04626be62d claude-code: the manifest, the managed directory and the tools (hq design 36, to-be 40 WP2) ...

The module owns /etc/claude-code: managed-mcp.json lists the console as `mesh` over HTTP on
loopback plus the servers in its mcp_servers setting (exclusive, by the operator's choice — the
https rule of managedMcpServers refuses a loopback console); managed-settings.json carries the
attribution convention, keeps claude.ai connectors, and adds the key-helper only for an API-key
licence; CLAUDE.md says how a session here works. Rendered whenever the runtime collects the
tools, written only on change, through the operator account's sudo. Under the home, only the
credentials file, only on a hand-over. Nothing declared under a home or /etc; the console's
port comes from node-tools' mcp-endpoint (mesh-tools #34).

2026-10-03 16:13:01 +02:00

..

grant.test.ts

claude-code: the sealed hand-over, the credentials write with the lineage rule, the identity read (hq to-be 40 WP2, in progress)

2026-10-03 16:05:58 +02:00

identity.test.ts

claude-code: the sealed hand-over, the credentials write with the lineage rule, the identity read (hq to-be 40 WP2, in progress)

2026-10-03 16:05:58 +02:00

render.test.ts

claude-code: the manifest, the managed directory and the tools (hq design 36, to-be 40 WP2)

2026-10-03 16:13:01 +02:00

seal.test.ts

claude-code: the sealed hand-over, the credentials write with the lineage rule, the identity read (hq to-be 40 WP2, in progress)

2026-10-03 16:05:58 +02:00