lumen v0.2.0 is the first public release — launch-ready docs, community surface, and a tag-driven npm publish pipeline.
Install: npm install -g @lumen-seo/cli · One-off: npx -y @lumen-seo/cli audit https://example.com · Docs: https://nitishagar.github.io/lumen/
First npm publish
The five @lumen-seo/* workspaces publish in dependency order (core → audit → providers → mcp → cli) the moment the one-time NODE_AUTH_TOKEN secret is configured — the exact setup step v0.1.0's publish skipped on, now documented in docs/release.md. Re-running this release workflow after adding the secret completes the publish; duplicates are handled idempotently, and the site's install commands resolve as soon as the packages appear.
Launch readiness
- README rewritten for the launch — quickstart, MCP onboarding snippet, npm badge, TypeScript-source packaging note (was still describing the M0 bootstrap scaffold and pointing at a planning path that no longer exists).
- LICENSE restructured to the canonical Apache-2.0 layout so GitHub detects the license (the prepended notice pushed it to "Other").
- SECURITY.md now points at the
lumenadvisory URL and@lumen-seo/*package names (it still referenced the pre-renameseoliteslug). - Root workspace renamed
seolite→lumen; per-packagefilesallowlists,engines >= 22.7, and real READMEs forcore/audit/cli/mcpso npm pages aren't bare manifests. - CHANGELOG.md added (0.1.0 history + this release), bug/feature issue templates, PR template.
The system (unchanged from v0.1.0, now launch-packaged)
- 18-rule site audit engine — bounded crawl, severity scoring, CI exit codes
- 7 free-tier BYOK providers with pacing and provenance
- 5 MCP tools over stdio + thin Cloudflare Worker gateway
- 7-command CLI with JSON everywhere and JSONL rank history
Full changelog: https://github.com/nitishagar/lumen/blob/main/CHANGELOG.md