Take the build agent and the toolchain images out of the catalogue's prose, and refuse the word where it comes back outside the one module still naming it (issue 1295, E6)

modules/gitea/README.md

@@ -161,7 +161,7 @@ listed repository:
 - one in the organisation is only put right: main's rule narrowed, `mesh/check` required in place of
   `mesh/merge-gate` and `mesh/repo-check`, and every other status already there kept. A main that requires
   `mesh/repo-check` alone (hq's did, until issue 1296) is given `mesh/check` in its place too, since nothing writes
-  `mesh/repo-check` once build-agent is gone (ADR 0527 §2); `mesh/check` is never dropped.
+  `mesh/repo-check` once the merge check's second layer is gone (ADR 0527 §2); `mesh/check` is never dropped.
 
 Every other repository of the organisation whose main requires `mesh/merge-gate` or `mesh/repo-check` has the old statuses swapped
 for `mesh/check`, and only its statuses (issue 1301): the switch reaches every repository the merge gate judged, with

modules/gitea/cmd/repositories/repositories.go

@@ -39,8 +39,8 @@ const (
 
 // wanted is what a main rule requiring have should require: have with GateStatus and OwnCheckStatus replaced by
 // CheckStatus, every other status kept in its order (ADR 0447 §1). A rule requiring OwnCheckStatus alone, as hq's
-// did, is swapped too: the checker judges hq like any repository and nothing writes OwnCheckStatus once build-agent
-// is gone (ADR 0527 §2, issue 1296). This reads the rule, not a list of names (lead decision L11 of R4e).
+// did, is swapped too: the checker judges hq like any repository and nothing writes OwnCheckStatus once the merge
+// check's second layer is gone (ADR 0527 §2, issue 1296). This reads the rule, not a list of names (lead decision L11 of R4e).
 func wanted(have []string) []string {
 	out := []string{}
 	for _, s := range have {

modules/gitea/provisioner/teams.ts

@@ -2,7 +2,7 @@
 // half of the provisioner around it — pure of the forge's address, so it is tested with a stand-in.
 //
 // **Two teams, by what the consumer said it needs** (novox/hq issue 624). A consumer that publishes —
-// the build agent, whose builds publish the SDK and every TypeScript module's packages — joins `packages`:
+// the build modules, whose builds publish the SDK and every TypeScript module's packages — joins `packages`:
 // code read on the org's repositories and write on its packages. A consumer that contributes
 // `{"access": "read"}` joins `readers`: code read and package read, and no write. The lab is the first: it
 // clones branches that are not yet reviewed and runs their code beside its credential, and code that is