SingleFile CLI 2.18.0

New features

--manifest writes a manifest of the capture next to the saved page, as <page filename>.manifest.json in canonical JSON (RFC 8785). It records the resources the page fetched with their final URL, status, headers and SHA-256 hash, the document and resource timings, the requests the browser made with their redirects, response body hashes, server addresses and TLS details when the engine exposes them, the certificates, the requests SingleFile made outside the browser, the capture options, the environment, the hash of the saved file, and a cross-check of the hashes computed by the page and by the network layer. The format is described in MANIFEST.md. Works with Chromium and Firefox, and is also part of the JSON of --output-json and --dump-json.

--browser-ignore-insecure-certs had no effect, the option was read under another name.
A resource fetched outside the browser now reports the URL it was finally served from, so a redirected stylesheet or image is recorded under its final URL.
Firefox captures no longer keep the process alive for 15 seconds after the page is saved.
Updated single-file-core to 1.6.27: grouped duplicate images are written in a stable order, and only a leading byte order mark is removed from text resources.

Co-authored by Claude (Claude Code)