gitea: graph-driven announce, both check statuses, the change plan, branch-protection tools (hq ADR 0238) #98

2026-10-06T20:51:29Z

mesh-admin commented

2026-10-06 20:51:29 +00:00

Implements the forge side of hq ADR 0238.

pull.updated carries what the controller maps a PR onto the module graph with: module_dirs at the head (issue 278), removed, and merge_check (whether the head has a merge-check.sh). Every PR the forge holds is announced; the controller decides.
A verdict sets mesh/merge-gate (the gate: modules moved, dependents, the change plan's summary) and mesh/repo-check (the repository's own merge-check.sh). A change that builds something gets its change plan as a comment; a failing/erroring layer gets the check's account.
New tools gitea_branch_protection_get / gitea_branch_protection_set (edit the branch's rule — required statuses replaced, everything else kept — or create one that refuses direct pushes unless push=true; optional block_admin_override). Pure body logic in protection.ts, tested.
merge-check.sh is the catalogue's own layer: every manifest through the running controller's module check, the touched Go modules' tests (-race when gcc); TypeScript modules and unfetchable deps said as not tested.

Tested: node --test for pulls/protection (the pre-existing client test a commit status is set on the commit fails as on main: client.ts imports ./token.js, which strip-types cannot resolve); tsc clean in the TypeScript toolchain.

Pairs with mesh-controller #101. Do not merge before review.

Implements the forge side of hq ADR 0238. - `pull.updated` carries what the controller maps a PR onto the module graph with: `module_dirs` at the head (issue 278), `removed`, and `merge_check` (whether the head has a merge-check.sh). Every PR the forge holds is announced; the controller decides. - A verdict sets `mesh/merge-gate` (the gate: modules moved, dependents, the change plan's summary) and `mesh/repo-check` (the repository's own merge-check.sh). A change that builds something gets its change plan as a comment; a failing/erroring layer gets the check's account. - New tools `gitea_branch_protection_get` / `gitea_branch_protection_set` (edit the branch's rule — required statuses replaced, everything else kept — or create one that refuses direct pushes unless `push=true`; optional `block_admin_override`). Pure body logic in `protection.ts`, tested. - `merge-check.sh` is the catalogue's own layer: every manifest through the running controller's module check, the touched Go modules' tests (-race when gcc); TypeScript modules and unfetchable deps said as not tested. Tested: `node --test` for pulls/protection (the pre-existing client test `a commit status is set on the commit` fails as on main: client.ts imports ./token.js, which strip-types cannot resolve); tsc clean in the TypeScript toolchain. Pairs with mesh-controller #101. Do not merge before review.

mesh-admin added 3 commits 2026-10-06 20:51:29 +00:00

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) bd7b757dd9

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.

gitea: tell the controller which files a pull request deletes; say the dependents a merge would build (hq ADR 0238) dba71a97a8

The controller asks its planner what a pull request reaches, as if merged: a module whose
manifest the change deletes is one the merge removes, and the plan's dependents are said
on the gate's status beside the modules it moves.

gitea: post a pull request's change plan with its verdict (hq ADR 0238)

mesh/merge-gate pass: the merge check passed

mesh/delivery superseded: a newer head of the same pull request

Details

cc1305a354

The gate's status says what the change does and how it was judged; a change that builds
something gets its plan as a comment — the tiers, what each machine receives, and what
is not an ordinary send.

jschoubben added 1 commit 2026-10-06 20:54:55 +00:00

Test the modules the planner says the change reaches (hq ADR 0238)

mesh/merge-gate pass: the merge check passed

mesh/delivery delivered

Details

mesh/delivery-group group feat/the-graph-decides-what-is-checked merged: every member is merged

Details

81641a4b22

mesh-admin merged commit 88135ad0e7 into main

2026-10-06 21:00:27 +00:00

mesh-admin deleted branch feat/the-graph-decides-what-is-checked

2026-10-06 21:00:28 +00:00

mesh-admin commented

2026-10-06 23:08:50 +00:00

Delivery novox/mesh-catalog@cc1305a3541d — superseded since 2026-10-06T23:05:28Z

Group feat/the-graph-decides-what-is-checked, in order:

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#98's head announced
2026-10-06 23:05 proposed → checked (checked): the verdict names this commit
2026-10-06 23:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-06 23:05 ready → superseded (new-head): a newer head of the same pull request

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@cc1305a3541d` — **superseded** since 2026-10-06T23:05:28Z **Group** `feat/the-graph-decides-what-is-checked`, in order: **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#98's head announced - 2026-10-06 23:05 proposed → checked (checked): the verdict names this commit - 2026-10-06 23:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-06 23:05 ready → superseded (new-head): a newer head of the same pull request The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin referenced this pull request

2026-10-12 22:54:44 +00:00

build-agent: declare busy, so a replaced agent finishes the check it runs (issue 594, hq ADR 0335) #260

mesh-admin referenced this pull request

2026-10-13 22:07:58 +00:00

build-agent: declare busy, so a replaced agent finishes the check it runs (issue 594, hq ADR 0335) #283

mesh-admin referenced this pull request

2026-10-13 22:34:52 +00:00

build-agent: declare busy, so a replaced agent finishes the check it runs (issue 594, hq ADR 0335) #283

mesh-tools referenced this pull request

2026-10-26 17:35:05 +00:00

The catalogue's placement files: listed at a merge and checked (issue 1126) #505