@bobfrankston/rmfmail 1.2.297 → 1.2.298

package/.commitmsg

@@ -1,32 +1,33 @@
-Reading a message outranks syncing it; a filter is not a selection
+The signature in accounts.jsonc never reached compose
 
-Two things Bob hit on 2026-08-29.
+`sig` has been a documented field on AccountConfig for months and three of the
+four accounts carried one, yet no signature has ever appeared in a compose
+window. The reason is a projection: `MailxService.getAccounts()` builds the
+client's account list field by field — id/name/email from the DB row, then
+label, defaultSend, primary*, identityDomains from the config — and `sig` and
+`signature` were simply not on the list. `normalizeAccount()` resolved them
+correctly, `openCompose` forwarded `a.sig` faithfully, and compose.ts appended
+`acct.sig` exactly as designed; the value was undefined by the time any of that
+ran.
 
-**"If I look at a letter while sync, things get confused. Eventually it reports
-an error rather than retrying. Viewing the body should get priority instead of
-waiting for sync."** Both halves were real:
+Both fields are now carried, with a comment saying why the enumeration stays an
+enumeration rather than becoming `...cfg`: cfg holds the IMAP and SMTP
+passwords, which have no business crossing into the WebView. Anything new that
+the client needs has to be added in that spot deliberately.
 
-- Lanes are strictly sequential, and a click-time body fetch went on the tail
-  of the fast lane behind whatever background work was already queued.
-  `withConnection` now takes `priority`, which puts the task at the FRONT of
-  its lane; the interactive fetch uses it and a 30 s cap instead of 90 s. It
-  still cannot preempt the command in flight — an IMAP command cannot be
-  cancelled without dropping the connection — but it no longer waits out the
-  backlog.
-- `fetchMessageBody` swallowed every error into `null`. To the reconciler that
-  means "the server has no body for this message", which is classified
-  non-transient, skips the 3-attempt retry budget, and paints a banner. A lane
-  timeout says nothing about whether the message has a body: transient errors
-  (timeout, dropped socket, discarded client) now propagate, so the existing
-  retry-with-backoff applies and the reader gets the message instead of an
-  error. Only a genuine "no body here" still arms the prefetch backoff — a
-  timeout used to arm it too, poisoning the next view for up to 12 h.
+The signature itself moved to the top level of accounts.jsonc — three
+byte-identical per-account copies replaced by the one the file format already
+supports, which every account without its own `sig` inherits. It is now
+`Bob Frankston<br>https://Frankston.com` with `html: true`; the previous text
+relied on bare newlines for its line break (HTML collapses those to a space)
+and pointed at a relative `href='Frankston.com'`, which resolves against
+whatever page the mail client happens to be rendering.
 
-**"If I press * on search it shouldn't automatically select those letters, just
-show them."** Nothing was selected — the flagged-only filter washed the whole
-list in the flag colour (added 2026-06-26 to make the filter unmistakable), and
-a coloured background over rows is exactly how this list says "chosen". The
-wash is gone; the filter now announces itself above the list, by name:
-"Showing flagged (★) messages only — click to show everything", and clicking it
-clears the filter. Same chip covers the priority-senders filter, which had the
-same shape.
+Two stale comments corrected while here. `AccountSignature.html` was documented
+in both mailx-types and compose.ts as "reserved for future use / currently
+ignored". It has never been ignored — compose has always branched on it — and
+now that a signature actually renders, the difference between escaped text and
+raw HTML is the thing an author needs to know.
+
+Compose only. Nothing in the send path or the daemon appends a signature; the
+body that leaves the editor is the body that goes out.