6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	32655b95f6	GIT1, GIT2, GIT3, GIT10: the forge module serves the seat git's verbs and says its events, retires its acting tools, follows the catalog half ... The four share files (index.ts, module.json, guard.test.ts), so they land as one commit. GIT1: seat.ts serves pull, open-pulls, tags, trees, file, contains, statuses, status, comment, view, note, merge-pull as tools on the seat, each answering the contract's shape and an error of kind refused, not-found or failed; a comment, view or note whose act id is held is answered held (note matched by id). merge-pull merges the head the caller names (its from-G judgements are GIT6, GIT7, GIT9). GIT2: seatevents.ts says pull-updated, pull-merged, pull-closed, forge-pull, forge-status, forge-delete and repo-writable on mesh.seat.git.event.<event>; the module's emits drop them. GIT3: merge.ts, check.ts, the acting tools, the owed watch, the gate's source read and check-gates-merge are gone. GIT10: catalog.ts follows the seat mesh-catalog (revision, catalog-revision); no write is granted before the first view. Builds: design 47 G §310, §311, §312, §313, §314, §163, §317, §278, §321, §196 Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ	2026-11-11 11:31:24 +01:00
jschoubben	5450707aaf	CAT-G2: gitea reads no MESH_* word nothing sets ... The forge's container is the manifest's name, and the hand-run token is GITEA_TOKEN alone (checks/environment). Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig	2026-11-04 14:57:22 +01:00
jschoubben	7afcd0282d	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) ... At 12:37 on 2026-10-24 node-tools on novox was replaced; gitea's watcher bundle awaited the webhook's set-up on the forge's admin API at the top of its import, outlasted the 10 s handshake and was killed, never to start again. gitea_commit_status, gitea_merge_pull_request and gitea_events were then served nowhere: the forge bridge's calls found no responders and no new pull request was announced.	2026-10-24 13:00:57 +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
jschoubben	77f3963d83	Test that the gitea bundle's import resolves while its binds are refused (issue 1793)	2026-10-22 00:49:27 +02:00