@bobfrankston/rmfmail 1.2.278 → 1.2.280

package/client/app.ts

@@ -5417,9 +5417,37 @@ async function openAboutDialog(): Promise<void> {
     backdrop.addEventListener("mousedown", (e) => { if (e.target === backdrop) close(); });
 
     try {
-        const [v, accounts] = await Promise.all([
+        // The bundled editor's own version, read from the tree the editor
+        // actually loads from — so it cannot drift from what is running. Both
+        // specs are caret ranges and the resolved version moves whenever npm
+        // re-resolves: tinymce sat at 8.6.0 for weeks under ^8.5.0 with nothing
+        // to notice (Bob 2026-08-23, "do you track updates for TinyMCE?").
+        // build-tinymce.js also prints it, but npmglobalize swallows a
+        // sub-build's stdout — only "Build succeeded" reaches the archived
+        // transcript — so the build log is NOT where this question gets
+        // answered. Here it is answerable on the machine showing the symptom.
+        // (Claude Code 2026-08-24)
+        const editorBundle = async (): Promise<string> => {
+            const readJson = async <T>(url: string): Promise<T> => {
+                try {
+                    const r = await fetch(url);
+                    return r.ok ? await r.json() : null;
+                } catch {
+                    return null;
+                }
+            };
+            const [pkg, langs] = await Promise.all([
+                readJson<{ version: string }>("lib/tinymce/package.json"),
+                readJson<string[]>("lib/tinymce/langs/index.json"),
+            ]);
+            if (!pkg?.version) return "";
+            const n = langs?.length || 0;
+            return n ? `TinyMCE ${pkg.version} · ${n} languages` : `TinyMCE ${pkg.version}`;
+        };
+        const [v, accounts, editorInfo] = await Promise.all([
             getVersion().catch(() => ({} as any)),
             getAccounts().catch(() => [] as any[]),
+            editorBundle(),
         ]);
         const storage = v.storage || {};
         const isApp = typeof mailxapi !== "undefined" && mailxapi?.isApp;
@@ -5440,6 +5468,7 @@ async function openAboutDialog(): Promise<void> {
         if (storage.folderId) rows.push(["Drive folderId", storage.folderId]);
         if (storage.folderOwner) rows.push(["Drive owner", storage.folderOwner]);
         if (storage.configDir) rows.push(["Config dir", storage.configDir]);
+        if (editorInfo) rows.push(["Editor bundle", editorInfo]);
         rows.push(["Accounts", String((accounts || []).length)]);
         rows.push(["User agent", navigator.userAgent]);
         rows.push(["Screen", `${screen.width}×${screen.height}`]);

package/npmchanges.md

@@ -564,3 +564,54 @@ Harper (English only) are untouched, and Quill/tiptap have no localized chrome.
 tests/tinymce-langs.test.ts pins the resolution against the real manifest.
 Needs rmf-tiny 0.1.52 for the adapter's `language` option.
 
+## v1.2.278 — 2026-08-25
+
+TinyMCE 8.6.0 → 8.8.2
+
+Routine maintenance releases — no security advisories, no breaking changes
+(all within major 8). Four of the fixes land on paths mailx actually uses:
+
+- The menubar could wrap onto multiple rows on narrow viewports or at high
+  browser zoom, leaving little or no visible editable area (8.8.1). Same class
+  of failure as the v1.2.264 "body must fill the iframe" bug, and compose is
+  routinely used zoomed.
+- CSS custom property names and colour values in a style attribute were
+  lowercased when parsed (8.7.0) — that is quoted mail passing through a
+  reply/forward.
+- Copying or dragging in an image didn't set width/height on the tag (8.7.0),
+  which the inline-image → cid path then had to carry.
+- The link plugin threw a querySelectorAll syntax error on anchors containing
+  semicolons (8.8.0). Mail bodies are full of odd links.
+
+Also: undo not restoring the selection, deleting a newline in a list item
+eating the item, and the emoticons dialog's 300-item cap (we load that plugin).
+
+Verified before publishing: all 17 plugins we request still exist in 8.8.2, the
+dom model is unchanged, and the package still ships no langs/ directory — the
+61 packs added in 1.2.277 come from tinymce-i18n and are copied after the tree,
+so the re-copy keeps them (62 files present, manifest included).
+
+The spec moves from ^8.5.0 to ^8.8.2. The old floor already permitted 8.8.2;
+the tree had simply drifted at 8.6.0 with nothing to notice it, which is what
+prompted this. Raising the floor makes the intent explicit rather than leaving
+a fresh install free to resolve lower.
+
+## v1.2.279 — 2026-08-25
+
+build-tinymce: report which TinyMCE and language-pack versions were copied
+
+Both specs are caret ranges, so the resolved version moves on its own whenever
+npm re-resolves the tree — tinymce sat at 8.6.0 for weeks under a ^8.5.0 spec
+with nothing to notice ("do you track updates for TinyMCE?", Bob 2026-08-23).
+
+Pinning exact would only trade silent drift for silent staleness: no more patch
+fixes, and the surprise moves to whoever edits the pin. A dependency bot is the
+wrong shape too — those work by filing PRs, and this repo publishes from the
+local tree with direct commits.
+
+So make it visible where it already costs nothing. Every publish archives its
+build transcript to c:\temp\rebuild\, and build-tinymce.js already prints what
+it copied; it now prints the resolved versions of tinymce and tinymce-i18n as
+well. "Which TinyMCE shipped in 1.2.277?" is answerable from the log, with no
+network call at build time and nothing to maintain.
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/rmfmail",
-  "version": "1.2.278",
+  "version": "1.2.280",
   "description": "Local-first email client with IMAP sync and standalone native app",
   "type": "module",
   "main": "bin/mailx.js",