3 Commits

Include renames

Author	SHA1	Message	Date
jochen	758537dd4e	Plan a controller merge in the worker-of order in the three-kinds test ... The test's fixture had no worker-of edge and expected the builder first, then the controller and the proxy together: the order before hq issue 206. Since then the build seat's holder follows the controller that defines its worker, and every controller merge plans controller, builder, proxy in three tiers. The fixture now carries the edge and the test that order.	2026-10-08 22:22:24 +02:00
jochen	add807f034	Say no cycle for a packages edge in a plan's last tier ... A packages edge orders nothing, so a module and what packages its source share a tier by rule; hasCycle counted the edge and the merge handler said "the last tier depends on itself" of plans with no cycle. Skip the kind as tiersOf does. The planner tests' cycle rows and property now pass.	2026-10-08 22:22:02 +02:00
jochen	8ca4b04321	Hold the delivery planner to its recorded rules with a table and a property ... A table of merges (two repositories, every edge kind, a diamond, a cycle, files no build reads) and a seeded property over 500 random catalogues pin what a merge moves and in which tiers, per ADR 0162 and ADR 0238 §3. The shared-repository rows document today's behaviour that issue 338 would change, once with hand edges and once with edges derived from the store. The cycle check fails on main: hasCycle reads a packages edge between two modules of the last tier as a cycle, so a plan with none is said to have one. Left failing, marked BUG, for the planner's fix.	2026-10-08 22:15:20 +02:00