5 Commits

Include renames

Author	SHA1	Message	Date
jochen	c2cd2e1eb1	issue 800: fix review round 3 finding, a true sliding window instead of a session quota ... A session that only reset after a quiet minute kept counting, and so folding, a steady trickle of mail forever even with no burst (one mail every 50s). N is now the account's qualifying mail arrived in the trailing 60 seconds, counted fresh on every arrival; a fold holds only its own overflow and the notice names just that count, not the whole history.	2026-10-15 19:03:05 +02:00
jochen	66713c5a1e	issue 800: fix review round 2 findings in mesh-mail-notifier ... A buffer was replaced, discarding whatever it still held unsent, once Window had passed since its first mail — losing a failed send waiting for its retry, or a folded mail waiting for its minute's end, if a new mail arrived meanwhile. The window now slides on the gap since the last mail, not on time elapsed since the first: a session's count never resets, and its buffer is never replaced, while anything in it is still unsent. The fold notice now counts every mail of the account in that minute, not only the overflow, and says "mail" for one and "mails" for more.	2026-10-15 18:50:21 +02:00
jochen	b771794f1c	issue 800: keep notify's health as unit; the gate refuses a one-process module judged only by its own tool ... ADR 0227 rule 8 / ADR 0240 rule 2 refuse a module with no health check of another kind beside a tool check. mesh-mail-notifier has one process (notify); wiring mail_notifier_health as its manifest health, as the review note's wording suggested (mirroring mesh-mail's watch/mail_health), trips that rule because mesh-mail also has keep (kind unit) beside watch. mail_notifier_health stays built, tested and callable; notify's manifest health stays kind unit until the lead decides how a one-process module gets this automatically.	2026-10-15 18:33:22 +02:00
jochen	ed66a2e873	issue 800: fix review round 1 findings in mesh-mail-notifier ... Flush now sorts accounts instead of walking a map, so notice order is stable. A failed node-notifier.send keeps its mail pending and retries at most once a minute, without holding up other accounts' notices, and the failure is kept in the Store for a new health tool (mail_notifier_health) that is unhealthy past ten minutes of failure. The burst rule now follows the lead's reading of ADR 0378 S9: within an account's sliding minute, the first three qualifying mails are shown one by one and the rest are folded into one notice at the window's end; there is no separate quiet-gap timer. The dedupe key is the account and message id, falling back to folder/uidvalidity/uid only when no message id is given, so a UIDVALIDITY reset cannot suppress a new mail, and a redelivered event already buffered is never recounted. status now lists every granted account, not only those with a notice, and caches mail-store.accounts for a minute.	2026-10-15 17:54:27 +02:00
jochen	dc89995d96	Add mesh-mail-notifier, the default holder of mail-notifier (issue 800 part B) ... ADR 0378 §9 as amended by ADR 0379: a module of its own, built from mesh-mail's event shape, runs as its own account to hear mesh-mail's restricted MAIL stream (ADR 0376 §2), shows each new inbox mail through node-notifier.send at most once, folds more than three from one account into one notice, and emits its own shown event.	2026-10-15 17:33:15 +02:00