8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	efca168c55	Stop the forge bridge performing mesh/check: the forge module writes it (R2-1) ... R4e round 2 finding R2-1, ADR 0521: nothing in the delivery plan orders the forge module before the bridge, and the forge module's durable consumer keeps its deliver policy when its filters change, so a check.status emitted before it consumed the event was lost. The forge module now watches the checker's owed state and writes mesh/check itself, once per revision. The bridge emits no check.status, declares no emits, and neither reads the checker's owed nor hears its stream; OwedAct still refuses mesh/check. The integration test shows the bridge calls no tool and publishes nothing of its own when the checker owes mesh/check.	2026-10-22 21:40:09 +02:00
jschoubben	bb4a4a82dc	Emit mesh/check as the bridge's own check.status, never through 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 rested on "only the bridge invokes it", but node-tools invokes every tool and a tool is told no caller, so any session could set mesh/check and merge past the checker. The bridge now emits check.status on mesh.mod.mesh-delivery-forge-bridge.event. check.status, which the bus grants to its own account alone (emits), with the owed status, its key and its revision; the event id check.<key>.<rev> is the bus's dedup id. A status the bus did not take is not kept as done. OwedAct refuses mesh/check, and gitea.gitea_check_status leaves the invokes. The integration test shows the tool runner's account refused on that subject and gitea's durable consumer handed statuses emitted before it fetched.	2026-10-22 21:23:27 +02:00
jschoubben	2855ae7ebf	Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A) ... The forge's gitea_commit_status refuses the context mesh/check from R4e, so that only the checker's account, through this bridge, can make a pull request pass the one required status.	2026-10-22 17:59:30 +02:00
jschoubben	96ba6bd3dc	Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)	2026-10-21 21:20:42 +02:00
mesh-tools	543d91d626	Read each module's manifest and lock files in the forge bridge, so the indexer gets them (issue 1448, design 47 R4c-2)	2026-10-20 18:51:27 +00:00
mesh-tools	507fac41fe	Declare the bridge's performed bucket (issue 1341)	2026-10-20 00:14:42 +00:00
jschoubben	ca667af562	Keep the head last written per pull request in a bucket of the bridge's own instead of scanning FORGE, and test the bridge under its composed permissions (issue 1279, ADR 0443)	2026-10-19 22:09:41 +02:00
jschoubben	1f9606654c	Write the forge's pull requests as messages on FORGE in a new forge bridge module (issue 1235)	2026-10-19 14:50:13 +02:00