The licence manager runs as its own account, so its own logs are issued to it and its carry-over can finish (issue 1409) #659

Merged

mesh-tools merged 2 commits from fix/1409-own-runtime into main 2026-11-12 08:41:49 +00:00

Conversation 1 Commits 2 Files Changed 6

+244 -25

2 Commits

Author	SHA1	Message	Date
jschoubben	8291502cbb	C2: a key pair the manager cannot read is made anew in its place (issue 1409) ... Moved to its own account, the manager finds manager-key.json still owned by the tool runner's account, which the node-engine does not hand over; it skipped making a pair because the file existed, and every verb answered the read error. Now a pair it cannot read is replaced by a new one, renamed over it, and said in its journal; every use passes the public key per ask, so nothing depends on the old pair. Builds: design 39 bus-and-switch C2 Claude-Session: https://claude.ai/code/session_01NcbgfHb9d4T9nq5Q6WqdiJ	2026-11-12 09:38:03 +01:00
jschoubben	8d2497b65e	C1: the licence manager runs as its own account, its service and its tools in its own runtime (issue 1409) ... Run inside the machine's tool runner, the manager was issued none of its own logs and states, so the carry-over failed live ("keeps no log called usage ... it was issued: none"). It now declares runs-as claude-licence-manager, makes that account, owns what it places on its machine and its secrets, reaches the bus with its own broker secret, and invokes a node's claude_code_grant, which the tool runner's account could ask and its own could not. The whole tests play the manager's own runtime: they issue only the states, logs, asks and events its manifest names, and fail on a manifest without runs-as; a unit test holds every ask in the code to the manifest's invokes. Builds: design 39 bus-and-switch C1 Claude-Session: https://claude.ai/code/session_01NcbgfHb9d4T9nq5Q6WqdiJ	2026-11-12 09:25:57 +01:00