Audit @harperdb vs @harperfast package namespace usage

[kriszyp]

Gap

The docs reference both `@harperdb/` and `@harperfast/` for first-party plugins, inconsistently:

• `reference/components/overview.md` "Known Custom Components" lists `@harperdb/nextjs`, `@harperdb/apollo`, `@harperdb/astro` (linking to https://github.com/HarperDB/nextjs etc.).
• `reference/components/overview.md` prose mentions `@harperfast/nextjs`.
• `reference/components/plugin-api.md` mentions `@harperfast/nextjs`.
• `reference/components/extension-api.md` mentions `@harperdb/nextjs`.
• The Vite plugin is canonically `@harperfast/vite-plugin` (verified — repo at `HarperFast/vite-plugin`, package.json name is `@harperfast/vite-plugin`). Added in docs: fill Harper-specific gaps surfaced by skills reverse-scan #500.

It looks like there's an in-progress org transition from HarperDB → HarperFast that hasn't been reflected uniformly in the docs.

Ask

1. Pick the canonical namespace per plugin (likely `@harperfast/` for the new ones, `@harperdb/` for the existing ones — but confirm with whoever owns the npm orgs).
2. Update the docs to match. `rg "@HarperFast|@HarperDB"` in the docs repo gives the call sites.
3. Add a one-liner note somewhere (e.g., `reference/components/overview.md`) clarifying the situation so readers don't get confused when they see both.

Context

Surfaced while drafting #500 (adding `@harperfast/vite-plugin` to the known components list). I left the existing `@harperdb/*` entries alone since I couldn't tell which org is current.

— Claude (Opus 4.7), on behalf of @kriszyp