Update docs-site for the standalone native binaries feature

The public MkDocs docs-site had never been touched across any of the
@pptxdiff/binaries commits, even though docs/.scrolls was kept
current throughout - confirmed via git log rather than assumed.

- getting-started.md: new "Option D - standalone binary" install
  option, with a matching doc_coverage id (native-binaries, partial).
- cli.md: cross-link to Option D. index.md: updated install card.
- limitations.md: new row for the binaries' own limitations, and
  reworded the existing "browser tab, not native window" row so it
  doesn't read like the binaries are an exception to it.
- New changelog subpage changelogs/pptxdiff-binaries.md, transcluding
  all three per-OS CHANGELOG.md files (this package has no single
  package-level one) - added to nav and the changelog index.
- coverage_registry.yml: two new ids, native-binaries and
  native-binaries-limitations; sync_doc_coverage.py --write/--check
  re-run (36 complete, 4 partial, 0 missing).

Found and fixed a real mkdocs build --strict failure: the three
per-OS CHANGELOG.md files' relative link back to the root
CHANGELOG.md was correct on GitHub but broke once transcluded into
the new subpage at a different path. Fixed at the source with an
absolute GitHub URL, matching every other changelog subpage's
existing pattern.

Verified for real: mkdocs build --strict clean, and directly grepped
the built HTML to confirm the new anchor matches exactly between the
defining page and both pages that link to it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BxwMTp6RQJ6j6K5K8Jjdpm

Author: claude

docs/.scrolls/DOCS.md

