10 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	68e7a2ddbf	Pin mesh-sdk at f02f142, the sdk1 head whose tests no longer leak package globals, so the group's check builds against it ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 20:14:16 +01:00
jschoubben	7f4cc9e2ec	Pin mesh-sdk at the sdk1 group's head 1c7356c, so the group's check builds every module against the narrowed SDK it was written for ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:29:53 +01:00
jschoubben	7f8701637f	Pin mesh-sdk to the group head of issue 1126 ... Every member builds against mesh-sdk abf5eac, the head of feat/1126-removal, so the group is checked as one contract. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 12:29:57 +01:00
jschoubben	04379702e5	Pin mesh-sdk to the group head of issue 1126 ... Every member builds against mesh-sdk f569924, the head of feat/1126-removal, so the group is checked as one contract. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 12:29:56 +01:00
jschoubben	70396caeab	Pin mesh-sdk to the group head of issue 1126 ... Every member builds against mesh-sdk 729a86b, the head of feat/1126-removal, so the group is checked as one contract. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 12:29:56 +01:00
jschoubben	3e08301b27	Pin every module to the group's mesh-sdk head after the gofmt fix ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 03:30:59 +01:00
jschoubben	c4406da4a3	Pin every module to the group's mesh-sdk head after review round 1 ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 03:17:47 +01:00
jschoubben	c19edac804	Pin every module that names mesh-sdk at the group's final head, without the judge (ADR 0578 §4) ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 02:50:43 +01:00
mesh-admin	a72eb3dbb2	licence manager: say what moved a binding, why, and who asked (issue 625) ... A switch of g14 back to another licence on 2026-10-13 left no trace: the manager logged no line and sent no event for bind, switch or release, and its audit kept only the verb's name. Every change of what a consumer holds now goes to the journal, the audit and a licence.<what> event with the same fields: consumer, licence before and after, generation, why (the verb or the rule) and by (the caller the runtime proved, or the manager itself). The node is told why in the bindings state and says it when it applies. The audit and binding tables become readable through the store's reader. The SDK moves to the version that proves the caller (issue 365).	2026-10-13 11:45:52 +00:00
jochen	15b2e6b86e	The licence manager, in Go, and claude-code's half of ADR 0206 ... claude-licence-manager holds the anthropic-licence-manager seat: it reads every node's holdings state, adopts a login it does not hold by refreshing it (newest first, once per account), keeps each grant alive under a lease, publishes what each consumer should hold as its bindings state with a generation, and answers current sealed to the consumer's key. Postgres store prepared by a run-once step; grants encrypted with the vault's key. claude-code reports what its node holds (fingerprints and account, never a token), hands its grant over only when the manager asks, watches its binding and fetches the token on a newer generation, and writes access-token-only. Its ask now reads the runtime's answer as a value and addresses seats as seats.	2026-10-04 12:18:51 +02:00