9 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c459f75730	compose: an offer of form none composes no credential and holds nothing ... After the controller, nothing makes a pair row for a new consumer, so a need whose provider offers no credential (form none) was composed with a stand-in on both ends and the node-engine held the consumer (issue 1126: mesh-cli on ace, "stands in for the grant of mcp-endpoint"). The vault never mints for form none, so such a need now composes with no credential: the consumer's need carries none, the provider's grant carries the consumer and nothing sealed, neither is named foreseen, CredentialsNeeded asks the vault for neither, and no empty grant file is written. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 15:30:43 +01:00
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	91413de335	compose names the pair credentials a node's composition reads as consumer and provider, and frombus asks them sealed before it composes (issue 1126, ADR 0550 §5)	2026-10-26 19:18:46 +01:00
jschoubben	b72de2b75a	A node applying what it composed refuses a composition that stands in for anything its input lacks, the bus's user list alone held out (issue 1126, ADR 0547 §2)	2026-10-26 18:59:05 +01:00
mesh-tools	cf965b93c2	Test the grant of a consumer on the provider's own node (review round 2, item 2); it failed before the previous commit	2026-10-20 07:06:26 +00:00
mesh-tools	3eadff23eb	Take the suffix of internal names from the Input and never the environment: Input.InternalSuffix and a local internal-name helper, so the package doc is true (review round 1, finding 5). The test failed first; the suite is 1257 tests in 1.04 s	2026-10-20 07:02:58 +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	bd9ff3797d	Test the credential half of the rendering over an Input (issue 1364). Fixtures from mesh-control 6c2a8d62 outside_not_given_test.go (the assistant's two secrets) and the facts_test.go provider and consumer; the refusals checked word for word against plan.go and secrets.go. Written after the code, each rule broken in turn and a test seen to fail. The bus user list is an Input value, so its test is that it is carried (see the commit of the code). Unit level 1.04 s of 2 s.	2026-10-20 06:42:55 +00:00