10 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	475ffdcb33	gitea waits and keeps serving while its keys are unread; pin mesh-sdk 007b6fd ... After a restart the forge-account provider returned a plain error, which the helper writes as failed with its values cleared, so every consumer lost its forge entry until the keys loaded. provider.ErrNotReady keeps the entry serving, in waits (issue 1954).	2026-10-30 00:04:14 +01:00
jschoubben	cb7a5c9939	mesh-provisioner composes through fromruntime's reader; pin mesh-sdk fa5a6ae across A3's modules ... The SDK now reads a module's `reads` through the runtime, so busread.go's own copy goes, and the manifest is held to frombus.StatesReads (issue 1954).	2026-10-30 00:02:38 +01:00
jschoubben	451d790edd	Judge each provider by what its manifest declares and fill what a provision depends on, so a templated pair provider is provided only after its credential (issue 1954) ... A provider declaring bound is judged by its entries, any other by its own have, and only once every provision it depends on, its secret-<provision> first, is provided. The credential is the vault's own provision. One integration test runs the holder on a real bus over mesh-sdk's in-memory mesh: a want composes the key, the outcomes provide it, leaving the node asks. Pins mesh-sdk 6b8c694.	2026-10-29 22:49:26 +01:00
jschoubben	6bee0b6789	Never set a provision provided without its provider's outcome, read from the entry's state and why, and pin mesh-sdk 692dbf9 (issue 1954) ... A provider that writes no outcome leaves its keys asked (ADR 0570 clause 3), so a provider that fails is never hidden.	2026-10-29 22:43:16 +01:00
jschoubben	077135a7f3	Keep mesh-config's held values in mesh-sdk's KeptValue layout, which the checks read, and pin mesh-sdk 66ff33d (issue 1953) ... The layout and its keys are unchanged, so no value moves.	2026-10-29 22:41:29 +01:00
jschoubben	4117ec3a57	Serve compare, take-over and hand-back as the mesh-config seat's verbs, beside the module's own tools; pin mesh-sdk 4204afd (issue 1953)	2026-10-29 22:29:48 +01:00
jschoubben	d34645361d	Build config's switch from the controller's records: declared, compare, take-over and hand-back, so the operator approves the last move only once nothing differs (issue 1953) ... compare also resolves every placed module's values on every node both ways, as ADR 0565's insight of 2026-10-29 asks after #558. After the take-over the predefined list and pull requests' config come from the indexer and pull-declares is refused; a hand-back returns to the mirrors until the lease write. From the lease write a trusted value is set only on an Approve. Acts are recorded through mesh-hand-acts. Pins mesh-sdk 2e5cc4f.	2026-10-29 22:27:23 +01:00
jschoubben	59cad7154a	Pin mesh-sdk to the group's head 38dbe1d in the build modules, mesh-config, the gate and the vault; the vault's test answers by proposal (issue 1126)	2026-10-28 18:52:35 +01:00
jochen	2379027cec	Propose mesh-issues' owners: take the SDK that reads names with digits as names (issue 1439) ... mesh-config refused every owners proposal as carrying a secret, because the SDK's CheckSecret took modules/asus-zephyrus-g14, i3status-rust and powerlevel10k for random strings. The SDK at feat/1439-name-runs judges such a lowercase name piece by piece; this moves mesh-config to it and proves the catalogue's own owners list plus okioki is put to the operator.	2026-10-21 09:57:56 +02:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00