4 Commits

Include renames

Author	SHA1	Message	Date
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
jschoubben	5a7076a6a2	Take the checker's owed without waiting on the forge, so a large owed never times its watch out (issue 1726) ... The runtime gives a watch's current values 10 s and waits for each to be taken; a forge write per key made ~200 keys outlast it at every attempt, so after node-tools restarted on novox at 23:25:58 the watch never held and no verdict reached mesh/check. Writes now run in the background, a few at a time, each key's in revision order.	2026-10-23 23:52:52 +02:00
jschoubben	896bd88380	Write mesh/check from the checker's owed state, read by a watch (R2-1) ... R4e round 2 finding R2-1, ADR 0521: the delivery plan draws no edge that orders the forge module before the forge bridge, and the forge module's durable consumer keeps its deliver policy when its filters change, so a check.status the bridge emitted before the forge module consumed it was lost. An in-memory revision guard also forgot itself on a restart. The forge module now reads mesh-delivery-checker.owed, which the checker announces readable, by a watch: the watch hands over the latest value of every key whenever the module starts, so a status written while it was away is written then, and only the latest. Each mesh/check is written once per revision, an older one dropped; a forge refusal is asked again on a bound until written or overtaken; a refused read is said once and asked again until granted. No tool writes mesh/check, and no check.status is consumed.	2026-10-22 21:45:53 +02:00
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