jschoubben
3d7d65edce
An old-form build (not src2:) has no composition, so no want can ever name what such a node runs. Design limit, decided by the lead (lead-47): its first want names the newest F, by every rule as usual - the canary (rule 3: this node is the canary, or the canary runs F healthy), everything F needs (built, not held, granted, composed) and the providers (rule 5). Otherwise nothing is written and the neither condition stays. The canary stays in force, and old-form modules (clipmenu and screen-lock on g14) leave neither list by themselves, without a hand-written want. The code already behaved so (an old-form have falls through to Holds); the case is now named in Wants, and proven: a unit test for both sides of the canary, the providers and the grant, and the integration test gives g14 F and clears its neither condition once the canary ace runs F healthy.
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.