6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	a474762527	Pin route-proxy to a commit of mesh-sdk main, since the pinned one is on a feature branch only (issue 1669)	2026-10-21 14:25:34 +02:00
mesh-tools	4083755ca1	Let the build agent read the gate's pull keys and watch both buckets (issue 1325) ... From R3e the gate writes mesh-delivery-gate_pulls and today's bucket stops (ADR 0450 §1). The build agent's manifest reads both, and a running check's watch listens in every bucket that exists, so a move is heard whichever holds the key.	2026-10-19 21:42:37 +00:00
jschoubben	e16cb4207b	Review round 1 of milestone 5: the move settles changed rows under the lock; reports counted by kind; route-proxy at the new SDK; the plan pass never revives an ended assignment; the store's mirror is refused once moved (issues 1090, 1092, 1093) ... 1090/1092: the move tests pick each report by kind and expect three, all already, on the second run. 1090-1093: under the share lock the switch reads the rows again and writes every key whose value differs from its row (and ends an assignment the store dropped) before recording the kind, so an update the old controller made after the first pass is not lost. 1093: route-proxy is pinned at mesh-sdk f185aedb and vendored; the controller uses only the SDK's asks package. KeepAssignmentPlans decides each key by keepStep, which never makes or revives an assignment. AssignmentsMirrorToWrite refuses once the assignments are moved.	2026-10-18 03:36:05 +02:00
jschoubben	b752b1f1df	Remove the release-branch judge from the controller, the wire and the build seat (issue 977, part A, ADR 0401)	2026-10-17 20:43:06 +02:00
jschoubben	65d570f114	Vendor route-proxy's SDK so its provider builds offline (issue 1019)	2026-10-17 18:15:43 +02:00
jschoubben	1586bd1134	Bring build-agent and route-proxy in whole (issue 1019)	2026-10-17 18:15:33 +02:00