4 Commits

Include renames

Author	SHA1	Message	Date
jochen	3d05d74400	Publish only a commit on its module's trunk; post a pull request's change plan (hq ADR 0238) ... One commit, one plan: a commit off the trunk — a pull request's head, a branch built by hand, a rebuild or replay of one — is for checking. The build seat reads from its clone which branches hold the commit, and the controller records and never registers a build whose commit is not on the branch the module follows (the repository's default for a new one), so nothing off the trunk can be sent. A pull request's check now carries its change plan, computed by the planner: what a merge would build in which order, what each machine would receive, and what is not an ordinary send — the bus step, a module waiting for a person, a provider's consumers.	2026-10-06 22:49:55 +02:00
jochen	58ebe590a5	Ask the planner what a pull request reaches; map a changed file onto modules in one place (hq ADR 0238) ... touchedBy is now the only mapping of changed files onto modules — touched, added, and read by no build — and reachOfMerge the planner's whole answer with the dependency walk. The merge handler, the plan what-if, the merge gate's width and composition, and a pull request's check all ask it, so planning and gating cannot disagree. The gate composes the definitions of the modules a merge would rebuild or add, not every one in the tree, and the check says the dependents a merge would build after them.	2026-10-06 22:34:57 +02:00
jochen	9c714f00d6	Judge every pull request against the mesh that runs, before it merges (hq ADR 0237, to-be 45 §9) ... Every check the mesh had ran after a merge, on a machine: a manifest the node-engine refused (236), an identity a real machine's name made too long (263). merge-gate raises the mesh as the facts snapshot says it is and the mesh with the change, each in a throwaway store through the controller's own records, composes every machine twice and validates it with the node-engine's validator, and fails what the change breaks, naming the machine's roles and the module - plus a manifest the judging controller cannot read, a consumer left out of its grant, a module removed while a machine runs it, a new module the node-engine would refuse; it warns on a wide rebuild. The forge's new head of a pull request becomes a check the controller asks of the build seat: the head and, beside it, the controller the mesh runs, the catalogue, the host and the lab; a throwaway store and bus of the versions the mesh runs; the repository's merge-check.sh in the mesh's Go toolchain with no container runtime socket; then mesh-lab's replays. The verdict is said as checked, an error never a pass, and nothing is recorded or registered.	2026-10-06 21:11:26 +02:00
jschoubben	c585158836	The two seat commands appear in the usage text ... Both existed and neither was listed: rename since ADR 0122, the handover since ADR 0131. Found by asking the running binary for help and seeing only the list.	2026-09-27 23:45:59 +02:00