7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e362c800a4	The engine test-dials, switches, confirms, drops and falls back across a rotation of its login ... On node-logins' ready the engine fetches the new value through the vault's own hand-out (own/<node>/mesh-host/<login>, opened with its sealing key), dials a second connection as the new login on the pinned certificate, and switches only if that authenticates, then calls mesh-vault.node-account-confirm over the link as the new login (the vault is asked in the name of the login the open link authenticated as, and only once that link is open). It keeps the old value until the key says the rotation is done and drops it then, never before; an abandon, after the switch before or after the confirmation, switches back before the new value is dropped; repeated refusals of the new login's credentials before rotation-done bring it back to the old one, said as the finding node-account-fallback (in the journal: no route for an engine's finding to the watchman is decided), and the same rotation is not tried again. Tests: two added, paid by merging two identity sealing tests into one; more to be paid by deleting the identity token tests that move to mesh-sdk with the token (774/S64). (issue 774, 774/S62, 774/S63) Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 01:49:01 +01:00
jschoubben	a4c0cee251	Read this node's placement from its node and module keys, or its placement.<node> before the holder converts it, so a write of the holder's is composed only once its node key lands (issue 774, research 072 row 37)	2026-10-31 09:37:23 +01:00
jschoubben	dd8ba97989	Node agent: wait for the bus's word that the seat's placement and candidates states were created, then watch them (issue 1126)	2026-10-28 18:43:49 +01:00
jschoubben	11a635796d	Bound a key's history read to 10 s and test it on a real bus; the witness test waits for its process to run from its image (issue 1945)	2026-10-25 12:51:00 +01:00
jschoubben	8343c4fb36	Apply the revision of a composition key whose digest the want names, from the revisions the bucket keeps (issue 1945)	2026-10-25 12:42:20 +01:00
jschoubben	e5a06cc73d	The node agent waits for a backup's end on the holder's event, not by polling; the manifest consumes it (R6-A A5)	2026-10-24 17:03:30 +02:00
jschoubben	3303797bfb	The node agent runs in the node-engine: watches the wants and compositions on the link, applies one module's composition, asks the backup, writes the haves (R6-A A1, A5, A6)	2026-10-24 16:39:51 +02:00