7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	0cdbdca139	Foresee a bus account not yet issued in a composition asked ahead of the Approve, so a module with its own account can be placed (issue 774) ... On 2026-10-30 the placement proposal p-20261030t192428-77dabc was refused on ace and novox: "has no bus credential: nothing was issued for novox.mesh-conditions" (and mesh-self-check, mesh-healers). The vault mints a bus account from the grants part's wanted list once the placement is written on the operator's Approve (ADR 0561 §1: "From the lease write, the vault mints every new bus account and the controller mints none"; ADR 0567 §5: "A placement is written on the operator's Approve"), so a shadow composition can never hold it, and no new module with its own account could be placed. Quick fix: skip the check for the three modules. Thorough fix: the Foreseeing mode foresees an unissued bus account like any own secret the next step makes; the issue-203 refusal (busCredentialIssued), the controller's send's, is gone, and the Reading mode still leaves out what was never issued. Chose thorough: it holds for every module with its own account.	2026-10-30 20:33:05 +01:00
jschoubben	233b6be5dd	Compose each node's provisioning plans from the bus alone, in a Planning mode that reads no secret, so mesh-provisioner composes the plans the controller did (issue 1954 L6-P1, ADR 0570 clause 2)	2026-10-29 22:31:02 +01:00
mesh-tools	075bf1e1fe	Restore the line break the previous patch lost in rowsFor (formatting only)	2026-10-20 07:06:40 +00:00
mesh-tools	8f0150bba2	Grant a consumer on the provider's own node too: a need answered on the same machine has its secret made before the grants are read (review round 2, item 2). The test failed first; the suite is 1259 tests in 1.05 s	2026-10-20 07:06:17 +00:00
mesh-tools	892a3955b7	Place a given secret-family member whose value the Input lacks with a stand-in and name it foreseen, not drop it (review round 1, finding 4). The test failed first; the suite is 1256 tests in 1.05 s	2026-10-20 07:01:56 +00:00
mesh-tools	66da19827c	Grant a provider every consumer the same send would make a credential for, with a stand-in named foreseen, so the identity bound is judged for a consumer a change adds; rows in the controller's order (review round 1, finding 2). Three tests failed first; the suite is 1254 tests in 1.05 s	2026-10-20 07:00:44 +00:00
mesh-tools	b7e1c22512	Compose the credential half of the rendering over an Input: grants, own secrets, core boxes, the certificate, the bus's user list (issue 1364). Ported from mesh-control 6c2a8d62 plan.go renderingFor, grantsFor, certificateFor and core_box.go in their Reading and Foreseeing modes: nothing is made, kept or written; a stand-in is named foreseen, a core box to keep is returned, a consumer left out of a grant and a credential bound elsewhere are returned naming them. The bus's user list is an Input value the controller composes: the broker's account composer (internal/broker, about 900 lines that import the lease and the bus client) is not ported, see the report of this branch.	2026-10-20 06:41:58 +00:00