Mail reading: mesh-mail-reader notes each new mail, tells mail that matters on Telegram, and the mail page shows and corrects it (design 59 milestone 2) #397

2026-10-20T23:56:12Z

mesh-tools commented

2026-10-20 23:56:12 +00:00

Design 59 milestone 2, one release of mesh-catalog (hq playbook 07). Decided by ADR 0459 (mail reading), ADR 0461 (mail signal), ADR 0472 (one grants list; supersedes ADR 0460).

mesh-mail's manifest declares the seat mail-reading (scope mesh; entries, groups, correct, lessons, undo, status).
New module mesh-mail-reader: runs as its own account; hears mesh-mail's added events (recorded before acknowledged, caught up in arrival order); its own postgres database of mail entries, mail groups and reading lessons, never a body; batches of at most 10 mails as one judgement within 55 KiB and 40 s, at least 160 s apart; health by its own tool (runtime-health), unhealthy on a refused, timed-out or misshapen judgement with cause and since; one tell per batch of mail that matters, words checked with messenger_check, the safe form when refused, untold mail carried past the cap; none for a scam warning or while unhealthy; the six verbs answer only callers in its own trusted setting callers (default mesh-mail-web). It invokes no send verb.
mesh-mail-web: the mail page shows mail that matters, mail groups and scam warnings above the classical list (the cause instead while mail reading is unhealthy; the list always renders), takes corrections and undoes reading lessons with token-bound forms, and shows reading lessons per 100 read mails per week.
Integration tests start mesh-mail-reader and mesh-mail-web whole against a real bus and store (issues 1431, 1524, 1517/AC4, 1523/AC4).

