1300 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	26d81b09b5	Register the repository mesh-delivery as an owner, so its issues can be located in it (issue 1133) ... The tracker runs with the manifest's owners default; a test now holds the default and the template's copy to one list.	2026-10-18 18:39:11 +02:00
jschoubben	54db38be08	gitea: a repository the module makes refuses an administrator's merge past its checks (issue 1141) ... narrowed never set block_admin_merge_override, so novox/mesh-delivery's main let an administrator merge past mesh/merge-gate and mesh/repo-check, unlike every other repository's main since 2026-10-07. narrowed sets it and isRight requires it, so the module's next start puts mesh-delivery right.	2026-10-18 18:10:29 +02:00
jschoubben	e75e793a4b	gitea: fill repositories.json through the provisioner client, so an approved value lands at once (issue 1128) ... The file was merged by the controller (merge, takes-config), which writes a config change only on the node's next send (ADR 0348 §10): the operator's Approve of the mesh-delivery repository set the value and nothing made it. A plain template saying ${config:repositories} is filled by the provisioner client on config-changed, and the node-engine reruns the run-once program that names the file under restart-on.	2026-10-18 17:40:59 +02:00
jschoubben	11761637cf	Put main's rule right again once a new repository is in the organisation: the forge drops a merger without access, and under the setup account the tools' account has none (issue 1124, ADR 0428 §3, review round 1)	2026-10-18 16:58:17 +02:00
jschoubben	8c587d0f00	Let the repositories pass's failed exit be its gate: a run-once step the node-engine runs again until it passes, its stderr naming each refused repository, step and forge answer, instead of a health check of its own (issue 1124, ADR 0428 §6)	2026-10-18 16:52:29 +02:00
jschoubben	df275b3c6e	Make the organisation's repositories from the gitea module's config value, protected under the setup account before they join the organisation, and take the owner argument from gitea_create_repo, since a repository's maker becomes its administrator (issue 1124, ADR 0428)	2026-10-18 16:49:12 +02:00
jschoubben	94b49a296f	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
jschoubben	0d3f0fd3fc	Let gitea_create_repo create in an organisation, saying the forge's refusal, so novox repositories can be made through the tools (issue 1124)	2026-10-18 15:45:01 +02:00
jschoubben	50fee22d0a	Test that gitea_create_repo creates in an organisation and says the forge's refusal (issue 1124)	2026-10-18 15:44:38 +02:00
jschoubben	6954467292	mesh-delivery bus test waits for the group's composed check, not a member's own check asked at once (issue 1115)	2026-10-18 12:33:02 +02:00
jschoubben	5f002441b7	mesh-delivery takes an empty answer to a check ask as a refusal (issue 1115)	2026-10-18 12:28:03 +02:00
jschoubben	fc9ddd9185	mesh-delivery adopts a standing verdict only when every required check stands, at every look, and counts an ask with no id as none (issue 1115)	2026-10-18 12:25:53 +02:00
jschoubben	1760b94824	mesh-delivery waits for nothing: a check is asked at once and a standing verdict adopted (issue 1115)	2026-10-18 12:22:31 +02:00
jschoubben	30d3bb9466	A pull request announced at a live head takes its delivery over when the other one closes or is edited (issue 1114)	2026-10-18 11:53:28 +02:00
jschoubben	bc1acddaa4	mesh-delivery hears the forge's own pull-request closed event as a close unmerged (issue 1107)	2026-10-18 04:55:48 +02:00
jschoubben	b0ec4f6f14	A group member refused for a pending status of its own asks its own check once, not the composed check (issue 1049)	2026-10-18 04:27:42 +02:00
jschoubben	3bc4215d87	Take the bus's backup guard out of modules/nats: it would move the bus (issue 1098, guard follows in issue 1104)	2026-10-18 03:55:50 +02:00
jschoubben	68e3326d4c	Providers and the provisioner client take the SDK that reads an ended assignment as a removed key (issue 1098)	2026-10-18 02:40:18 +02:00
jschoubben	84af0ed180	Guard that the bus storage stays declared as data with a backup (issue 1098)	2026-10-18 02:37:28 +02:00
jschoubben	9edd16eaeb	mesh-provisioner-client takes a module off the node when its assignment is ended (issue 1098)	2026-10-18 02:37:28 +02:00
jschoubben	60a3823f0e	mesh-vault reads an ended assignment as a removed key (issue 1098)	2026-10-18 02:37:28 +02:00
jschoubben	bdbca4b921	mesh-config drops an ended assignment as a removed one (issue 1098)	2026-10-18 02:37:28 +02:00
jschoubben	7383bc3170	A stale composed pass counts members judged since it was asked, whichever verdict lands first (issue 1047, review round 2)	2026-10-18 01:20:18 +02:00
jschoubben	ebd29223f3	Prove over a real bus that an edit of the description asks the Approve again (issue 1079, review round 1)	2026-10-18 01:18:43 +02:00
jschoubben	e8a74765f8	A composed check that lands judged against a trunk that has moved is out of date and asked again (issue 1047, review round 1)	2026-10-18 01:18:13 +02:00
jschoubben	6556e61485	Read a pull request's review record again when its description is edited, and ask the Approve again if it was unanswered (issue 1079)	2026-10-18 01:12:40 +02:00
jschoubben	93365be98f	A new pull request at a commit whose delivery was stopped and unmerged takes that delivery over (issue 1083)	2026-10-18 01:10:51 +02:00
jschoubben	814c1a991c	A trunk move asks at once the check of a group member whose Approve is not asked yet (issue 1047)	2026-10-18 01:10:12 +02:00
jschoubben	983e4a6444	A closed group's member whose merge was refused asks the composed check again at once, and a refusal loop past ten minutes is said (issue 1082)	2026-10-18 01:09:37 +02:00
jschoubben	da094008ea	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
jochen	684e8801c4	Take the ask back on the router when withdrawing a record (issue 1081, review round 1) ... WithdrawRecord only ended the waiting ask locally; the router kept it open, so the operator still saw Approve/Decline for a withdrawn record and an answer to it was dropped silently. It now also publishes a cancel on the router's subject once the withdraw is saved, as the controller's asker does; a cancel the router cannot be told of is logged and the withdraw still stands. The module's existing "uses": ["operator-channel"] already grants this; no manifest change needed, since the ask and cancel subjects are both under that seat.	2026-10-18 00:09:16 +02:00
jochen	6394a62a02	Merge remote-tracking branch 'origin/main' into fix/1081-withdraw	2026-10-18 00:03:16 +02:00
jochen	ddf7a5ab09	Let a proposed record be withdrawn (issue 1081) ... A dropped proposal or a stale reservation stayed proposed forever: there was no way to say the operator decided against it. knowledge-base.withdraw takes a reserved or proposed record to withdrawn as a new version naming why, ends a waiting operator's ask and clears a pending review in the same version, and refuses an already accepted, superseded or withdrawn record. The number stays spent either way. The old Withdraw (the background job for reservations never proposed) is renamed WithdrawStale to make room for the new, caller-driven WithdrawRecord.	2026-10-18 00:02:48 +02:00
jschoubben	4d03755c65	Bring the branch up to main after #354 (issue 1047: the trunk move asked no check)	2026-10-17 23:43:21 +02:00
jochen	bf3b3a5e36	Review round 1: list's pending ignores an ask that has ended, and its before cursor never cuts a page between a decision and research effort of the same number (issue 1064)	2026-10-17 23:09:46 +02:00
jochen	7bdb8f4782	Review round 1: list numbers combines search and before as AND, its limit defaults to the count asked and said names a cut; README names brief, numbers and worker (issues 1070, 1071)	2026-10-17 23:07:29 +02:00
jochen	b387cddc7c	Let the knowledge base answer its whole-set findings, whole or by record (issue 1069)	2026-10-17 23:01:22 +02:00
jochen	1cfbcf8e30	Let the knowledge base list its records by kind, status, topic or a flag (issue 1064)	2026-10-17 22:59:09 +02:00
jschoubben	c898a937a1	Order the events of the failed-backup bus test: each after the module took the one before (issue 1068)	2026-10-17 22:57:44 +02:00
jschoubben	82693a441c	A release the controller refuses to take leaves the delivery held for its failed backup (issue 1068)	2026-10-17 22:53:43 +02:00
jochen	1124f17912	Let issue-tracker.list take numbers and worker (issue 1070)	2026-10-17 22:50:09 +02:00
jschoubben	4799f79242	Read the plan's backups as the controller says them: machine, module, state, words (issue 1068)	2026-10-17 22:45:46 +02:00
jochen	01c9ab0cf5	Let issue-tracker.get answer briefly, with only its last note (issue 1071)	2026-10-17 22:45:42 +02:00
jschoubben	8f7aeeeb81	Hold a delivering delivery for a failed backup before the send; release asks the backups again (issue 1068)	2026-10-17 22:45:03 +02:00
jschoubben	914099774e	Record a backup that cannot start as the module's last night (issue 1067)	2026-10-17 22:42:21 +02:00
jschoubben	47e42806ff	Leave a composed member's gate to the group's verdict, reword the mark leftovers, restore main's merge-check.sh (issues 1022, 978)	2026-10-17 21:33:03 +02:00
jschoubben	2d3b61ec45	Merge a group in one pass on its one Approve, with no order and no turns (issue 978) ... A group has no order: mesh-delivery asks the controller for none, reads no after: line (it says once that the line is not read), merges every member in one pass once the composed check passed and the Approve covers the heads, and gives the plan its word once every member is merged. A failed member stops no other. The composed verdict sets each member's mesh/merge-gate (pending, saying why, until one stands), the groups answer says composed_gate, and a trunk move asks the out-of-date members' checks at once and merges on the same Approve (issue 1047).	2026-10-17 20:54:16 +02:00
jschoubben	668444785d	Ask the Approve as soon as the checks pass, with no ready mark (issue 1022) ... The review finishes before the push and its record is a Reviewed-by line in the description, so the mark repeated what the push meant. mesh-delivery asks the operator when a pull request's checks pass, keeps an ask through a trunk move by asking the check again at once, and hands the merge tool the approved heads, which replace the forge review of each sibling.	2026-10-17 20:44:54 +02:00
mesh-tools	7104df6fa2	Take in main's move of build-agent and route-proxy to mesh-controller (issue 1024) ... mesh-catalog #350 removed both modules from the catalogue; this change's edits to them go with them, and mesh-issues keeps both #350's change and its `unknown`. The branch's tree is the reviewed tree merged with main 5e6f5b8f6d.	2026-10-17 17:55:07 +00:00
mesh-tools	652b00b25b	Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422) ... Every directory and archive resource carries `unknown`: move-out for a home folder whose program writes nothing there (the node-engine, delivered in mesh-host #117, moves the rest to ~/.local/state/mesh-moved/<module>/ with a list), module for ~/.ssh and ~/.claude, program elsewhere; `knows` keeps what a program or the operator relies on (powerlevel10k's compiled files, i3's scripts and the asus/g14 drop-ins, dunst's slack rule, betterbird's records, node-env's forge credential, issue 1033). Two shared folders are no longer declared. Each module's README says it. checks/owned holds every manifest to it; checks/sshdir stays while main's merge check runs it (issue 1035). Tests that pin a manifest follow the new key only. Reviewed in three rounds.	2026-10-17 16:23:03 +00:00