7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	a40b4d3d3f	Let the vault mint every wanted bus account whoever holds the controller's lease, keep its mint over a controller's issued value, and tell a node which modules it judged handed, so no account waits on a node reporting to the controller (issue 774)	2026-10-31 09:49:15 +01:00
jschoubben	b60138990b	Read a machine's placement once per answer of own, and say how long every answer took and every refusal, so an answer of 143 credentials is not 143 bus reads and an ask that went unanswered can be told from one never heard (issue 774) ... Quick fix: the plan reader keeps the machine's one placement key for the answer, as it keeps each module's assignment (issue 1126, 2026-10-28); the second time one answer's reads per credential held own past the node-engine's 15 s. Thorough fix (not here): the node-engine asks own only when a secret or a credential it composes from changed, and the assigner writes no want that is unchanged.	2026-10-31 01:05:01 +01:00
jschoubben	d5c4f8aaa9	Answer a module's own secrets to its node-engine when its plan only keys a provision, so twenty modules whose route the provisioner now keys compose again (issue 774)	2026-10-30 23:48:29 +01:00
jschoubben	a9d96b30be	mesh-vault: a watch of the assignments begun again keeps nothing an earlier attempt took, and a module the mirror lacks is read directly before a credential is refused (issue 1126, review round 1) ... A watch that failed partway kept what it had taken; begun again, the runtime does not hand a key deleted meanwhile, so a removed assignment read as standing and credentialRefusal could hand a consumer credential to a node no longer running its module. Each attempt now begins from nothing held, and a late delivery to an older attempt changes nothing. A 'not on the node' refusal is confirmed by a direct read first, since a watched mirror can be behind.	2026-10-28 14:55:36 +01:00
jschoubben	277a4d0060	mesh-vault answers own in one pass: assignments from its watch, each module's once, one synced record per answer (issue 1126) ... Seed-9's probe (13:31-13:36Z): novox's own of 57 secrets and 146 credentials took 26 s, past the node-engine's 15 s, and ace and novox refused their whole shadow answer. own read the controller's assignment over the bus once per secret and per credential (203 reads), read every record of every node, and synced the hand-out record once per value, under the one lock every node's answers share. Now the vault watches the assignments mirror (a watch, never a poll) and reads it from memory once caught up, over the bus until then; one answer reads each module's assignment once; only own/<node>/ records are read; and every hand-out of one answer is recorded in one synced write, none handed when it cannot be. Quick fix weighed: a longer bound in the node-engine (VaultWithin). Thorough fix chosen: the cost grows with every module and every node, and the lock is shared by every shadow answer and every apply.	2026-10-28 14:47:20 +01:00
jschoubben	1faf317069	Review of L2: the vault's own fails closed: a pair credential's consumer is read standing, the shared value goes only to a holder its record names, and unread assignments refuse, never hand (C1, C2); the placement check pins mesh-sdk 3968849 (issue 1126, ADR 0550 §5)	2026-10-26 20:12:21 +01:00
jschoubben	851e8782d5	Nodes compose: the catalogue's placement files and their check, mesh-config reading placement, the vault's own and pair credentials, the forge's commit trees (issue 1126) ... One commit for the branch feat/1126-nodes-compose of mesh-catalog: its 15 commits squashed so its history does not carry two compiled programs committed by mistake and removed later, mesh-config (5.5 MB) and checks/placement (6.2 MB) (issue 1577). The tree equals the former head 2db56067. The operator allowed this rewrite of the feature branch on 2026-10-26.	2026-10-26 19:49:39 +01:00