Issues: 1426, 1517, 1518, 1519, 1427, 1520, 1521, 1428, 1429, 1522, 1430, 1523, 1431, 1524. Try build-1792540396180144551 passed at f3007eb2 (mesh-mail 7.1 s, mesh-mail-reader 19.5 s, mesh-mail-web 8.4 s). Delivery: builds mesh-mail and mesh-mail-web to novox; registers mesh-mail-reader (assigned nowhere until the operator's Approve after delivery).

Reviewed-by: review-m2@g14 at f3007eb242

Design 59 milestone 2, one release of mesh-catalog (hq playbook 07). Decided by ADR 0459 (mail reading), ADR 0461 (mail signal), ADR 0472 (one grants list; supersedes ADR 0460). - mesh-mail's manifest declares the seat mail-reading (scope mesh; entries, groups, correct, lessons, undo, status). - New module mesh-mail-reader: runs as its own account; hears mesh-mail's added events (recorded before acknowledged, caught up in arrival order); its own postgres database of mail entries, mail groups and reading lessons, never a body; batches of at most 10 mails as one judgement within 55 KiB and 40 s, at least 160 s apart; health by its own tool (runtime-health), unhealthy on a refused, timed-out or misshapen judgement with cause and since; one tell per batch of mail that matters, words checked with messenger_check, the safe form when refused, untold mail carried past the cap; none for a scam warning or while unhealthy; the six verbs answer only callers in its own trusted setting callers (default mesh-mail-web). It invokes no send verb. - mesh-mail-web: the mail page shows mail that matters, mail groups and scam warnings above the classical list (the cause instead while mail reading is unhealthy; the list always renders), takes corrections and undoes reading lessons with token-bound forms, and shows reading lessons per 100 read mails per week. - Integration tests start mesh-mail-reader and mesh-mail-web whole against a real bus and store (issues 1431, 1524, 1517/AC4, 1523/AC4). Issues: 1426, 1517, 1518, 1519, 1427, 1520, 1521, 1428, 1429, 1522, 1430, 1523, 1431, 1524. Try build-1792540396180144551 passed at f3007eb2 (mesh-mail 7.1 s, mesh-mail-reader 19.5 s, mesh-mail-web 8.4 s). Delivery: builds mesh-mail and mesh-mail-web to novox; registers mesh-mail-reader (assigned nowhere until the operator's Approve after delivery). Reviewed-by: review-m2@g14 at f3007eb242f8bd17ad2ca428610d661e38618a80

mesh-tools added 22 commits 2026-10-20 23:56:12 +00:00

Declare the seat mail-reading and the module mesh-mail-reader's skeleton (issue 1426) d17b7e832d

Keep a mail entry per mail, never the body (issue 1517) 0d2d19daa0

Hear mesh-mail's added events, recorded before acknowledged, in arrival order (issue 1518) d7b5c87887

Keep mesh-mail-reader's own health, surviving a restart (issue 1519) 183cc58347

Build the batch's question and read its answer, bounded and out of shape when wrong (issue 1427) 83bc01e746

Run the reader's batches: paced, judged, written as entries, unhealthy on failure (issue 1520) 42bffb9363

Serve entries, groups and status: filtered, sorted, with the weekly reading-lessons measure (issue 1521) a13a6c5898

Keep the operator's corrections as reading lessons at once: correct, lessons, undo (issue 1428) e87269b0d2

Build the mail signal's own words: headline, nearest due date first (issue 1429) 72f4bc52a4

Send the mail signal after each batch: messenger_check, tell, untold carried over (issue 1522) 35496d6381

Show mail that matters, mail groups and scam warnings above the classical list (issue 1430) 8ff94287a7

Correct a mail's mark or group and undo a lesson from the page, with the weekly measure (issue 1523) 0bc59c6f4a

Start mesh-mail-reader whole against the real bus and store: entries, no body kept, the tell, the cap (issue 1431) 95704c7410

Prove a refused judgement fails loudly and catches up, and the page shows why (issue 1524) 3d030c9b4f

Merge remote-tracking branch 'origin/main' into feat/mail-reading d61fe4e2da

Fix the try: guard shared test state with mutexes, pgxpool over one conn, a short batch gap for integration builds, unique+forced database drops (issues 1431, 1524, 1517) 794de09c4d

Merge remote-tracking branch 'origin/main' into feat/mail-reading bb594652fa

Fix the try on bb594652: a const batch gap unit tests assert directly, wait for the bundle's own subscribe before publishing, and a migration-0001 database built through the real path (issues 1520, 1518, 1431, 1517) cfea9de530

Merge remote-tracking branch 'origin/main' into feat/mail-reading 63980bf5ac

Fix the try on 63980bf5: keep a test database's name within postgres's 63-byte limit so two calls in one long-named test never collide (issue 1517) f89b73d936

Review round 1: an unset mail-reading verb answers unavailable not unknown, cache the index instead of leaking a pool per call, a gone mail leaves the queue without going unhealthy, sort the judge's own cause by its words, drive RunBatches itself for its pacing test, and prove no tell while unhealthy against a genuinely untold mail (issues 1430, 1523, 1517, 1518, 1520, 1519, 1524) 8000b63785

Fix the try on 8000b637 and review round 2: RunBatches takes its gap as a parameter instead of reading the var BatchGap, and no tell while unhealthy is checked as an exact count, not a before/after that a same-pass tell could hide behind (issue 1520, 1524)

mesh/merge-gate head f3007eb242f8 merged into trunk 6c6d5f681c30 — pass: builds mesh-mail, mesh-mail-web, new: modules/mesh-mail-reader → novox; no bus ste…

Details

mesh/repo-check head f3007eb242f8 merged into trunk 6c6d5f681c30 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…

Details

mesh/delivery delivered

Details

f3007eb242

mesh-tools commented

2026-10-20 23:56:23 +00:00

Delivery novox/mesh-catalog@f3007eb242f8 — delivered since 2026-10-21T00:08:09Z

Delivery plan — builds mesh-mail, mesh-mail-web, new: modules/mesh-mail-reader → novox; no bus step

tier 0: mesh-mail, mesh-mail-web
novox: receives mesh-mail, mesh-mail-web

Machines

mesh-mail on every machine running it: sent
mesh-mail-web on every machine running it: sent

Transitions

2026-10-20 23:56 (new) → proposed (announced): novox/mesh-catalog#397's head announced
2026-10-21 00:01 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-21 00:01 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-21 00:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-21 00:06 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-21 00:08 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.

**Delivery** `novox/mesh-catalog@f3007eb242f8` — **delivered** since 2026-10-21T00:08:09Z **Delivery plan** — builds mesh-mail, mesh-mail-web, new: modules/mesh-mail-reader → novox; no bus step - tier 0: mesh-mail, mesh-mail-web - novox: receives mesh-mail, mesh-mail-web **Machines** - mesh-mail on every machine running it: sent - mesh-mail-web on every machine running it: sent **Transitions** - 2026-10-20 23:56 (new) → proposed (announced): novox/mesh-catalog#397's head announced - 2026-10-21 00:01 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 00:01 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 00:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 00:06 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-21 00:08 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-21 00:01:11 +00:00

Merge check at f3007eb2
Judged: head f3007eb242f8 merged into trunk 6c6d5f681c30; read beside it: mesh-controller 0fee5404d95b, mesh-controller-main 0fee5404d95b, mesh-host c5c4caa2a4ab, mesh-tools e0fadc43d9dd

mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-mail, mesh-mail-web, new:modules/mesh-mail-reader)
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, mesh-mail-web, new: modules/mesh-mail-reader → novox; no bus step

tier 0: mesh-mail, mesh-mail-web
novox: receives mesh-mail, mesh-mail-web
read by no module's build: modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/manifest_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/runtime_integration_test.go, modules/mesh-mail/cmd/mesh-mail/manifest_test.go

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

--- the gate: mesh-mail, mesh-mail-web, new:modules/mesh-mail-reader
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, 11 tool(s), keeps state sends, accounts, mails, ready: keep by unit every 30s; watch by its tool mail_health every 1m0s; send by unit every 30s
mesh-mail-reader: ok, 7 tool(s), invokes seat:mail-store.read, seat:mail-store.accounts, claude-code.claude_code_judge, claude-code.claude_code_judged, messenger.messenger_check, seat:operator-channel.tell, ready: mesh-mail-reader.own-runtime by its tool mail_reader_health every 1m0s
mesh-mail-web: ok, 3 tool(s), invokes seat:mail-store.accounts, seat:mail-store.search, seat:mail-store.read, seat:mail-store.send, seat:mail-store.send-status, seat:mail-reading.entries, seat:mail-reading.groups, seat:mail-reading.status, seat:mail-reading.correct, seat:mail-reading.lessons, seat:mail-reading.undo, reads mesh-mail.accounts
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
3 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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-20T23:48:13Z 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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
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-20T23:48:13Z

modules the change moves:
  - mesh-mail (changed)
  - mesh-mail-reader (added)
  - mesh-mail-web (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
  - a machine (yvbpsm): composes

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

notes:
  - mesh-mail-reader could not be tried on a machine: mesh-mail-reader on f35 has no bus credential: nothing was issued for f35.mesh-mail-reader, and a push would seal a placeholder its process cannot read (novox/hq issue 203). `module issue mesh-mail-reader --node f35`, then push again
  - modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/manifest_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/runtime_integration_test.go and modules/mesh-mail/cmd/mesh-mail/manifest_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 57791 strings of 893 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.015s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.010s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.022s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/owned	0.009s
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.015s
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.274s
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.015s
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.234s
testing modules/mesh-mail
ok  	mesh-mail/cmd/mesh-mail	8.514s
?   	mesh-mail/cmd/mesh-mail/internal/secret	[no test files]
testing modules/mesh-mail-reader
ok  	mesh-mail-reader/cmd/mesh-mail-reader	21.141s
testing modules/mesh-mail-web
ok  	mesh-mail-web/cmd/mesh-mail-web	9.892s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `f3007eb2` Judged: head `f3007eb242f8` merged into trunk `6c6d5f681c30`; read beside it: mesh-controller `0fee5404d95b`, mesh-controller-main `0fee5404d95b`, mesh-host `c5c4caa2a4ab`, mesh-tools `e0fadc43d9dd` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-mail, mesh-mail-web, new:modules/mesh-mail-reader) - `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, mesh-mail-web, new: modules/mesh-mail-reader → novox; no bus step - tier 0: mesh-mail, mesh-mail-web - novox: receives mesh-mail, mesh-mail-web - read by no module's build: modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/manifest_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/runtime_integration_test.go, modules/mesh-mail/cmd/mesh-mail/manifest_test.go Run by the build seat on shanks as `build-1792540576395438577` (`builds --log build-1792540576395438577`). ``` --- the gate: mesh-mail, mesh-mail-web, new:modules/mesh-mail-reader 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, 11 tool(s), keeps state sends, accounts, mails, ready: keep by unit every 30s; watch by its tool mail_health every 1m0s; send by unit every 30s mesh-mail-reader: ok, 7 tool(s), invokes seat:mail-store.read, seat:mail-store.accounts, claude-code.claude_code_judge, claude-code.claude_code_judged, messenger.messenger_check, seat:operator-channel.tell, ready: mesh-mail-reader.own-runtime by its tool mail_reader_health every 1m0s mesh-mail-web: ok, 3 tool(s), invokes seat:mail-store.accounts, seat:mail-store.search, seat:mail-store.read, seat:mail-store.send, seat:mail-store.send-status, seat:mail-reading.entries, seat:mail-reading.groups, seat:mail-reading.status, seat:mail-reading.correct, seat:mail-reading.lessons, seat:mail-reading.undo, reads mesh-mail.accounts long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 3 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 3 module(s) changed against 4 machine(s), as the snapshot of 2026-10-20T23:48:13Z 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 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-20T23:48:13Z modules the change moves: - mesh-mail (changed) - mesh-mail-reader (added) - mesh-mail-web (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 - a machine (yvbpsm): composes a merge would rebuild 2 module(s) in 1 tier(s): mesh-mail, mesh-mail-web notes: - mesh-mail-reader could not be tried on a machine: mesh-mail-reader on f35 has no bus credential: nothing was issued for f35.mesh-mail-reader, and a push would seal a placeholder its process cannot read (novox/hq issue 203). `module issue mesh-mail-reader --node f35`, then push again - modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailreading_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_integration_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/mailwrite_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/manifest_test.go, modules/mesh-mail-web/cmd/mesh-mail-web/runtime_integration_test.go and modules/mesh-mail/cmd/mesh-mail/manifest_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 57791 strings of 893 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.015s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.010s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.022s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/owned 0.009s 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.015s 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.274s 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.015s 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.234s testing modules/mesh-mail ok mesh-mail/cmd/mesh-mail 8.514s ? mesh-mail/cmd/mesh-mail/internal/secret [no test files] testing modules/mesh-mail-reader ok mesh-mail-reader/cmd/mesh-mail-reader 21.141s testing modules/mesh-mail-web ok mesh-mail-web/cmd/mesh-mail-web 9.892s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-tools merged commit f99f11e8a4 into main

2026-10-21 00:06:24 +00:00

mesh-tools deleted branch feat/mail-reading

2026-10-21 00:06:24 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#397