4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	6ac5c934d2	The gate holds no merge for a check: the hold, the turns, their stalled line and tools, and check-gates-merge go; the merge judges the operator's Approve alone (milestone 47/G, W11.14) ... ADR 0661: the check gates the ask, in one place (askWaits); once the Approve covers the heads (approvedWaits) no verdict, carry, composed check or required status is judged, an Approve given before a trunk move merges onto the new trunk, and a failure after the Approve is said once on the pull request and as a stalled line naming the merge it follows. A check failing before the answer withdraws the ask. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ (Joined from 43696644.) Builds: design 47 G §278, test 52 (GATE10) Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ	2026-11-11 14:43:01 +01:00
jschoubben	cb5a8dd98e	The gate keeps one delivery record per milestone's delivery on its ledger (milestone 47/G, W11.1) ... ADR 0656 §7 and design 47 (The delivery record): the gate asks the bus module for a ledger `records` (template ledger, capped at 768 MiB) with two types: a record, keyed by its milestone and its heads, whose operations open it, write its group state, trace, outcomes, nodes away, pinned revisions and end, and remove it; and a month's list of the records opened, since a bundle cannot list a ledger's instances. An open of heads already recorded leaves the record as it is, an outcome applied twice writes nothing, and each open removes the records past the setting record-retention (90 days by default), naming each revision they pinned. The layout is the gate's own (design 20). Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ (Joined from 84eda463.) Builds: design 47 G §141, §142, §143, §144, §145, §146, §155, §34 (GATE1) Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ	2026-11-11 14:35:53 +01:00
jschoubben	32ad59fc64	mesh-delivery-gate and gitea: a setting check-gates-merge; false asks a reviewed pull request's Approve and merges it without waiting for mesh/check ... The operator, 2026-10-25 22:56: "run the check locally only, but not as a gate, it loses us too much time". Tonight each merge ask waited 3-7 minutes for mesh/check, and every merge into main refused the next approved merge for a check judged on the trunk before (mesh-delivery#52). Both settings default to true, so nothing changes until the operator sets them. False: the gate makes a reviewed pull request ready and asks its Approve with no verdict, a trunk's move puts nothing out of date, a verdict is kept and shown, and a group still merges in one pass; the merge tool merges a head the Approve names whatever its mesh/check says. delivery_status and show say the mode.	2026-10-25 23:07:50 +01:00
jschoubben	b5908b486e	Give the gate a settings file for the bounds ADR 0505 sets on saying a refusal and a needed new head	2026-10-22 14:12:31 +02:00