jschoubben
189e64c486
The holder's code over a real nats-server bucket with a time to live per key: issue, the operator's yes, redeem as enrol.ace, the node confirming as the login its key of node-logins names (the stand-in vault writes it at node-account), node-enrolled and placement-changed said on their subjects, the user enrol.ace composed while the key is live and gone with it, the token dropped only after the end; and a token never redeemed expires on the bus, is heard, says enrolment-expired and is dropped. Found by it: a bucket with a time to live per key must keep one revision per key, or the bus expires nothing (nats-server 2.11.17), so the state enrolments declares no history. Paid for: the integration test is paid by merging the builder's archive-only and root-module integration tests into one table test; the module's ten unit tests by merging the assigner's three small composition tests into one table (net 2 of 10 paid; the rest is for the lead, the repository being over budget). (issue 774, 774/S60) Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
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.