1316 Commits

Include renames

Author	SHA1	Message	Date
jochen	95089762ef	mesh-mail: retry the outcome's own write on a changed revision, and never ack or emit an outcome that could not be kept (review round 1 finding 5; issue 1198)	2026-10-19 10:43:45 +02:00
jochen	ce3b12f349	mesh-mail: emit mail.send.failed when the sender's own claim refuses or finds a send already sending, same as a failed send after it (review round 1 finding 4; issue 1198)	2026-10-19 10:40:41 +02:00
jochen	acb82992ee	mesh-mail: index a send for a tell or mail_health's overdue check before its record carries the outcome, drop the old index entry only after, and report an index write that fails instead of dropping it silently (review round 1 finding 3; issues 1194, 1199)	2026-10-19 10:38:07 +02:00
jochen	0a7669b48f	mesh-mail: a send still approved (the tools' own publish-then-record race) is redelivered later, never refused or told (review round 1 finding 2; issue 1196)	2026-10-19 10:31:39 +02:00
jochen	f140099a75	mesh-mail: declare the sender's own secret broker-send, so the controller can issue its account (review round 1 finding 1; issue 1172)	2026-10-19 10:29:48 +02:00
jochen	f3a59ee63a	mesh-mail: tell the operator once for a failed approved send and once more if its sender has not taken it, make an overdue send unhealthy, and give mail_send_status its full vocabulary (ADR 0436 clauses 11, 12; issue 1199)	2026-10-19 10:22:27 +02:00
jochen	33a97e6d13	mesh-mail: the sender records a send's outcome, retries a not-taken failure and emits mail.send.sent or mail.send.failed, acknowledging only once it is kept (ADR 0436 clauses 10, 11; issue 1198)	2026-10-19 10:11:41 +02:00
jochen	e7dce9616c	mesh-mail: classify an SMTP send's outcome (not taken, refused, not proven), and carry the send id in the Message-ID (ADR 0436 clause 10; issue 1197)	2026-10-19 10:03:44 +02:00
jochen	1ccb617a86	mesh-mail: the sender verifies the operator's warrant again from the router's own record and claims a send once before any connection (ADR 0436 clauses 9, 10; issue 1196)	2026-10-19 09:57:07 +02:00
jochen	dd3ed68483	mesh-mail: a send process that connects on its own bus account and consumes the mail-sends queue, stopping cleanly on a signal (ADR 0436 clause 7; issue 1195)	2026-10-19 09:49:24 +02:00
jochen	428b42181d	mesh-mail: on the operator's Approve the tools record approved and queue the send for the sender, instead of sending it themselves (ADR 0436 clause 8; issue 1194)	2026-10-19 09:44:42 +02:00
jochen	59c0906c79	mesh-mail: move password reading out of the tools' reach into its own package, so only keep and the send actor import it (ADR 0436 clause 12; issue 1193)	2026-10-19 09:32:54 +02:00
jochen	75a9a45c6f	mesh-mail: pin mesh-sdk go to release 2, declare the sender account, bus process and work-queue stream (ADR 0436 clauses 7, 8; issue 1172)	2026-10-19 09:23:45 +02:00
jochen	a32b7af3fd	Ask a refused merge again when its checks turn green on the forge (issue 1144)	2026-10-18 23:50:25 +02:00
mesh-tools	a6295d6b98	Merge pull request 'Write a provisioner client's files only on a change over the bus, never on a timer (issue 1129, ADR 0430)' (#366) from fix/1129-no-drift-pass into main	2026-10-18 16:56:32 +00:00
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
jochen	e7ff7c3045	Write a provisioner client's files only on a change over the bus, never on a timer (issue 1129, ADR 0349 clause 4)	2026-10-18 18:08:50 +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