novox/mesh-catalog
13
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

mesh-mail sends an approved mail from its own sender process, and tells a failed send once (ADR 0436, ADR 0438; issues 1172, 1193-1199) #371

Merged
mesh-tools merged 19 commits from feat/mail-sender into main 2026-10-19 11:36:51 +00:00
Conversation 2 Commits 19 Files Changed 27
+3782 -233
mesh-tools commented 2026-10-19 11:31:51 +00:00
Member
Copy Link
Copy Source

Release 3 of feature mail-sender (hq ADR 0436 clauses 7-12, ADR 0438). Fixes hq issues 1172, 1193, 1194, 1195, 1196, 1197, 1198, 1199 (1172 split into eight) and, once live, 871.

  • 1172: mesh-sdk go pinned to release 2 (go 1.26.0); manifest: user mesh-mail-send; own secrets mail-credential-* owned by it and broker-send (its bus account); stream mail-sends (work queue, 1 day, 64 MiB, 5 deliveries, 24 h duplicates); process send with its bus declaration; state directory 0711 and accounts.json 0644 (no password file widens; the lead's decision on 1172).
  • 1193: password reading in internal/secret, imported only by keep and the sender; a test fails if the tools' files import it; the tool path runs with no secrets directory.
  • 1194 (ADR 0438): on the operator's warrant the tools record queued first, then publish with the send id as message id; the sweep republishes a queued, unclaimed send older than a minute.
  • 1195: mesh-mail send connects on its own account (mesh-sdk go/process) and consumes MAIL_SENDS.
  • 1196: the sender re-verifies the warrant from the router's record under its own account, claims queued/retrying -> sending once; sending -> not proven; a repeat for a finished send is dropped untouched; a never-approved send is refused.
  • 1197: SMTP failures classified (not taken / refused / not proven); Message-ID carries the send id.
  • 1198: outcome recorded before ack (re-read once on a changed revision, else leave), retries after 1, 5, 15, 30 min, fifth = failed; mail.send.sent / mail.send.failed emitted; module-whole acceptance test on a real bus with a scripted SMTP server.
  • 1199: a failed, refused or not-proven approved send told once through operator-channel.tell (telling/told); an overdue send makes mail_health unhealthy and is told once; mail_send_status's words per ADR 0436 clause 12.

Try: build-1792409419207898338 passed (59 s; mesh-mail 4.2 s incl. its integration tests).

Delivery: moves mesh-mail on novox. The controller then mints broker-send (module issue). Live proof after the delivery: one mail_send from the mesh account to the gmail account, approved by the operator, arrives once and shows one new-mail notice on g14 and shanks (issues 871, 859, 865).

Reviewed-by: review-cat-mail-sender@g14 at a2c0c58677

Release 3 of feature mail-sender (hq ADR 0436 clauses 7-12, ADR 0438). Fixes hq issues 1172, 1193, 1194, 1195, 1196, 1197, 1198, 1199 (1172 split into eight) and, once live, 871. - 1172: mesh-sdk go pinned to release 2 (go 1.26.0); manifest: user mesh-mail-send; own secrets mail-credential-* owned by it and broker-send (its bus account); stream mail-sends (work queue, 1 day, 64 MiB, 5 deliveries, 24 h duplicates); process send with its bus declaration; state directory 0711 and accounts.json 0644 (no password file widens; the lead's decision on 1172). - 1193: password reading in internal/secret, imported only by keep and the sender; a test fails if the tools' files import it; the tool path runs with no secrets directory. - 1194 (ADR 0438): on the operator's warrant the tools record queued first, then publish with the send id as message id; the sweep republishes a queued, unclaimed send older than a minute. - 1195: `mesh-mail send` connects on its own account (mesh-sdk go/process) and consumes MAIL_SENDS. - 1196: the sender re-verifies the warrant from the router's record under its own account, claims queued/retrying -> sending once; sending -> not proven; a repeat for a finished send is dropped untouched; a never-approved send is refused. - 1197: SMTP failures classified (not taken / refused / not proven); Message-ID carries the send id. - 1198: outcome recorded before ack (re-read once on a changed revision, else leave), retries after 1, 5, 15, 30 min, fifth = failed; mail.send.sent / mail.send.failed emitted; module-whole acceptance test on a real bus with a scripted SMTP server. - 1199: a failed, refused or not-proven approved send told once through operator-channel.tell (telling/told); an overdue send makes mail_health unhealthy and is told once; mail_send_status's words per ADR 0436 clause 12. Try: build-1792409419207898338 passed (59 s; mesh-mail 4.2 s incl. its integration tests). Delivery: moves mesh-mail on novox. The controller then mints broker-send (module issue). Live proof after the delivery: one mail_send from the mesh account to the gmail account, approved by the operator, arrives once and shows one new-mail notice on g14 and shanks (issues 871, 859, 865). Reviewed-by: review-cat-mail-sender@g14 at a2c0c586772b2b325860235a8aa6748b39aa2083
mesh-tools added 19 commits 2026-10-19 11:31:51 +00:00
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) 75a9a45c6f
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) 59c0906c79
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) 428b42181d
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) dd3ed68483
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) 1ccb617a86
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) e7dce9616c
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) 33a97e6d13
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) f3a59ee63a
mesh-mail: declare the sender's own secret broker-send, so the controller can issue its account (review round 1 finding 1; issue 1172) f140099a75
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) 0a7669b48f
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) acb82992ee
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) ce3b12f349
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) 95089762ef
mesh-mail: tighten tests that proved less than their criterion — attempt 5 and no mail received (1198/AC4), mail_health actually turning unhealthy (1199/AC2), and the words mail_send_status gives, not only its status (1199/AC4) (review round 1 finding 6) 7397051771
mesh-mail: on Approve the tools record the send queued directly, with no separate approved state, then publish; a stuck queued record is republished by the sweep past a short grace, never NakWithDelay'd by the sender (ADR 0436 clause 8, decided to replace the review round 1 item 2 work-around; issues 1194, 1196, 1199) 1639269ad4
mesh-mail: fix the work-queue stream's real bus name (MAIL_SENDS, not MAIL-SENDS) and build the integration tests' stream, subject and duplicate window exactly as the controller composes them, exercising the send id's dedup (review round 1 finding 7; issue 1198) 7db4bd215d
mesh-mail: decide kept by settleSend's own returned revision, not its error, so a changed revision is actually retried instead of silently accepted as another writer's state; emit mail.send.failed from claimQueuedSend only once its own write lands (review round 2; issue 1198) 06dfce87f5
mesh-mail: the refused-sign-in acceptance test's wait excluded queued too, so it returned done on the very first look before the sender ever claimed anything (issue 1198) dd8305d97d
mesh-mail: a redelivery of a message whose send already finished (sent, failed, refused or not proven) is a repeat, terminated without recording, emitting or telling anything again (operator-approved change to ADR 0436 clause 10; issue 1196)
mesh/merge-gate head a2c0c586772b merged into trunk c441d83ba753 — pass: builds mesh-mail → novox; no bus step; every machine composes with the change as i…
Details
mesh/repo-check head a2c0c586772b merged into trunk c441d83ba753 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Details
mesh/delivery delivered
Details
a2c0c58677
mesh-tools commented 2026-10-19 11:31:59 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@a2c0c586772b — delivered since 2026-10-19T11:39:00Z