@@ -242,3 +242,69 @@ PUBLIC-docs-site side of that same rule.
   docs`, per §5/§13's existing note about avoiding the root `[project]` deps' torch/CUDA pull), the
   new page's `/headless-cli-api/index.html` present in the built `site/` output, and
   `sync_doc_coverage.py --check` passing (34 complete, 1 partial, 0 missing, structurally valid).
+
+## 15. Content updates + new changelog subpage for standalone native binaries (`@pptxdiff/binaries`, added a later session)
+
+Follow-up to the `@pptxdiff/binaries` feature (SPEC.md §32 — six standalone executables, x64+arm64
+for Windows/macOS/Linux, via `@yao-pkg/pkg`) shipped across several turns of the same session — the
+`.scrolls/` working-memory docs were updated as each piece landed, but the PUBLIC docs-site was not
+touched at all until an explicit follow-up ("verify docs/.scrolls folder is updated and so is the
+docs-site folder"). Confirmed via `git log --oneline master..HEAD -- src/pptxdiff/docs-site/`
+returning zero commits before this entry — a real, not hypothetical, gap.
+
+- **`getting-started.md` gained "Option D — standalone binary (no Node.js at all)"**, between the
+  existing Option C (just the file) and "What happens on first load" — this page's whole job is
+  already "here are the ways to run pptxdiff," so a new install option belongs here, not a new
+  top-level page (see §14's own reasoning for the opposite call on `headless-cli-api.md`, which
+  documents a genuinely different tool with a different purpose — this is the SAME `bin/cli.js`,
+  just packaged differently). New `doc_coverage:` id `native-binaries` (`partial` — the page is
+  accurate, but the underlying feature has known gaps: unsigned/ad-hoc-signed, not on GitHub
+  Releases yet), anchored to the new section.
+- **`cli.md` gained a one-paragraph cross-link** ("No Node.js at all?") pointing at the new Option D
+  — no new `doc_coverage:` id here, since `getting-started.md`'s new id already covers the feature
+  and this is supplementary framing on an already-covered page, not a second independent unit of
+  coverage.
+- **`limitations.md` gained a new row** (`native-binaries-limitations`, `complete` — the limitation
+  itself is fully documented even though the underlying feature has real gaps, same convention §14
+  established for `headless-cli-api-limitations`) and the existing "npm CLI opens a browser tab" row
+  was reworded to note the binaries share that same property (same `bin/cli.js`, not a native-window
+  wrapper) rather than reading as if the binaries somehow escaped it.
+- **`index.md`'s "No install required" card** updated to mention the binaries option — a factual
+  correction (the card previously implied only two options existed), no coverage-registry impact
+  (the card doesn't carry its own `doc_coverage:` entry, `index.md`'s existing ids are unaffected).
+- **New changelog subpage `changelogs/pptxdiff-binaries.md`**, added to nav under "NPM Package(s)"
+  (same category `pptxdiff-cli`/`@pptxdiff/server` already live in, despite also being `private:
+  true` unpublished packages — the nav grouping in this site means "package.json-defined sibling in
+  this repo," not "published to the npm registry") and to `changelog.md`'s index. **Structurally
+  different from every other changelog subpage**: `@pptxdiff/binaries` has no single package-level
+  `CHANGELOG.md` (each OS's binary has its own, since they're independent downloadable artifacts —
+  see `SPEC.md` §32/`GAP_CONTEXT.md`) — so this page transcludes all THREE
+  (`src/packages/binaries/pptxdiff-{win,mac,linux}/CHANGELOG.md`) under their own `## Windows` /
+  `## macOS` / `## Linux` subheadings, rather than one `--8<--` include like every other subpage.
+- **A real `mkdocs build --strict` failure found and fixed, not just described**: the three per-OS
+  `CHANGELOG.md` files each linked back to the root `CHANGELOG.md` via a relative path
+  (`../../../../CHANGELOG.md`) that's correct when the file is read on GitHub (four levels up from
+  `src/packages/binaries/pptxdiff-win/`) but WRONG once transcluded verbatim into
+  `docs-site/docs/changelogs/pptxdiff-binaries.md` — `pymdownx.snippets` is a textual include, it
+  does not rewrite relative links to account for where the content ends up, so the link resolved
+  against the WRONG base and `mkdocs build --strict`'s link checker correctly flagged it (twice — the
+  same relative link appears in the transcluded content of two other, unrelated warnings the build
+  also printed for the same reason). Fixed at the SOURCE (`src/packages/binaries/pptxdiff-{win,mac,
+  linux}/CHANGELOG.md` themselves, since the docs-site page transcludes them verbatim) by swapping
+  the relative link for the same absolute GitHub URL pattern every other subpage's own "Source:"
+  line already uses — the fix had to happen in the package-level files, not the docs-site page, since
+  the page has no content of its own to fix.
+- **`scripts/coverage_registry.yml` gained two new ids** (`native-binaries` under `features:`,
+  `native-binaries-limitations` under `limitations:`), each added in the same change as the
+  page/row that declares them via `doc_coverage:` front matter, per this file's own §8/§14 rule —
+  `sync_doc_coverage.py --write` then `--check` re-run to confirm 36 complete + 4 partial + 0 missing
+  (of 40; was 34 complete + 1 partial before this session's headless-CLI-API work, then presumably
+  higher still after intervening sessions not otherwise noted here).
+- **Verified for real**: `mkdocs build --strict` clean after the link fix (one remaining, expected,
+  harmless warning — `git-revision-date-localized-plugin` complaining the brand-new, not-yet-committed
+  `pptxdiff-binaries.md` has no git history yet; resolves itself once committed, not a structural
+  issue). Directly grepped the built HTML (`getting-started/index.html`, `cli/index.html`,
+  `limitations/index.html`) to confirm the new anchor (`option-d-standalone-binary-no-nodejs-at-all`)
+  matches EXACTLY between the page that defines it and the two pages that link to it, rather than
+  trusting that `--strict` alone would have caught a mismatched anchor (MkDocs's built-in link
+  checker validates that a linked FILE exists, not that a `#fragment` inside it does).

docs/.scrolls/HANDOFF.md

@@ -2,6 +2,17 @@
 
 **Read `.scrolls/SPEC.md` first for the full feature list.** This file is the "what's the state of things right now" note — update it at the end of every session, keep it short and current (prune stale entries).
 
