jschoubben
031cfb8277
Met twice on 2026-10-30 (the engine's acts, then mesh-host_health): the composer refused one principal as a second writer, and that refusal ended the whole composition, so the list in force stood for every principal while changes piled up; the next list that composed moved 52 users at once (16:37:28). Quick fix: leave the refused principal out and write the rest (locks that principal out of the bus). Thorough fix, chosen because the kind was met twice and it hides every other change: ComposeEach composes each principal on its own; a refused one keeps its grants of the list in force (the part's sealed grants), written as the composer writes an entry; one the list in force does not carry stays out; a list that would drop one the list in force carries, whose grants were not kept, is held, said. The refusal is raised as the warning mesh-grants.principal-refused, by name and why, cleared once it composes, and listed in the pass (principals_refused). The entry renderer mirrors buscompose.ComposeAccounts's lines and is pinned to them by the test (the entry the bus loaded is written back byte for byte); it belongs in mesh-sdk as an exported entry writer.
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.