novox/mesh-controller
3
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity
Files
98aea8b25ca0d906577b57c3213e1dbee82b2a6e
mesh-controller/internal
T
History
jschoubben bc289cbe04 The restart-on rename reads both list shapes 
A resource composed in code carries restart-on as []string; the rename
only read []any, so the overlay's registry-trust reload kept its bare
reference, pointed at nothing, and the runtime was never restarted —
the trust was on disk and not in the daemon, with every check passing.
Diagnosed on the built-store-cross-node bed, run 8 (issues 042/048).
2026-09-17 23:35:12 +02:00
..
broker
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
builder
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
catalogue
The restart-on rename reads both list shapes
2026-09-17 23:35:12 +02:00
identity
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
inventory
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
licences
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
link
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
overlay
The network carries the registry trust (ADR 0082, issues 042/048)
2026-09-17 23:05:23 +02:00
secrets
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
store
Read a context's store connection from a file, not only from the environment
2026-09-10 23:40:37 +02:00
token
The token carries the node's name
2026-08-30 02:36:57 +02:00