6 Commits

Include renames

Author	SHA1	Message	Date
jochen	e41b78cd77	Fill a preference's ${setting:} from its manifest default (hq ADR 0262) ... Without a default, a running module could never gain a setting: the file asking for it failed to compose until set, and the key was refused as stray until a file asked for it. Defaults sit under the mesh's and the node's settings, never merge into a JSON file, are refused for the operator's own values, and settings shows each value's source.	2026-10-08 17:24:32 +02:00
jschoubben	4d9894138e	The derived-value record is ADR 0202 (was 0201) ... The key-value-buckets record took 0201 on main while this waited to merge. Only the comments citing the derived-value work move; this repository's other 0201 citations are the buckets record's own and stay. (cherry picked from commit 75b2676d32)	2026-10-08 01:42:19 +02:00
jochen	6d620f77c3	Bound a consumer's identity by the provision it requires (hq issue 263) ... The one global 20-character bound made every consumer pay an object store's key length, even for provisions that keep no name, and a single overflow refused the provider's whole declaration. An offer now states its own bound (identity: {max, in} or false); unsaid, a provider told its consumers keeps 20 and one told nothing keeps none. module check judges every identity on the longest machine name before merge, and a provider leaves an overflowing consumer out of its grants and composes, with the consumer named by push, plan and status (ADR 0225).	2026-10-06 02:16:20 +02:00
jschoubben	b9ad7a2948	Review before merge: refuse a silent disagreement, and bound the sweep ... Three things found reading this back, each of which would have been quiet. A consumer that keeps several holders of one provision (ADR 0094) gets a login per holder, and a provider derives from the login — so it would make a resource per holder while the consumer is told one value for the requirement. That is issue 124's own failure one case to the side: authenticate, then be refused on every object. Refused now, naming both ends. The sweep runs inside somebody's build and was unbounded. At most two hundred artifacts and sixty seconds, stopping at the first refusal because a store that refuses one refuses all; the rest is offered again next build. The citation and migration renumbers are in the commit before this one.	2026-10-04 03:27:32 +02:00
jschoubben	79993fb498	Rebased onto main: ADR 0188 renumbered to 0201, migration 0055 to 0056 ... The bundles refactor took ADR 0188 on main, so this work's record is 0201 and every comment citing it moves with it. Main also took migration 0055 (an older build never replaces a newer), so the store's collected-artifacts table is 0056 — a number two migrations share is a schema nobody can trust. make check passes except TestTheResolverIsToldEveryMachineOnTheNetworkAndToldAgainWhenOneLeaves, which fails on main too and now for two stacked reasons (hq issues 203 and 202).	2026-10-04 02:45:06 +02:00
jschoubben	580c4d66a7	A served value may name the consumer it is served to (hq ADR 0188) ... ${consumer:as} and ${consumer:as:dns} in a serves block are filled per consumer at resolution, and the one filled value reaches both ends: the consumer's binding and its ${bound:...} substitutions, and the provider's contributions entry as `derived`. A fact or alphabet the mesh does not have is refused at parse; a consumer whose own file already holds the derived value is refused at resolution, naming the placeholder to write instead.	2026-10-04 02:32:19 +02:00