Badge the installed icon, and share to the phone rather than to Downloads

Three things an installed ihasmail did not do that a phone user expects,
and all three are about the app once it is off the browser tab.

The unread count was painted into the tab title and the favicon, neither
of which exists in `display: standalone` -- so putting ihasmail on a home
screen threw the count away entirely. It goes to the Badging API as well
now. Web Push marks the icon while the app is closed, and marks it with a
dot rather than a figure: the service worker has no session to ask how
many messages are unread, and a push carries the new mail rather than a
total, so counting the payload would badge "2" over an inbox holding
forty. The next tab to open writes the real count over it.

Sharing is new. Everything that left ihasmail left as a download, which
on a phone is close to a dead end -- the file lands in Downloads and
whoever meant to send it somewhere goes looking for it in a file manager.
The share sheet is now on the message menu, on each attachment row, and
in the file viewer, which is where an attachment is already open and
where both callers meet. A message shares as text rather than as the
.eml beside it: a share sheet is aimed at everything that is not a mail
client, and an .eml in a chat app is an attachment nobody can open.

Every control feature-detects, and sharing a file is a separate question
from sharing at all -- desktop Linux and Firefox have neither, and not
every browser with `share` takes files. Anything that fails, including
the transient activation running out while a large attachment is fetched,
falls through to the download the button sits beside, so the worst case
costs a tap rather than the file. `NotAllowedError` is reported as
unsupported for that reason: it cannot be told apart from a refusal, and
a toast about activation is not something a reader can act on.

The share strings are contextual keys rather than the existing "Share…".
That one means granting another account access, and several languages use
a different verb for it -- German had "Freigeben" where the sheet wants
"Teilen". Three new strings, in all nine catalogues.

The manifest gains `launch_handler: navigate-existing`, so a mailto:, a
shortcut or a notification tapped while ihasmail is running arrives in
the copy that is running: two windows on one inbox disagree about what
has been read. `focus-existing` would have been wrong -- it only focuses
and leaves the target URL to launchQueue, which nothing here consumes, so
it would swallow the mailto. There is deliberately still no `id`, and the
manifest now says why: it is the one member resolved against the origin
of start_url rather than against the manifest's own address, so no
relative form can name a subpath mount, and the default id already is
start_url -- writing one now would give every installed copy a new
identity and orphan it as a second app.

Verified by test rather than on a device: the extension driving Chrome
was not connected, and Chrome on Linux has no Web Share to drive anyway.
The preview dialog is covered by a component test that stubs the browser
both ways.

web/src/ui/filepreview.tsx

@@ -1,10 +1,11 @@
 import { useCallback, useEffect, useMemo, useRef, useState, type ReactNode } from "react";
-import { Code2, Download, Eye, Pencil, Printer, Save, X } from "lucide-react";
+import { Code2, Download, Eye, Pencil, Printer, Save, Share2, X } from "lucide-react";
 import { confirmDialog, Dialog } from "./dialog";
 import { formatSize } from "@/lib/format";
 import { previewKind, TEXT_PREVIEW_CHARS, TEXT_PREVIEW_MAX } from "@/lib/preview";
 import { isMarkdown, renderMarkdown } from "@/lib/markdown";
-import { t } from "@/lib/i18n";
+import { canShareFiles, shareFile } from "@/lib/share";
+import { t, tc } from "@/lib/i18n";
 
 /**
  * One blob, described the way both callers can describe it. The URLs are built
@@ -144,6 +145,43 @@ export function FilePreviewDialog({
     void confirmDialog({ title: t("Close without saving?"), confirmLabel: t("Discard"), danger: true }).then((yes) => yes && onClose());
   };
 
+  /*
+   * Hand the file to another app rather than to the filesystem.
+   *
+   * This is the surface where it matters most on a phone: opening an
+   * attachment lands here, and until now the only way onward was Download,
+   * which on Android and iOS means "put it somewhere and go and find it".
+   *
+   * The bytes have to be fetched rather than the URL passed along, because the
+   * share sheet takes a File. `same-origin` credentials because both URLs are
+   * ihasmail's own blob proxy and it is the session cookie that authorises the
+   * read -- which is also why this does not break the rule about `ui/` not
+   * reaching for the JMAP client: it is a plain fetch of a URL the caller
+   * already handed over.
+   *
+   * Anything that goes wrong, including a share the browser turned out not to
+   * support, falls through to the download. That is the button that was here
+   * before, so the worst case costs a tap rather than the file.
+   */
+  const shareIt = useCallback(async () => {
+    if (!file) return;
+    const download = () => {
+      const l = document.createElement("a");
+      l.href = file.url;
+      l.download = file.name;
+      l.click();
+    };
+    try {
+      const res = await fetch(file.url, { credentials: "same-origin" });
+      if (!res.ok) throw new Error(String(res.status));
+      const blob = await res.blob();
+      const out = await shareFile(new File([blob], file.name, { type: file.type || blob.type || "application/octet-stream" }));
+      if (out === "unsupported") download();
+    } catch {
+      download();
+    }
+  }, [file]);
+
   /*
    * Print what is on screen, not the mail or the file list behind it.
    *
@@ -209,6 +247,7 @@ export function FilePreviewDialog({
                   </div>
                 )}
                 {editable && <button className="btn" onClick={startEditing}><Pencil size={16} />  {t("Edit")}</button>}
+                {canShareFiles() && <button className="btn" onClick={() => void shareIt()}><Share2 size={16} />  {tc("share sheet", "Share")}</button>}
                 {kind && !tooBig && <button className="btn" onClick={print}><Printer size={16} />  {t("Print")}</button>}
                 <a className="btn" href={file.url} download={file.name}><Download size={16} />  {t("Download")}</a>
               </>