13 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4a92ec6102	Pin mesh-sdk at the head after review round 1 ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 03:13:17 +01:00
jschoubben	909cc25169	Pin mesh-sdk at the judge-less release head in the controller and route-proxy ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 02:46:24 +01:00
jschoubben	0e9c4c8299	Check route-proxy's composed targets over the live shapes in an existing test's place, and pin the mesh-sdk that keeps unassigned bare ports (issue 774, research 072 row 34) ... The table covers gitea and grafana moved by the placement, influxdb's bare port, mailu's and photos' fixed mappings and home-assistant on the host's network; it replaces the loopback test it subsumes, so route-proxy's test count does not grow. The controller, NATS-native: no piece moves; route-proxy only.	2026-10-31 13:22:00 +01:00
jschoubben	14d10051e5	Dial a route at the machine port its module's placement assigned, from the mesh-sdk whose plans carry it (issue 774, research 072 row 34) ... route-proxy from plans dialled every route at the software's own port: gitea at 127.0.0.1:3000 (published at 20000) and grafana on ace at 3000 (published at 20012), and public sites answered 502. The proxy already reaches a module beside it over loopback and one elsewhere at the plan's address; the plan now carries the assigned port, and a test composes the plan with the SDK and reads it as the proxy does, so the two cannot drift again. The controller, NATS-native: no piece moves; route-proxy only.	2026-10-31 13:11:00 +01:00
jschoubben	a07621d761	Pin route-proxy at the group's mesh-sdk head acbf80a and its contract at the published tag v0.1.0, so it builds and reads the contributed payload; refresh its manifest digest for the events its contract names (issue 774)	2026-10-31 10:27:05 +01:00
jschoubben	22935b9202	Serve route-proxy's routes through its own contract: decode each plan entry's opaque contribution with it, say each name served, withdrawn or refused on the bus, and take who is inside from the seat mesh-placement, since the membership went with the assignments stream (issue 774, research 072 rows 33 and 34)	2026-10-31 09:44:07 +01:00
jschoubben	bfb728730f	Answer route-proxy's routes from the seat mesh-provisioner's plans and keys, not the controller's assignments, so a route the seat keys for a module not handed is marked provided and its new builds are no longer withheld (issue 774)	2026-10-31 00:27:11 +01:00
jschoubben	58512a9c6d	Pin mesh-sdk at the R4e member's final head 104533e8 and vendor it (R4e E) ... The SDK's S1 and S2 review fixes landed after 875c680d.	2026-10-22 21:19:46 +02:00
jschoubben	a0b2d98002	Merge main (upgrade safety's declared packages, issue 1840) and pin the R4e mesh-sdk member's final head 875c680d, re-vendored here and in modules/route-proxy; the controller announces declared-packages readable (issue 1790, D1; E)	2026-10-22 20:44:59 +02:00
jschoubben	499ff5c218	Move the route proxy into its module and run it from the trust image, on mesh-sdk's public membership (issues 1633, 1634, 1635) ... A bundle is built only from its module's directory (ADR 0480 clause 4), so the proxy leaves examples/ and the controller's internal/broker; the broker keeps no second copy of what the proxy shares with mesh-sdk. The image and its Dockerfile go, and a test holds that only build-agent declares one (clause 11).	2026-10-22 09:53:56 +02:00
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
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	1586bd1134	Bring build-agent and route-proxy in whole (issue 1019)	2026-10-17 18:15:33 +02:00