jschoubben f52545c4ba Stop asking the forge again for a mesh/check it refuses for good, and end the ask when its key is deleted (issue 774) ...

gitea asked an owed status again every 30 s forever, even on 403 and 404 (jschoubben/hal and jschoubben/novadock, 119
times each in the sweep), and a key the checker deleted did not end a loop already running.

Quick fix: return from askAgain on 403/404. Thorough fix: the same, said once with its cause; a delete of the key
marks its revision seen, so any running ask again ends before its next write; a newer revision still asks anew.
The checker no longer owes statuses outside the mesh (mesh-delivery), which removes the trigger. Not done: raising
the module's health, since gitea's TypeScript SDK has no seat publish for a condition (mesh-sdk).

2026-10-30 18:23:55 +01: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

Set up the forge's webhook without holding the bundle's import, so a slow forge never costs gitea its handshake and its tools (issue 1726)

2026-10-24 13:00:57 +02:00

check-owed.test.ts

Stop asking the forge again for a mesh/check it refuses for good, and end the ask when its key is deleted (issue 774)

2026-10-30 18:23:55 +01: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

gitea commit trees: drop the listed directories, which only the bridge's placement files used

2026-10-28 18:12:13 +01:00

delivery.test.ts

Write mesh/check from the checker's owed state, read by a watch (R2-1)

2026-10-22 21:45:53 +02:00

gate.test.ts

gitea: judge and write only the statuses a base requires, so merges go on mesh/check (issue 1301, S5-S7)

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

guard.test.ts

gitea: set a default branch and a pull request's base by named tools; announce a retargeted pull request again (issue 1422)

2026-10-28 11:07:31 +01:00

kept.test.ts

Announce every state another module reads as readable, and refuse a catalogue that does not (issue 774)

2026-10-30 18:07:53 +01:00

mainrules.test.ts

Gate the token mint's main-rule write by keep-main-rules too

2026-10-23 15:57:44 +02:00

merge-retry.test.ts

Merge an approved group only when every member merges now, and let no other merge land between its members (issue 1275)

2026-10-26 14:53:22 +01: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

gitea: set a default branch and a pull request's base by named tools; announce a retargeted pull request again (issue 1422)

2026-10-28 11:07:31 +01:00

protection-full.test.ts

gitea: gate and judge every trunk the gate's source names, not main alone

2026-10-28 16:52:50 +01:00

protection-read.test.ts

gitea: require no status on main, judge mesh/check in the merge tool instead (ADR 0534)

2026-10-23 12:01:57 +02:00

protection.test.ts

gitea: keep the operator's own login on main's merge whitelist beside mesh-tools (ADR 0534 §2)

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

pulls.test.ts

gitea: set a default branch and a pull request's base by named tools; announce a retargeted pull request again (issue 1422)

2026-10-28 11:07:31 +01: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

team-rights.test.ts

gitea_team_rights: refuse a forge user that does not exist; keep ForgeRepository's doc comment on it (issue 1563)

2026-10-27 21:54:51 +01: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

gitea: fail a protection or settings write the forge answered and did not apply, and take every field gitea 1.27.3 edits

2026-10-28 16:39:54 +01:00

tools-account.test.ts

gitea: mesh/check is the mesh's own status and never blocks; signed commits, an outdated branch and a rejected review are said as blocking the mesh's merge (issue 1945, review round 2)

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

trunk.test.ts

gitea: the merge tool reads a carried verdict's line as judged on the new trunk, so it merges a carried verdict (ADR 0548 §8; issue 568, review round 1)

2026-10-26 12:15:20 +01:00

watch.test.ts

Gitea announces from the forge's events and one pass at the start, not by polling (issue 1422)

2026-10-28 12:05:03 +01:00

webhook.test.ts

Gitea announces from the forge's events and one pass at the start, not by polling (issue 1422)

2026-10-28 12:05:03 +01:00