7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	66dc501fc4	Split the unit level from the integration level in cmd, builder, link, catalogue, inventory; cheap fixtures for the archive-entry bound, the registry waits and the catalogue copy (issue 895)	2026-10-17 21:32:23 +02:00
jschoubben	81715273d3	issue 1025: the operator's Approve of a reviewed group registers a moved module from its new repository (ADR 0420 §7)	2026-10-17 15:56:49 +02:00
jochen	1560c498b6	Ask the rollback test's failed build after the registered one, whenever it runs ... Its id named 2026-10-10 02:40 UTC; once the clock passed that, the registered build read as newer and the test failed on main.	2026-10-10 12:49:44 +02:00
jochen	eca6390d6f	Judge the one protection rule the forge applies, and keep a recorded repository id ... The forge applies the rule named for a branch, else the first glob covering it; the judge passed a branch whose applied rule let pushes when a later rule happened to guard it. And a registration whose id the forge could not give cleared the id already recorded (the confirmation review of 2026-10-09).	2026-10-09 12:58:28 +02:00
jochen	95e7a7120a	Register only from a protected trunk of the same repository, and mark the serving controller never the terminal ... A source repository's name is not its identity, and a trunk anyone may push to makes the trunk rule mean nothing (the review of 2026-10-09). Through any verb a module now registers only from a repository on the mesh's forge whose trunk refuses direct pushes, requires a status and lets no administrator merge past one, asked of the forge's own tools; and only from the repository by the forge's id, recorded at registration (migration 0084), so one deleted and made again under the name is refused. The serving controller marks its environment, so nothing it runs or starts reads as the terminal, and a terminal request covers only the repository and path it asked.	2026-10-09 12:37:18 +02:00
jochen	1b780eae3a	Put back on a failed gate only a build of the module's own repository ... A build refused for its repository is still recorded, and a fork carries the commit the module was registered at: the rollback's search for the previous build would have found it and registered it by the back door.	2026-10-09 12:37:18 +02:00
jochen	a5e8baf6da	Register a module only from the repository the catalogue builds it from ... An agent could make a repository of its own, or fork one the mesh builds from, commit a module.json naming sudo or mesh-host, and ask the build verb for it: the outcome was registered under that name, and the next push made whoever wrote it root on every node (novox/hq ADR 0266 §7, the review of 2026-10-09). The trunk rule checked the trunk of the repository built, which was the agent's. The take-in, which every outcome reaches whichever verb asked it, now registers a module only from its registered repository, and a new module only from a repository the catalogue already builds from (a merge adding one); anything else only when the build request was kept as asked at the controller's terminal (migration 0084). Through a verb, a build of a repository the catalogue builds nothing from is not asked at all.	2026-10-09 12:37:18 +02:00