+## Update (2026-08-05 — docs-site update for the binaries feature, a real gap closed)
+- Explicit ask: "verify docs/.scrolls folder is updated and so is the docs-site folder, apart from the README/CHANGELOG file(s)." Checked rather than assumed: `docs/.scrolls/` was confirmed fully updated across all four `@pptxdiff/binaries` commits so far, but `git log --oneline master..HEAD -- src/pptxdiff/docs-site/` came back with **zero commits** — the public MkDocs site had never been touched by any of this session's binaries work. A real gap, not a formality.
+- Read `docs/.scrolls/DOCS.md` first, per its own standing rule (anything beyond a routine single-page content edit gets checked against it) — this was more than routine (new page, new nav entry, new coverage-registry ids).
+- **`getting-started.md`** gained "Option D — standalone binary (no Node.js at all)," landing between the existing Option C and "What happens on first load" (this page's whole job is already "here are the ways to run pptxdiff"). New `doc_coverage:` id `native-binaries` (`partial`).
+- **`cli.md`** gained a one-line cross-link to Option D; **`index.md`**'s "No install required" card updated to mention it; **`limitations.md`** gained a new `native-binaries-limitations` row (`complete`) and had its existing "npm CLI opens a browser tab" row reworded to note the binaries share that property rather than reading as an exception.
+- **New changelog subpage `changelogs/pptxdiff-binaries.md`**, added to nav — structurally different from every sibling subpage since `@pptxdiff/binaries` has no single package-level `CHANGELOG.md` (each OS has its own); this page transcludes all three under `## Windows`/`## macOS`/`## Linux` headings instead of one `--8<--` include.
+- **Real `mkdocs build --strict` failure found and fixed, not just described**: the three per-OS `CHANGELOG.md` files' relative link back to the root `CHANGELOG.md` (`../../../../CHANGELOG.md`, correct on GitHub) broke once transcluded into the new subpage — `pymdownx.snippets` doesn't rewrite relative links for their new location. Fixed at the source (the package-level files themselves, since the docs-site page has no content of its own) by swapping to the same absolute GitHub URL pattern every other subpage's "Source:" line already uses.
+- **`scripts/coverage_registry.yml`** gained `native-binaries`/`native-binaries-limitations`; `sync_doc_coverage.py --write` then `--check` re-run, confirmed 36 complete + 4 partial + 0 missing (of 40).
+- **Verified for real**: `mkdocs build --strict` clean (one remaining, expected, harmless warning about the brand-new file having no git history yet — resolves on commit). Directly grepped the built HTML to confirm the new anchor (`option-d-standalone-binary-no-nodejs-at-all`) matches exactly between the defining page and both linking pages, rather than trusting `--strict` alone (it validates linked files exist, not that `#fragment`s inside them do).
+- Full technical writeup: `docs/.scrolls/DOCS.md` §15 (new). `docs-site/CHANGELOG.md` gained a matching dated entry per the project's own house rule.
+
 ## Update (2026-08-05 — binaries: native Windows/Linux arm64 builds, `pptxdiff-win-arm64.exe`/`pptxdiff-linux-arm64`)
 - Direct, immediate follow-up to the mac-only arm64 addition below: "Can we support arm64 for windows and linux as well?" Unlike macOS, neither Windows nor Linux needs a signing step, so no new CI job was needed — both fold straight into the existing `build-linux-win` job.
 - **Verified `pkg` genuinely supports both targets first, hands-on, before implementing** (same rigor as every other step in this feature): the FIRST attempt (`pkg -t node22-linux-arm64 bin/cli.js ...`) failed outright with `ERR_ASSERTION`. `--debug` traced the real cause to a genuine exec-format failure: `pkg` needs to run a matching-arch "fabricator" helper binary to generate V8 bytecode for the entry script, and this x64 sandbox has no QEMU/binfmt arm64 emulation registered (confirmed empty, not assumed: `which qemu-aarch64` and `/proc/sys/fs/binfmt_misc` both came up empty) — the shell tried to interpret the foreign-arch ELF's raw bytes as a script, producing a `Syntax error`. `pkg`'s own warning named the fix: `--fallback-to-source` (ships the entry as plain JS instead of failing when bytecode generation isn't possible for the target arch) — added unconditionally to `buildOne()`'s pkg invocation (harmless no-op for same-arch builds, where bytecode generation just succeeds normally).

src/packages/binaries/pptxdiff-linux/CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to the Linux standalone `pptxdiff-linux`/
 `pptxdiff-linux-arm64` builds are documented here. The format is based on
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the version
 tracked is the `pptxdiff` app version bundled into the binary (see the
-root [`CHANGELOG.md`](../../../../CHANGELOG.md) for the app's own history)
+root [`CHANGELOG.md`](https://github.com/sugatoray/pptxdiff/blob/master/CHANGELOG.md) for the app's own history)
 since the binaries have no independent feature set of their own.
 
 ## [Unreleased]

src/packages/binaries/pptxdiff-mac/CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to the macOS standalone `pptxdiff-mac`/
 `pptxdiff-mac-arm64` builds are documented here. The format is based on
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the version
 tracked is the `pptxdiff` app version bundled into the binary (see the
-root [`CHANGELOG.md`](../../../../CHANGELOG.md) for the app's own history)
+root [`CHANGELOG.md`](https://github.com/sugatoray/pptxdiff/blob/master/CHANGELOG.md) for the app's own history)
 since the binaries have no independent feature set of their own.
 
 ## [Unreleased]

src/packages/binaries/pptxdiff-win/CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to the Windows standalone `pptxdiff-win.exe`/
 `pptxdiff-win-arm64.exe` builds are documented here. The format is based
 on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the version
 tracked is the `pptxdiff` app version bundled into the binary (see the
-root [`CHANGELOG.md`](../../../../CHANGELOG.md) for the app's own history)
+root [`CHANGELOG.md`](https://github.com/sugatoray/pptxdiff/blob/master/CHANGELOG.md) for the app's own history)
 since the binaries have no independent feature set of their own.
 
 ## [Unreleased]

src/pptxdiff/docs-site/CHANGELOG.md

@@ -24,6 +24,25 @@ summary, that one is the record of *why*.
 
 No changes yet.
 
+## 2026-08-05 — Content updates + new changelog subpage for standalone native binaries
+
+### Added
+
+- `getting-started.md`: new "Option D — standalone binary (no Node.js at all)" section; `cli.md` gained a one-paragraph cross-link to it.
+- `limitations.md`: new row for the standalone binaries' own limitations (unsigned/ad-hoc-signed, not on GitHub Releases yet).
+- New changelog subpage `changelogs/pptxdiff-binaries.md`, added to nav — structurally different from every other subpage since it transcludes THREE per-OS `CHANGELOG.md` files (no single package-level one exists for this package) under `## Windows` / `## macOS` / `## Linux` subheadings.
+- New `documentation-coverage.md` registry entries: `native-binaries` (feature, `partial`) and `native-binaries-limitations` (limitation, `complete`).
+
+### Fixed
+
+- The three per-OS `CHANGELOG.md` files' relative link back to the root `CHANGELOG.md` broke once transcluded into the new changelog subpage (`pymdownx.snippets` doesn't rewrite relative links for their new location) — caught by `mkdocs build --strict`, fixed by swapping to an absolute GitHub URL at the source.
+
+### Changed
+
+- `index.md`'s "No install required" card now mentions the binaries option.
+
+See `docs/.scrolls/DOCS.md` §15 for the full reasoning.
+
 ## 2026-07-31 — New "Headless CLI & Web API" page for `pptxdiff-cli`/`@pptxdiff/server`
 
 ### Added

src/pptxdiff/docs-site/docs/changelog.md

@@ -11,6 +11,7 @@ title: Changelog
 - [Changelog: pptxdiff](changelogs/pptxdiff.md)
 - [Changelog: @pptxdiff/cli](changelogs/pptxdiff-cli.md)
 - [Changelog: @pptxdiff/server](changelogs/pptxdiff-server.md)
+- [Changelog: @pptxdiff/binaries](changelogs/pptxdiff-binaries.md)
 
 ## VS Code Extension(s)
 

src/pptxdiff/docs-site/docs/changelogs/pptxdiff-binaries.md

@@ -0,0 +1,25 @@
+---
+title: "Changelog: @pptxdiff/binaries"
+---
+
+# Changelog: @pptxdiff/binaries
+
+Unlike this site's other package changelogs, `@pptxdiff/binaries` has no single package-level `CHANGELOG.md` — each OS's standalone binary has its own, since they're independent downloadable artifacts.
+
+## Windows
+
+Source: [`src/packages/binaries/pptxdiff-win/CHANGELOG.md`](https://github.com/sugatoray/pptxdiff/blob/master/src/packages/binaries/pptxdiff-win/CHANGELOG.md)
+
+--8<-- "src/packages/binaries/pptxdiff-win/CHANGELOG.md"
+
+## macOS
+
+Source: [`src/packages/binaries/pptxdiff-mac/CHANGELOG.md`](https://github.com/sugatoray/pptxdiff/blob/master/src/packages/binaries/pptxdiff-mac/CHANGELOG.md)
+
+--8<-- "src/packages/binaries/pptxdiff-mac/CHANGELOG.md"
+
+## Linux
+
+Source: [`src/packages/binaries/pptxdiff-linux/CHANGELOG.md`](https://github.com/sugatoray/pptxdiff/blob/master/src/packages/binaries/pptxdiff-linux/CHANGELOG.md)
+
+--8<-- "src/packages/binaries/pptxdiff-linux/CHANGELOG.md"

src/pptxdiff/docs-site/docs/cli.md

@@ -24,6 +24,8 @@ npm install -g pptxdiff && pptxdiff   # global install
 
 There are no command-line flags. One optional environment variable is supported — see [Lite mode](#lite-mode-cdn-sourcing) below.
 
+**No Node.js at all?** A standalone native executable per OS+chip runs this exact, unmodified `bin/cli.js` with the Node runtime embedded inside it — see [Getting Started → Option D](getting-started.md#option-d-standalone-binary-no-nodejs-at-all).
+
 ## What it does
 
 `bin/cli.js` is a stdlib-only Node script (`node:http` / `node:fs` / `node:child_process`, no npm dependencies):

src/pptxdiff/docs-site/docs/documentation-coverage.md

@@ -2,21 +2,21 @@
 title: Documentation Coverage
 render_macros: true
 coverage_summary:
-  generated_at: '2026-08-02T22:11:11Z'
+  generated_at: '2026-08-05T06:08:51Z'
   totals:
     overall:
-      items: 38
-      complete: 35
-      partial: 3
+      items: 40
+      complete: 36
+      partial: 4
       missing: 0
     feature:
-      items: 25
+      items: 26
       complete: 22
-      partial: 3
+      partial: 4
       missing: 0
     limitation:
-      items: 13
-      complete: 13
+      items: 14
+      complete: 14
       partial: 0
       missing: 0
   items:
@@ -112,6 +112,13 @@ coverage_summary:
     locations:
     - page: features/exports.md
       anchor: live-push
+  - id: native-binaries
+    kind: feature
+    title: Standalone native binaries (@pptxdiff/binaries, x64+arm64 for win/mac/linux)
+    quality: partial
+    locations:
+    - page: getting-started.md
+      anchor: option-d-standalone-binary-no-nodejs-at-all
   - id: npm-cli-packaging
     kind: feature
     title: npm CLI (bin/cli.js)
@@ -274,6 +281,14 @@ coverage_summary:
     locations:
     - page: limitations.md
       anchor: null
+  - id: native-binaries-limitations
+    kind: limitation
+    title: 'Standalone binaries: unsigned/ad-hoc-signed, macOS not cross-compiled,
+      not on GitHub Releases'
+    quality: complete
+    locations:
+    - page: limitations.md
+      anchor: null
   - id: offline-capability-limitations
     kind: limitation
     title: Offline-capability limitations (pdfjs-dist unvendored, latin-only font