jschoubben 5e24deb0f1 gitea: require mesh/check in place of the two old statuses on every main the gate judges (issue 1301, S1-S3) ...

ADR 0447 §1 has main require mesh/check alone. The repositories program now
requires it in place of mesh/merge-gate and mesh/repo-check on every listed
repository and on every other one whose main requires mesh/merge-gate, so the
switch needs no hand-kept list (lead decisions L4, L11). A main requiring
mesh/repo-check alone (hq) keeps it until issue 1296 (ADR 0503 §5).

2026-10-22 17:49:53 +02:00

..

agent-teams

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

agent-token

One forge user, nox-agent, for every machine's agents' SSH pushes, each machine's key titled by machine (issue 991, ADR 0410)

2026-10-17 00:46:43 +00:00

forge

Anchor patch hunks as git apply does, refuse patches touching non-100644 files by their real mode, survive bare-CR context lines (issue 1604 review)

2026-10-21 09:52:10 +00:00

forge-account-provider

Let gitea read the image build module's keys, so its key is the builders' (issue 1703f)

2026-10-22 10:27:01 +02:00

npm-registry

gitea forge bundle: name the parent the forge used, match protection rules as the forge does, bound a commit's size and a search's time (issue 539)

2026-10-12 12:51:22 +02:00

repositories

gitea: require mesh/check in place of the two old statuses on every main the gate judges (issue 1301, S1-S3)

2026-10-22 17:49:53 +02:00