5 Commits

Include renames

Author	SHA1	Message	Date
jochen	73bb597c16	Hold what the tools say to the glossary's retired words (hq ADR 0244) ... An agent meets the mesh's words most often in tool descriptions, and nothing compared them with the glossary: several still said "the host" for the node-engine and the forge's pull request comment was headed "Change plan", a word retired twice over. retired-words is the copy of the words the glossary retires for the tools, and checks/words fails the repository check when any string a module's code can show, or any manifest description, uses one. Those found are reworded here.	2026-10-07 20:02:09 +02:00
jochen	c0f9039695	Keep the count of long-running resources without health, and let it only go down (hq ADR 0240 rule 8) ... A field that is optional for ever is one half the catalogue never gets. The catalogue's merge check now holds the controller's count of long-running resources that do not say how they are ready to the number kept in health-undeclared: a change that raises it fails, one that lowers it must write the new number. Until the controller the mesh runs counts (Phase B), the check says it did not count.	2026-10-07 16:17:53 +02:00
jochen	81641a4b22	Test the modules the planner says the change reaches (hq ADR 0238)	2026-10-06 22:54:52 +02:00
jochen	bd7b757dd9	gitea: give the controller what it maps a pull request onto the graph with; set both check statuses; protect a branch by tool (hq ADR 0237) ... The controller now decides what a pull request's check runs from the mesh's module graph, so the announcement carries the changed directories that hold a module at the head and whether the head has a merge-check.sh. A verdict sets mesh/merge-gate (the gate, with the modules it judged) and mesh/repo-check (the repository's own tests). gitea_branch_protection_get/set let the operator's agent make those statuses required. The catalogue's merge-check.sh leaves the gate to the build seat and keeps its own layer: every manifest through module check, and the touched Go modules' tests.	2026-10-06 21:56:04 +02:00
jochen	9951718623	Check every pull request before it merges, and show the verdict on it (hq ADR 0237, to-be 45 §9) ... The forge's announcer announces each new head of an open pull request as pull.updated, once, and marks the head pending; the controller asks the build seat to check it against every machine of the mesh's facts, and says the verdict as checked, which the forge's holder sets as the head commit's status mesh/merge-gate - an error never as a success - with the check's own account as a comment when it is not a pass. merge-check.sh is the catalogue's check: every manifest through the running controller's module check and merge gate, and the Go tests of each module the change touches, a module whose dependencies cannot be fetched said as not tested.	2026-10-06 21:16:32 +02:00