Delivery plan — builds mesh-mail → novox; no bus step

  • tier 0: mesh-mail
  • novox: receives mesh-mail

Machines

  • mesh-mail on every machine running it: sent

Transitions

  • 2026-10-19 11:31 (new) → proposed (announced): novox/mesh-catalog#371's head announced
  • 2026-10-19 11:35 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-19 11:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-19 11:36 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-19 11:36 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-19 11:39 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@a2c0c586772b` — **delivered** since 2026-10-19T11:39:00Z **Delivery plan** — builds mesh-mail → novox; no bus step - tier 0: mesh-mail - novox: receives mesh-mail **Machines** - mesh-mail on every machine running it: sent **Transitions** - 2026-10-19 11:31 (new) → proposed (announced): novox/mesh-catalog#371's head announced - 2026-10-19 11:35 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-19 11:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-19 11:36 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-19 11:36 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-19 11:39 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-tools commented 2026-10-19 11:35:10 +00:00
Author
Member
Copy Link
Copy Source

Merge check at a2c0c586
Judged: head a2c0c586772b merged into trunk c441d83ba753; read beside it: mesh-controller a5a43c8f31f0, mesh-controller-main a5a43c8f31f0, mesh-host 2474bf28330f, mesh-tools 7412c5b6c9c5

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-mail)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-mail → novox; no bus step

  • tier 0: mesh-mail
  • novox: receives mesh-mail
  • read by no module's build: modules/mesh-mail/cmd/mesh-mail/acceptance_integration_test.go, modules/mesh-mail/cmd/mesh-mail/claim_test.go, modules/mesh-mail/cmd/mesh-mail/config_test.go, modules/mesh-mail/cmd/mesh-mail/health_test.go, modules/mesh-mail/cmd/mesh-mail/imap_test.go, modules/mesh-mail/cmd/mesh-mail/internal/secret/secret.go, modules/mesh-mail/cmd/mesh-mail/kit_test.go, modules/mesh-mail/cmd/mesh-mail/manifest_test.go, modules/mesh-mail/cmd/mesh-mail/outcome_test.go, modules/mesh-mail/cmd/mesh-mail/sdk_pin_test.go, modules/mesh-mail/cmd/mesh-mail/secret_boundary_test.go, modules/mesh-mail/cmd/mesh-mail/send_test.go, modules/mesh-mail/cmd/mesh-mail/sender_integration_test.go, modules/mesh-mail/cmd/mesh-mail/sender_test.go, modules/mesh-mail/cmd/mesh-mail/smtp_classify_test.go, modules/mesh-mail/cmd/mesh-mail/tell_test.go

Run by the build seat on shanks as build-1792409514837747064 (builds --log build-1792409514837747064).

--- the gate: mesh-mail
note: mesh-mail uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-mail: ok, 10 tool(s), keeps state sends, ready: keep by unit every 30s; watch by its tool mail_health every 1m0s; send by unit every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-19T11:12:01Z says they run
composing every machine as the mesh is
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
composing every machine with the change
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
the bus's user list leaves out 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm. Each is a user that cannot connect until one is issued
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-19T11:12:01Z

modules the change moves:
  - mesh-mail (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes; the change adds 3 resource(s) and removes 0 (+file:mesh-mail.needs-broker-send, +process:mesh-mail.send, +user:mesh-mail.account)
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-mail

notes:
  - modules/mesh-mail/cmd/mesh-mail/acceptance_integration_test.go, modules/mesh-mail/cmd/mesh-mail/claim_test.go, modules/mesh-mail/cmd/mesh-mail/config_test.go, modules/mesh-mail/cmd/mesh-mail/health_test.go, modules/mesh-mail/cmd/mesh-mail/imap_test.go, modules/mesh-mail/cmd/mesh-mail/internal/secret/secret.go, modules/mesh-mail/cmd/mesh-mail/kit_test.go, modules/mesh-mail/cmd/mesh-mail/manifest_test.go, modules/mesh-mail/cmd/mesh-mail/outcome_test.go, modules/mesh-mail/cmd/mesh-mail/sdk_pin_test.go, modules/mesh-mail/cmd/mesh-mail/secret_boundary_test.go, modules/mesh-mail/cmd/mesh-mail/send_test.go, modules/mesh-mail/cmd/mesh-mail/sender_integration_test.go, modules/mesh-mail/cmd/mesh-mail/sender_test.go, modules/mesh-mail/cmd/mesh-mail/smtp_classify_test.go and modules/mesh-mail/cmd/mesh-mail/tell_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 54113 strings of 813 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.018s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/owned	0.008s
owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.273s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.016s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.232s
testing modules/mesh-mail
ok  	mesh-mail/cmd/mesh-mail	4.183s
?   	mesh-mail/cmd/mesh-mail/internal/secret	[no test files]
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `a2c0c586` Judged: head `a2c0c586772b` merged into trunk `c441d83ba753`; read beside it: mesh-controller `a5a43c8f31f0`, mesh-controller-main `a5a43c8f31f0`, mesh-host `2474bf28330f`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-mail) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-mail → novox; no bus step - tier 0: mesh-mail - novox: receives mesh-mail - read by no module's build: modules/mesh-mail/cmd/mesh-mail/acceptance_integration_test.go, modules/mesh-mail/cmd/mesh-mail/claim_test.go, modules/mesh-mail/cmd/mesh-mail/config_test.go, modules/mesh-mail/cmd/mesh-mail/health_test.go, modules/mesh-mail/cmd/mesh-mail/imap_test.go, modules/mesh-mail/cmd/mesh-mail/internal/secret/secret.go, modules/mesh-mail/cmd/mesh-mail/kit_test.go, modules/mesh-mail/cmd/mesh-mail/manifest_test.go, modules/mesh-mail/cmd/mesh-mail/outcome_test.go, modules/mesh-mail/cmd/mesh-mail/sdk_pin_test.go, modules/mesh-mail/cmd/mesh-mail/secret_boundary_test.go, modules/mesh-mail/cmd/mesh-mail/send_test.go, modules/mesh-mail/cmd/mesh-mail/sender_integration_test.go, modules/mesh-mail/cmd/mesh-mail/sender_test.go, modules/mesh-mail/cmd/mesh-mail/smtp_classify_test.go, modules/mesh-mail/cmd/mesh-mail/tell_test.go Run by the build seat on shanks as `build-1792409514837747064` (`builds --log build-1792409514837747064`). ``` --- the gate: mesh-mail note: mesh-mail uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here mesh-mail: ok, 10 tool(s), keeps state sends, ready: keep by unit every 30s; watch by its tool mail_health every 1m0s; send by unit every 30s long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-19T11:12:01Z says they run composing every machine as the mesh is HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus composing every machine with the change HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the bus's user list leaves out 6 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm. Each is a user that cannot connect until one is issued HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-19T11:12:01Z modules the change moves: - mesh-mail (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes; the change adds 3 resource(s) and removes 0 (+file:mesh-mail.needs-broker-send, +process:mesh-mail.send, +user:mesh-mail.account) - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-mail notes: - modules/mesh-mail/cmd/mesh-mail/acceptance_integration_test.go, modules/mesh-mail/cmd/mesh-mail/claim_test.go, modules/mesh-mail/cmd/mesh-mail/config_test.go, modules/mesh-mail/cmd/mesh-mail/health_test.go, modules/mesh-mail/cmd/mesh-mail/imap_test.go, modules/mesh-mail/cmd/mesh-mail/internal/secret/secret.go, modules/mesh-mail/cmd/mesh-mail/kit_test.go, modules/mesh-mail/cmd/mesh-mail/manifest_test.go, modules/mesh-mail/cmd/mesh-mail/outcome_test.go, modules/mesh-mail/cmd/mesh-mail/sdk_pin_test.go, modules/mesh-mail/cmd/mesh-mail/secret_boundary_test.go, modules/mesh-mail/cmd/mesh-mail/send_test.go, modules/mesh-mail/cmd/mesh-mail/sender_integration_test.go, modules/mesh-mail/cmd/mesh-mail/sender_test.go, modules/mesh-mail/cmd/mesh-mail/smtp_classify_test.go and modules/mesh-mail/cmd/mesh-mail/tell_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 54113 strings of 813 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.018s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/owned 0.008s owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.273s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.016s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.232s testing modules/mesh-mail ok mesh-mail/cmd/mesh-mail 4.183s ? mesh-mail/cmd/mesh-mail/internal/secret [no test files] --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools merged commit 7bb588ca1b into main 2026-10-19 11:36:51 +00:00
mesh-tools deleted branch feat/mail-sender 2026-10-19 11:36:52 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#371