diff --git a/modules/gitea/index.ts b/modules/gitea/index.ts index 4c89e9eb..d9c78c82 100644 --- a/modules/gitea/index.ts +++ b/modules/gitea/index.ts @@ -14,7 +14,8 @@ // `mesh/repo-check`, the repository's own merge-check.sh (novox/hq ADR 0237 as amended); with a comment // saying why when the gate is not a pass or the repository's own check failed. Of the two, only those the base // still requires are written (issue 1301): main requires `mesh/check` — the checker's — everywhere, hq included since -// ADR 0527 §2, so these are written only for a revert. +// ADR 0527 §2, and since R4g no controller judges a merge (its merge gate went with build-agent, ADR 0524 §5), so nothing +// publishes mesh-controller.checked and these two are written for no base. // // Reads mesh-delivery-checker.owed — what the checker owes the forge, mesh/check on each head it judged — by a watch, and // writes it (check.ts; ADR 0521, R4e finding R2-1). No tool writes mesh/check (finding K1), and no event: the watch hands diff --git a/modules/gitea/merge.ts b/modules/gitea/merge.ts index 832ae958..de2ce654 100644 --- a/modules/gitea/merge.ts +++ b/modules/gitea/merge.ts @@ -6,8 +6,8 @@ // Each bundle the runtime serves is its own process; from the tools' bundle the pending bypassed the writer's chain. // // **It judges on the status the base requires** (issue 1301; ADR 0447 §1, §4; ADR 0503 §5): mesh/check, the checker's, -// whose line names the trunk it judged ("pass on "); where a base does not require it, the controller's -// status it still requires (only on a revert), as before. A mesh/check of another trunk is refused and nothing is +// whose line names the trunk it judged ("pass on "). Every base requires it since ADR 0527 §2; a base +// that still required a controller's status would wait for good, as no controller writes one since R4g (ADR 0524 §5). A mesh/check of another trunk is refused and nothing is // asked: the checker sets it out of date on the trunk's move and checks it again. import { announce } from "./announce.js";