* Render mail print metadata as text and isolate print documents
* Update application dependencies for published security advisories
* Require patched Dovecot and Pigeonhole in mail images
`npm i -g openship` is the only install path that runs on the user's own Node
— scripts/install.sh resolves its own (system >= 22, else it vendors one).
With no engines floor, npm installed onto Node 18 with a warning that named
`commander`, exited 0, linked the bin, and then the command died with
"SyntaxError: Invalid regular expression flags" out of string-width's /v flag.
That reads as a broken install rather than a wrong Node, and it cost at least
one operator an afternoon.
node-entry.ts now checks the Node major before loading the CLI and, rather
than only refusing, reuses ensureNodeRuntime() — the same function `openship
update` calls — to run on a Node that satisfies the floor: reuse a vendored
Node 22 silently, else offer to fetch one (~50 MB, checksum-verified, into
~/.openship/runtime, system Node untouched). Hard stop below 20, warn on
20–21. OPENSHIP_VENDOR_NODE=1|0 accepts/declines without prompting for CI;
a non-TTY never blocks on stdin; OPENSHIP_NODE_REEXEC guards the re-exec loop.
Two ordering details are load-bearing. The CLI is loaded with a DYNAMIC
import: ESM evaluates a module's imports before its own body, so a static one
lets the SyntaxError win and the gate never prints. Recovery is its own bundle
imported in a try/catch for the same reason — inlining it would put its whole
import chain inside the gate, so one modern-syntax dependency anywhere in it
would break the gate with the very error it replaces.
Also drops the accidental `"openship": "^0.5.0"` self-dependency (shipped in
0.6.0 and 0.6.1), which unpacked a second, older CLI plus its dep tree into
every install.