Address review: switch browser subtrees to @moss-dev/moss-web

@HarshaNalluru and @yatharthk2 pointed out that the correct npm package
for browser / WebAssembly usage is `@moss-dev/moss-web` (not the Node
SDK `@moss-dev/moss`). Applied the correction in the two subtrees that
run in a browser:

- apps/next-js: package.json dep, actions.ts import, actions.test.ts
  vi.mock, README install command -> @moss-dev/moss-web. Regenerated
  package-lock.json. Also fixed a pre-existing type mismatch now
  surfaced by the new SDK: `results.timeTakenInMs` -> `timeTakenMs`
  (the new SearchResult shape).
- packages/vitepress-plugin-moss: package.json dep, Search.vue (static
  + dynamic imports), README dependency-split prose ->
  @moss-dev/moss-web. Regenerated pnpm-lock.yaml.
- packages/vitepress-plugin-moss/demo-site getting-started.md and
  index.md JS install commands and imports -> @moss-dev/moss-web.
- Generated TypeDoc reference docs under
  packages/vitepress-plugin-moss/demo-site/documentation/docs/reference/:
  - js/*: renamed @moss-dev/moss -> @moss-dev/moss-web and dropped the
    inherited v1.0.0-beta.7 version suffix down to v1.0.0 (moss-web has
    no betas published)
  - python/*: dropped the inherited v1.0.0b16 -> v1.0.0 (moss@1.0.0 is
    the only version on PyPI; same flag from @HarshaNalluru on
    reference/python/classes/MossClient.md)

Verification:
- `npm install` + `npx tsc --noEmit` on apps/next-js: clean
- `pnpm install --lockfile-only` on packages/vitepress-plugin-moss:
  clean; lock now has 3 @moss-dev/moss-web entries and zero non-hyphen
  @moss-dev/moss entries

All other @moss-dev/moss references in the repo (SDK source, Node demo
apps like moss-bun, docker/javascript, the Vercel SDK, test fixtures,
moss-live-labs TypeScript examples, root README code snippet, etc.)
are Node contexts and stay on @moss-dev/moss — those are not browser
usage.

Author: ashvathsureshkumar

apps/next-js/README.md

@@ -47,6 +47,6 @@ This demo showcases how to use **Server Actions** to securely interact with Moss
 
 To add Moss to your own Next.js app:
 
-1. Install the SDK: `npm install @moss-dev/moss`
+1. Install the SDK: `npm install @moss-dev/moss-web`
 2. Create a Server Action (see `app/actions.ts`).
 3. Call the action from your React components.

apps/next-js/app/actions.test.ts

@@ -3,7 +3,7 @@ import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest'
 const mockLoadIndex = vi.fn()
 const mockQuery = vi.fn()
 
-vi.mock('@moss-dev/moss', () => ({
+vi.mock('@moss-dev/moss-web', () => ({
   MossClient: vi.fn().mockImplementation(() => ({
     loadIndex: mockLoadIndex,
     query: mockQuery,

apps/next-js/app/actions.ts

@@ -1,6 +1,6 @@
 'use server'
 
-import { MossClient } from "@moss-dev/moss";
+import { MossClient } from "@moss-dev/moss-web";
 
 /**
  * Server Action to perform semantic search using Moss SDK.
@@ -33,7 +33,7 @@ export async function searchMoss(query: string) {
         score: doc.score,
         metadata: doc.metadata
       })),
-      timeTaken: results.timeTakenInMs
+      timeTaken: results.timeTakenMs
     };
   } catch (error) {
     console.error("Moss Search Error:", error);

apps/next-js/package-lock.json

@@ -11,7 +11,7 @@
     "test": "vitest run"
   },
   "dependencies": {
-    "@moss-dev/moss": "^1.0.0",
+    "@moss-dev/moss-web": "^1.0.0",
     "lucide-react": "^0.563.0",
     "next": "16.2.3",
     "react": "19.2.3",

apps/next-js/package.json

@@ -27,7 +27,7 @@ Index is live on Moss cloud                     (seamless handoff, no user actio
 
 Two separate npm packages are involved:
 - **`@inferedge-rest/moss`** — Node.js REST client used **at build time** (inside `@moss-tools/md-indexer`) to upload documents
-- **`@moss-dev/moss`** — WebAssembly browser SDK used **at runtime** to download the index and run local queries
+- **`@moss-dev/moss-web`** — WebAssembly browser SDK used **at runtime** to download the index and run local queries
 
 ---
 
@@ -288,7 +288,7 @@ vitepress-plugin-moss
 │   ├── @inferedge-rest/moss     REST client for uploading to Moss cloud
 │   ├── vitepress                uses resolveConfig + createMarkdownRenderer
 │   └── cheerio / gray-matter   HTML parsing, frontmatter
-└── @moss-dev/moss           ← runtime only (browser WebAssembly)
+└── @moss-dev/moss-web       ← runtime only (browser WebAssembly)
     └── Queries run locally after index is downloaded
 ```
 

packages/vitepress-plugin-moss/README.md

@@ -3,7 +3,7 @@ import { ref, shallowRef, computed, nextTick, watch, onBeforeUnmount, onMounted
 import { useData, useRouter } from 'vitepress'
 import { onKeyStroke, useScrollLock, useInfiniteScroll } from '@vueuse/core'
 import { useFocusTrap } from '@vueuse/integrations/useFocusTrap'
-import type { SearchResult, QueryResultDocumentInfo } from '@moss-dev/moss'
+import type { SearchResult, QueryResultDocumentInfo } from '@moss-dev/moss-web'
 import SearchButton from './SearchButton.vue'
 import mossLogo from './moss-logo.png'
 
@@ -292,7 +292,7 @@ async function initMoss() {
   status.value = 'initializing'
   initPromise = (async () => {
     try {
-      const { MossClient } = await import(/* @vite-ignore */ '@moss-dev/moss')
+      const { MossClient } = await import(/* @vite-ignore */ '@moss-dev/moss-web')
       const client = new MossClient((options.value as any).projectId, (options.value as any).projectKey)
       mossClient.value = client
       status.value = 'ready'