3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	657cb2b6c8	A section registered before the controller's terminal took over, or set there, is replaced or removed by a proposal the operator approves ... It could not be changed at all: propose refused a name set there and never replaced one. The ask now says plainly that it replaces or removes the registered section and binds its text's digest; on Approve every node renders the new text in the place of the old (a removal leaves it out); a replacement keeps the section's own heading form (issue 340 note 14). Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-05 22:14:55 +01:00
jochen	e139fb4dd9	claude-code: set shared agent text at the controller's terminal, for now ... Instructions, output styles, skills, commands and subagents for every node or some reach every session as the mesh's own word, and the tools cannot tell an agent from the operator; the operator decided they are set at the terminal until a surface of their own updates them (hq issue 340). They are settings keys, each text a list of lines; the home scope stays free.	2026-10-09 09:41:52 +02:00
jochen	736743fedc	claude-code: refuse registering what a session runs, so no agent can plant it in the operator's sessions ... The tool runner is not told who called, so a hook, a managed setting, a permission rule or a tool server registered through these tools could come from an agent confined on another node and run as the operator there (hq issue 340). They are set at the controller's terminal now; a skill, subagent or command that runs something by itself is refused too, kept hooks and settings are never rendered, and claude_code_registrations lists what is registered and by which node.	2026-10-09 02:30:11 +02:00