Publish the generator to npm, as npx @pmndrs/docs

[abernier]

Makes the generator installable from npm, so a docs build no longer needs Docker.

$ cat foo.mdx | npx @pmndrs/docs               # one HTML fragment, on stdout
$ npx @pmndrs/docs                            # …or type the MDX yourself, Ctrl-D to compile
$ npx @pmndrs/docs docs out                    # one .html per .mdx, assets alongside
$ npx @pmndrs/docs docs out --format website   # the whole website, statically exported

--format fragment, the default, is the compiled MDX and nothing else — no layout, no stylesheet, no script — so it needs nothing but node. Mermaid stays a fenced block (server-side SVG is a follow-up) and Sandpack shows its code without the editor. Every website option (--libname, --base-path, --icon, --theme-*…) falls back to the environment variable it maps to, so Docker and build.yml keep working untouched.

Notable

• Bare npx @pmndrs/docs reads the terminal. It always could, but in silence, which is indistinguishable from a hang — it now says what it expects and how to end it, on stderr so stdout stays a clean pipe.
• Built on commander, as abernier/material-theme-builder is. Every website option is declared once with the environment variable the app reads it as, and Option.env() does the fallback — so --help documents the pairing and the Docker image keeps working with no flags at all.
• Turbopack refuses to build a project rooted under node_modules, which is exactly where an installed package lives. The app is therefore copied out before building — which also simplified things: /api is kept out of the export by not being copied, so nothing is moved aside and put back, and no exit handler is needed to survive nextBuild calling process.exit() itself.
• bin/build.mjs is deleted. It predated the Docker image, was never usable (the package was private, so npx @pmndrs/docs build always 404'd), and built a server bundle rather than a static export.
• Toc leaves the MDX components map. The page renders it from the layout with toc={doc.tableOfContents}; written in a doc it only ever crashed.
• compileMdxContent takes an options object, so the CLI can override components — that is how a fragment keeps the h1 the website draws from frontmatter.
• next/image → <img> in People. images.unoptimized is already set, so it bought nothing but a width requirement that broke rendering outside Next.

Verified

npm pack → install in a third-party folder → the three modes	✅ 17 fragments, 20 pages exported
repo build, as Docker and CI run it	✅ unchanged
lint · format · types · 108 unit tests	✅
tarball	1.0 MB

Before merging

NPM_TOKEN must exist as a repository secret. The release step published nothing while the package was private; now it really publishes, and this PR wires the token into its env.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HfCBpbazo3fr1n2EUXNyh5