README npx quickstart fails because the package is not published #1

Reproduction

On a clean Windows environment:

> npx --yes one-step-seo audit https://example.com --pages 5
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/one-step-seo - Not found

npm view one-step-seo version returns the same E404, and https://registry.npmjs.org/one-step-seo returns 404.

Environment: Windows 10, Node v24.16.0, npm 11.13.0.

Why this blocks the launch path

The README's first proof path is npx one-step-seo ... and describes it as "No install needed." The npm badge and package link also point to one-step-seo, so a first-time evaluator currently cannot run the advertised 30-second demo.

Source checkout result

The implementation itself works from a checkout:

• npm install: success, 0 vulnerabilities
• npm run check: 39/39 tests passed
• node bin/cli.mjs audit https://mmxfq.github.io/firstpass-site/ --pages 10: success; report files generated

That isolates the failure to package publication/discovery rather than the CLI runtime.

Suggested acceptance checks

• npm view one-step-seo version returns 0.1.0 (or the intended public version).
• The README's exact npx one-step-seo audit https://example.com --pages 5 command exits successfully from a directory without the repository checkout.
• The npm badge resolves to the published version rather than package not found.

If publication is intentionally pending, a temporary source-checkout quickstart above the npx command would keep the first-run path accurate.