12 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	8e402c82bf	Pin mesh-sdk 2da0de7, the release's final head, in the modules the release changes (issue 774)	2026-10-30 01:15:38 +01:00
jschoubben	9cb177cae6	Pin mesh-sdk 6e4a301 in the modules the release changes, and keep the others on their pins (issue 774)	2026-10-30 00:23:45 +01:00
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	0842361f85	Keep the hand-act log's acts 400 days, as ADR 0565 §10 has it, now that a module log may say its age; pin mesh-sdk 2e5cc4f (issue 1953)	2026-10-29 22:18:59 +01:00
jschoubben	371abdaad1	Wait on keys that expire on the bus instead of in-process timers, so the healers' settles and S15's fortnight survive a restart (issue 1952) ... A settle and the fortnight end are keys of wakes whose time to live is the wait, heard on expiry; attempts and would keep each key a week by its own time to live. Rearm stays only for a settle that expired while no instance watched. Pins mesh-sdk bc6c8a6.	2026-10-29 22:17:29 +01:00
jschoubben	b5fdcb88c8	Say checked, healer-acted and act-recorded on their seats' subjects, where their consumers hear them, and pin mesh-sdk fbd00c8 (issues 1952, 1953) ... stdio.Emit put them on the module's subject, which no consumer of a seat's event hears. The manifests no longer list a seat's events as the module's own, which the SDK now refuses. mesh-hand-acts takes its act layout and names from mesh-sdk's handacts, and counts a repeated cause by its Repair rule.	2026-10-29 22:12:08 +01:00
jschoubben	e1cdeebcdf	Add mesh-hand-acts, holder of the seat mesh-hand-acts, so the hand-act log has a home the controller's lease does not hold (issue 1953) ... Acts are kept 400 days under the runtime-proven caller and said as act-recorded; a warrant is read from the router's own record and recorded once per ask; hand-acts answers over both logs. The act layout is a copy of mesh-sdk's until L5-S2 lands.	2026-10-29 21:54:21 +01:00