5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e6e1e3bc89	A gate judges its own send and the build it sent, and never puts the controller back behind its store (hq issue 352) ... On 2026-10-09 a release's gate on the control node read the machine's report against a newer send another plan had just made there, failed three builds the machine had reported healthy, and put them back on every machine to a controller older than the store's schema; that controller then passed the newer plan's gate from its own health. - A gate keeps what its send carried (digest, sequence) and reads the report against it; a report on the last send is on it too. - A gate judges only the build the machine was last sent: another build there supersedes the judging — no verdict, nothing put back. - A controller is told its build (MESH_CONTROLLER_VERSION, ${version} in a process's env) and records how far it reads the store's schema; a put-back to a build that reaches less, or never said, is refused and the current build kept, said as urgent. - A release's open gate holds other sends of its modules there, and a plan's own first send waits on it.	2026-10-09 17:15:40 +02:00
jschoubben	d9a730307c	Test the newest merge's order, a second reopening's gaps and sub-second merge times (hq issues 348, 349) ... The review of PR 179 found four paths no test held: which of two earlier plans NewestMergeOf takes, a tie between them, gaps kept across a second reopening in one keeper, and a merge time's fraction of a second.	2026-10-09 15:29:31 +02:00
jochen	2eb9a22c24	Act under a lease, keep accounts by order, one writer at composition (hq to-be 45 Phase 2) ... Two controllers could both act (issue 204), a reconcile's report could overtake the apply after it and the digest decided (issue 267), and a grant could make a second writer of a machine's report. - The lease (internal/lease, ADR 0229): mesh-controller_lease key `holder`, 15 s age, renewed every 5 s by compare-and-set; the epoch is the revision it was taken at. The gate is the clock (stops 3 s before expiry); a refused renewal is a loss and the process exits; a holder that stops gives it back. serve takes it before asserting the bus. Epochs kept in the store (migration 0068 controller_epoch) as a floor: a bucket raised from nothing is compacted past it. Unleased (no epoch, S12 urgent) only when nobody holds it and the bus will not let it be written. A shell command acts under the holder's epoch, or its own lease when none. - Declarations carry `epoch` inside the signed envelope, only to a machine whose latest account carried a report_sequence (mesh-host #35); would-send is composed with the epoch last sent. Allot and the send both pass the gate. - Reports: contract in internal/link/order.go (epoch, sequence, report_sequence, older_than, refused_older). Accounts kept by epoch, then sequence, then report sequence; older refused, counted; unordered reports keep the digest rule. Plans by compare-and-set on a revision, with epoch. Conditions and calls carry the epoch and are not written off the lease. - S12 and S13 (naming the writer by epoch) watched, D5 run; reset of the bucket said. Writers table compiled in and enforced in PermissionsFor; the controller no longer publishes mesh.control.>. A contract per consumed kind, and the empty-on-error lint over the repository. - mesh-host pinned to its main with the epoch in the validator (D1 validates the envelope as sent). Needs mesh-host's genesis lock with the lease grant (mesh-host PR) for TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose.	2026-10-06 12:29:18 +02:00
jochen	208901c6cc	Let a newer plan supersede the older open plans of its repository (hq issue 254, ADR 0218) ... A merge planned without looking at open plans, so two plans worked the same modules and a stuck plan stayed open for ever. The newer plan folds in what older plans of the same repository and branch had not built or sent, and closes them as superseded. A person can close a stuck plan by id with `plans close <id>`.	2026-10-05 18:17:52 +02:00
jschoubben	fdf338dbd1	A plan is kept, advanced and resumed from the store: the test	2026-10-01 17:56:06 +02:00