jschoubben 939475cb63 gitea: only the forge bridge writes mesh/check, through a tool of its own (issue 1301, S4) ...

Once main requires mesh/check, a hand that set it could pass a merge past the
checker, the gap issue 293 closed for the two statuses before it.
gitea_commit_status now refuses mesh/check in every state, and the new
gitea_check_status writes it alone; the bus grants that tool only to a module
whose manifest invokes it, the forge bridge (the lead's choice A).

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

..

announce.test.ts

issue 976: the forge's announcements get a deterministic message id; the announcement files go, the poll's watermark is kept in the module's state

2026-10-17 13:52:47 +02:00

announcing.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00

bind.test.ts

Start the gitea bundle's binds without awaiting them, so its handshake is answered while a refused bind is asked again (issue 1793)

2026-10-22 00:45:54 +02:00

bundle-import.test.ts

Test that the gitea bundle's import resolves while its binds are refused (issue 1793)

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

checks.test.ts

Cover a held merge only when the forge says a later delivered merge contains it (review of #150)

2026-10-09 02:57:18 +02:00

commit-trees.test.ts

Hash the root tree from the root's entries, since the forge names the commit (issue 1234)

2026-10-19 14:52:29 +02:00

delivery.test.ts

gitea: only the forge bridge writes mesh/check, through a tool of its own (issue 1301, S4)

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

gate.test.ts

Route a recheck's pending through the gitea module's one writer of mesh/merge-gate

2026-10-12 12:20:23 +02:00

guard.test.ts

gitea: only the forge bridge writes mesh/check, through a tool of its own (issue 1301, S4)

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

no-org-create.test.ts

Test that the gitea module makes the organisation's repositories from its config, protected before any team reaches them, and that no tool creates in the organisation (issue 1124, ADR 0428)

2026-10-18 16:45:49 +02:00

no-ready-mark.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00

pages.test.ts

Name the package each controller-repository image compiles, and say a renamed file under both names (hq ADR 0267, issue 363)

2026-10-10 02:58:31 +02:00

paging.test.ts

Page the announcer through every open pull request updated since its last look

2026-10-12 20:52:27 +02:00

protection-read.test.ts

Read branch protection as the forge's administrator, so builds register again

2026-10-15 00:18:39 +00:00

protection.test.ts

Main takes no push and only mesh-tools merges, set by setup and guarded (issue 948, ADR 0398 §2)

2026-10-16 21:28:43 +02:00

pulls.test.ts

Leave a composed member's gate to the group's verdict, reword the mark leftovers, restore main's merge-check.sh (issues 1022, 978)

2026-10-17 21:33:03 +02:00

rule-cases.json

guard.ts: cover every branch for a rule Go's regexp reads otherwise, and hold both matchers to one table (issue 539)

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

secret-setting.test.ts

Keep every password, token and API key the vault's, never a setting (hq issue 342)

2026-10-13 07:32:19 +02:00

siblings.test.ts

A group's composed verdict names each member's siblings at the heads it composed, so a sibling's own merge is no move (issue 1049)

2026-10-18 01:08:26 +02:00

teams.test.ts

lab: a read-only forge account of its own, and no credential left on disk after a stop (hq issue 624, review 196)

2026-10-13 14:00:59 +02:00

token.test.ts

Give the forge bridge a merge commit's trees in one call, and a pull request's head branch (issue 1234)

2026-10-19 14:50:19 +02:00

tools-account.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00

trunk.test.ts

Give the build agent a judge cache of its own, and prove a release branch's move puts its verdicts out of date

2026-10-14 13:48:30 +00:00

webhook.test.ts

Read a pull request's review record again when its description is edited, and ask the Approve again if it was unanswered (issue 1079)

2026-10-18 01:12:40 +02:00