7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	eff81f1220	Never refuse a node for a held module's stand-in by its own runtime's rules (issue 774) ... On 2026-10-30 at 21:04 mesh-self-check (ace) and mesh-conditions, mesh-healers (novox) were placed before their bus accounts were issued. Each was held for "needs a secret called broker and none was made"; its bare stub then lost its own secrets and was refused by ownRuntimes ("runs as its own account and declares no own secret broker"), a refusal no culprit takes, so 74 modules on ace and 79 on novox failed. A held runtime's stub met the same kind earlier today ("its build produced 0 bundle(s)"). Quick fix: let the bare stub keep its broker own secret, for this one rule. Thorough fix (chosen, the fourth of the kind today): a held module's stand-in (Stubbed) has no runtime composed at all, so no rule about its runtime, bundle or broker can refuse it: ownRuntimes passes it over and runtimeProcess composes none for a held runtime (what runs of either is carried, as before). A module of its own account left without its runtime by a held runtime is refused with a typed NoRuntimeToRunError, which makes the held runtime the culprit, so those modules are held after it and the node composes the rest.	2026-10-30 21:18:06 +01:00
jschoubben	8e3d7a4c3c	Give a tools bundle's bus-account secret to the runtime's account and refuse it where that account cannot reach, so the bus tools can read their credential (issue 1952 S5, ADR 0564 Limits 4)	2026-10-29 21:59:11 +01:00
jschoubben	c2999a4e13	A held module is no dependence of its neighbours: its hold stops spreading (issue 1126) ... novox's seed p-20261028t231141-ec84b4 refused 11 modules "what it composes of ..., held, is not what runs of them": de-spiegel's hold spread through mailu to postgres, nftables and route-proxy, and from postgres to every consumer, and gitea, held so, refused the node: "its credential of postgres-database is handed to the provisioner and the module is not: nothing would fill it". Three rounds each moved the error. The kind: a held module still took part in the composition as a dependence, so its hold spread. - The quick fix: let heldAsToday also follow dependsOnHeld's words, and skip the handed refusal for gitea. It moves the error once more and leaves every node's applying path holding consumers. - The thorough fix, chosen: a held module composes only as what runs of it. composeEach no longer compares the composition with each held module as its stub (dependsOnHeld removed): a consumer or collector composes against what runs of the held module like any other module, and a real difference is still a named difference in the answer, a module's own refusal still its refusal. A stub (compose.Stub, catalogue.Manifest.Stubbed) leaves the credentials and own secrets it would hand the provisioner out of its plan as they run, never refused for want of a plan. Only what a held module's new manifest says to others in their own files is still held behind it (dependents: the provider of what it contributes to, the filter where it listens), which heldAsToday already follows. Tests: rows added to existing tests (a held provider with a binding consumer, which the old code held in the seed's words; a held feeder of a collector; a held module with a handed credential and own secret). No new test function.	2026-10-29 00:49:00 +01:00
jschoubben	06742d0448	A contribution's unset required value is refused in its module's own form's words, as a file's is (issue 1126, seed-8: de-spiegel in the config form was told ${setting:…} and settings set)	2026-10-28 14:07:59 +01:00
jschoubben	16b8d8a1ee	Compose as the controller does, so a node's shadow can answer same (issue 1126, C1 C2 C3 C5 C6, T1) ... Seals are reused and compared by slot (resource, field), never across resources; one rule says which resolved config values are laid; a seat path that steps back is owned by the seat it steps back for, whatever the seat order; a folded module of an old-form build is composed from what runs of it; the operator export's file is carried as it runs; a differing resource names its differing JSON paths, found before its bodies are cut, and an answer is fitted to the node's key.	2026-10-28 09:36:36 +01:00
jschoubben	b7b81e040f	Carry shares on a requirement of s3-bucket to the provider's grant, so a bucket's other users are named in the manifest (issue 1591)	2026-10-21 11:15:49 +02:00
mesh-tools	5e4fcc6db7	Copy mesh-controller's catalogue into mesh-sdk, part 1: the package and its testdata, from mesh-control 6c2a8d62 (issue 1354)	2026-10-20 06:05:52 +00:00