jschoubben 8d3f81c2c0 Write mesh/check from the forge bridge's own event, never from a tool (K1) ...

Review finding K1 of R4e, issue 1301 S4 (ADR 0503 §3, ADR 0513 §4: the forge
requires mesh/check alone). gitea_check_status assumed only the bridge could
call it, but a tool is told no caller and node-tools invokes every tool, so any
session could set mesh/check to success and merge past the checker: the fault
issue 293 closed for the two statuses before it.

gitea now consumes mesh-delivery-forge-bridge.check.status, a subject the bus
grants to the bridge's own account alone, and check.ts writes mesh/check from
it: the source is checked, the head's whole sha and the state, and a revision
older than one already written on the head is dropped so a redelivered stale
pending never hides a verdict; a forge refusal throws, so the event is
delivered again. gitea_check_status is removed, and gitea_commit_status keeps
refusing mesh/check.

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

Write mesh/check from the forge bridge's own event, never from a tool (K1)

2026-10-22 21:14:01 +02:00

check-event.test.ts

Write mesh/check from the forge bridge's own event, never from a tool (K1)

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

Answer each named path's git object id from gitea_commit_trees (issue 1758, S1-S2, ADR 0499 §3)

2026-10-22 17:59:23 +02:00

delivery.test.ts

Write mesh/check from the forge bridge's own event, never from a tool (K1)

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

Write mesh/check from the forge bridge's own event, never from a tool (K1)

2026-10-22 21:14:01 +02:00

kept.test.ts

Say gitea's states with the SDK's emit, as the toolchain's SDK has no keeps yet (issue 1790, issue 1852)

2026-10-22 19:04:21 +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

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

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

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

webhook.test.ts

mesh-delivery-gate: read mesh/check alone on a base that requires it (issue 1302, S1-S10)

2026-10-22 17:50:25 +02:00