build: retire the old TypeDoc theme and its assets

[soimy]

Phase E of #81, stacked on the deployment phase. Review order: #82 → content migration → deployment → this.

What goes

typedoc-unhoax-theme has been unreferenced since the API reference moved to markdown, and the two assets it loaded were still being published.

• the theme is out of devDependencies (and out of node_modules after a fresh npm ci against the committed lockfile);
• assets/custom.css and assets/custom.js are deleted and out of the files allowlist with them;
• the published tarball goes from 30 files / 67kB to 28 files / 66.6kB, with assets/favicon.ico the only asset left in the allowlist (the repository still tracks the icons and the preview image; they were never published) — measured with npm pack --dry-run before and after;
• AGENTS.md and docs/contributor/compatibility.md carry the new allowlist and the measured counts.

What stays, and why

gh-pages keeps its place for now: doc:publish is the fallback deployment path until the Pages source is switched to GitHub Actions, and removing it before that switch would leave no way to publish. The deferred-work ledger records it as the one remaining step, together with cz-conventional-changelog (interactive commitizen commits only, unrelated to this migration).

Verification

npm ci --include=dev against the committed lockfile; lint 0/0; format:check; typecheck (TS 7.0.2); verify:docs; docs:build (11 legacy redirects written); 126 tests passed / 2 skipped; coverage 100%; verify:package green — bundler, node16, nodenext and the three documentation examples.

[soimy]

This layer is where files changed (the theme retirement took the tarball from 30 files to 28), so it is where the missing guarantee belongs: what the package publishes was never asserted. npm pack had been measured once — 28 files, no docs/ entry — but nothing failed if the site's source tree or the uncompressed PNGs joined the allowlist, or if src/ and a tsconfig left it. That mattered more after this migration put a whole tracked docs/ tree next to src, which is also in the allowlist.

scripts/verify-package.mjs now compares npm pack --dry-run --json against the intended file list and names the difference. Measured in both directions before trusting it:

State	Result
docs added to files	exit 1 — 179 files, not the 28 intended — not expected: docs/.vitepress/config.mts, … and 143 more
src dropped from files	exit 1 — 21 files, not the 28 intended — missing: src/abstract-bin.ts, src/geom/Rectangle.ts, …
intended allowlist	exit 0 — ✓ npm pack --dry-run lists the 28 intended files

Commit: build: pin the published file set, which also records in AGENTS.md that the list is pinned and where to edit it. The step numbering in that script was renumbered around the new check (it had two steps numbered 3).

[soimy]

The one item this layer's audit could not fix, so it goes in the ledger with the rest of the packaging follow-ups: a CommonJS TypeScript consumer under node16/nodenext gets TS1479 for a static import and TS1471 for import … = require(…), while await import(…), node10/bundler resolution and JavaScript require() all work.

Local to this PR because the fix is the same kind of decision the other entries here are: an exports map with per-format conditions and declarations — which also seals the deep imports this repository keeps working, hence 3.0.0. The sharp edge itself is documented for users in docs/user/troubleshooting.md (that part rides on #83); the measurements and the gate's blind spot are in the new bullet, and the section's "Neither … both" became "None of these … each" now that there are three.

[soimy]

Rebased on the current #84 head and out of draft. Gates on this head (91f973a): Node 20/22/24 matrix green, Build documentation green, Deploy to GitHub Pages correctly skipped on a PR. Locally the top layer also passes build + verify:package (28 intended files, six documentation examples executed against the installed tarball).

Three layers, one merge order: #83 → #84 → #85. Each next layer's base branch needs retargeting to master once the previous one is squashed.

[greptile-apps]

Confidence Score: 5/5

[Low risk] Removes old documentation theme assets and updates build verification.

Safe to merge; no blocking findings were identified.

What we checked:

• Validated that the 28-file package archive, dry-run listing, and inventory matched and verification passed; in an isolated checkout, adding a retired asset to the allowlist caused the 29-file package to be rejected.
• Opened and compared docs before and after asset removal; all four pages loaded with content and returned 200 in both versions, with no failed requests.
• Reproduced gate behavior on the package: normal 28-file listings passed, and after altering the allowlist to include assets/custom.css, the 29-file package was rejected.
• Observed that all four docs pages returned 200 and displayed content in both runs, and the absence of a favicon link predates this PR.

Summary

This PR removes the old TypeDoc theme and its custom assets, updates the published-file list, and adds an exact package inventory check. The package contains the intended 28 files, and the documentation pages continue to render. No issues were identified.

_{Reviews (1) · Last reviewed commit: "docs: record the CommonJS TypeScript imp..."}