docs: sweep docs and READMEs to the canonical vocabulary

Every docs page (error pages included) and README now follows the Terms
page: built-in devframes instead of a plugin concept, host framework /
host page / user app, node side / browser side, client runtime, RPC
client, viewer over shell, dock rail/panel, page script and in-page
channel, qualified scopes and sessions.

Author: antfubot

docs/content/2.adapters/1.initiate.md

@@ -1,9 +1,9 @@
 ---
 title: 'The Standard Handler'
-description: 'initDevframe() turns a DevframeDefinition into a live instance whose .handler — a Web Standard (request: Request) => Promise<Response> — carries the entire surface (SPA, __connection.json discovery, RPC socket, auth gate, MCP route) under one mount base. Every other serving path — adapters,…'
+description: 'initDevframe() turns a DevframeDefinition into a running devframe whose .handler — a Web Standard (request: Request) => Promise<Response> — carries everything a devframe serves (SPA, __connection.json discovery, RPC socket, auth gate, MCP route) under one mount base. Every other serving path — adapters,…'
 ---
 
-`initDevframe()` turns a `DevframeDefinition` into a live instance whose `.handler` — a Web Standard `(request: Request) => Promise<Response>` — carries the entire surface (SPA, `__connection.json` discovery, RPC socket, auth gate, MCP route) under one mount base. Every other serving path — [adapters](/adapters), [framework packages](/frameworks), [hub](/guide/hub-initiate) — is assembled from it. Mount it with a catch-all route.
+`initDevframe()` turns a `DevframeDefinition` into a running devframe whose `.handler` — a Web Standard `(request: Request) => Promise<Response>` — carries everything a devframe serves (SPA, `__connection.json` discovery, RPC socket, auth gate, MCP route) under one mount base. Every other serving path — [adapters](/adapters), [framework kits](/frameworks), [hub](/guide/hub-initiate) — is assembled from it. Mount it with a catch-all route.
 
 ```ts
 import { initDevframe } from 'devframe/initiate'
@@ -15,7 +15,7 @@ const devtools = initDevframe(myDevframe, { base: '/__my-tool/' })
 // devtools.connectionMeta(), devtools.close()
 ```
 
-`base` is required — pass `resolveBasePath(def, 'hosted')` (`def.basePath ?? /__<id>/`) to default it; the instance echoes it back as `devtools.base`. `handler`/`nodeMiddleware` await readiness internally. The instance binds no port — [the WebSocket binding](#the-websocket-binding) is the host's call.
+`base` is required — pass `resolveBasePath(def, 'hosted')` (`def.basePath ?? /__<id>/`) to default it; the running devframe echoes it back as `devtools.base`. `handler`/`nodeMiddleware` await readiness internally. The running devframe binds no port — [the WebSocket binding](#the-websocket-binding) is the host framework's call.
 
 ## Mount the handler
 
@@ -110,24 +110,24 @@ export const GET = ({ request }) => devtools.handler(request)
 ```
 
 ::
-Frameworks with dev-time module reloading (Next, Nitro, SvelteKit) re-evaluate the calling module, so memoize the instance on `globalThis` to avoid leaking a socket per reload. `@devframes/next`'s `createDevframeNextHandler` handles this.
+Host frameworks with dev-time module reloading (Next, Nitro, SvelteKit) re-evaluate the calling module, so memoize the running devframe on `globalThis` to avoid leaking a socket per reload. `@devframes/next`'s `createDevframeNextHandler` handles this.
 
 ## The WebSocket binding
 
-Fetch handlers only hand over `Request`s, so the host binds the RPC socket. The **local binding** resolves in this order:
+Fetch handlers only hand over `Request`s, so the host framework binds the RPC socket. The **local binding** resolves in this order:
 
 1. **`ws.port`** — a side-car server on that exact port.
-2. **`server`** — share the host's `node:http` server; the upgrade binds at `<base>__ws`. No extra ports.
-3. **`ws: { sidecar: true }`** — a side-car server on a free port, for hosts whose handlers never see upgrades (Next.js route handlers, Nitro, Rsbuild).
-4. **The host's own upgrades** — with none set, the socket waits: `devtools.attach(server)` routes a server's `upgrade` events (returning a detach fn); `devtools.handleUpgrade(req, socket, head)` completes a single one from a listener you own.
+2. **`server`** — share the host framework's `node:http` server; the upgrade binds at `<base>__ws`. No extra ports.
+3. **`ws: { sidecar: true }`** — a side-car server on a free port, for host frameworks whose handlers never see upgrades (Next.js route handlers, Nitro, Rsbuild).
+4. **The host framework's own upgrades** — with none set, the socket waits: `devtools.attach(server)` routes a server's `upgrade` events (returning a detach fn); `devtools.handleUpgrade(req, socket, head)` completes a single one from a listener you own.
 
-`ws.url` controls the *advertisement* instead — the browser dials it verbatim. Alone, an external server owns the transport and its auth (wire the instance's `context` via `createContextRpcServer` + a WS transport); alongside a local binding it overrides only the advertisement (the tunnel pattern).
+`ws.url` controls the *advertisement* instead — the browser dials it verbatim. Alone, an external WebSocket server owns the transport and its auth (wire the running devframe's `context` via `createContextRpcServer` + a WS transport); alongside a local binding it overrides only the advertisement (the tunnel pattern).
 
-`__connection.json` describes the active combination. Asking a configured instance to take over host upgrades reports `DF0055` (a local binding owns the socket) or `DF0056` (`ws.url` handed it off).
+`__connection.json` describes the active combination. Asking a configured running devframe to take over the host framework's upgrades reports `DF0055` (a local binding owns the socket) or `DF0056` (`ws.url` handed it off).
 
 ## Auth
 
-The instance **gates by default**. The interactive OTP handler wires automatically, printing its code/magic-link banner once the public origin is known (the first request, or the `origin` option). Pass `auth: false` for single-user localhost, or a `DevframeAuthHandler` for a custom scheme.
+The running devframe **gates by default**. The interactive OTP handler wires automatically, printing its code/magic-link banner once the public origin is known (the first request, or the `origin` option). Pass `auth: false` for single-user localhost, or a `DevframeAuthHandler` for a custom scheme.
 
 ## Relation to the other adapters
 

docs/content/2.adapters/2.cac.md

@@ -65,7 +65,7 @@ defineDevframe({
     port: 7777, // preferred port
     portRange: [7777, 9000], // passed through to get-port-please
     random: false, // passed through to get-port-please
-    host: '127.0.0.1', // default host; --host overrides
+    host: '127.0.0.1', // default bind host; --host overrides
     open: true, // auto-open the browser on dev start; embeds the current OTP so the tab lands authenticated
     configure(cli) { // contribute capability flags/commands
       cli.option('--config <file>', 'Custom config file')

docs/content/2.adapters/4.build.md

@@ -25,4 +25,4 @@ await createBuild(devframe, {
 | `distDir` | `def.clientAssets` | SPA dist override (or [remote assets](/guide/client-assets)). |
 | `pretty` | `false` | Pretty-print dump JSON. |
 
-The client runs read-only. For a custom URL base, build with relative asset paths (`vite.base: './'`).
+The RPC client runs read-only. For a custom URL base, build with relative asset paths (`vite.base: './'`).

docs/content/2.adapters/5.vite.md

@@ -21,4 +21,4 @@ The returned object has the shape `{ name, devtools: { setup, capabilities } }`.
 | `name` | `devframe:<id>` | Plugin name. |
 | `base` | `def.basePath ?? /.${id}/` | Mount path override. |
 | `dock` | `{}` | Overrides for the iframe dock entry (category, icon, when). |
-| `setup` | — | Host-only setup hook; receives the kit-augmented context. |
+| `setup` | — | Setup hook run only in the Vite host; receives the kit-augmented context. |

docs/content/2.adapters/7.mcp.md

@@ -1,9 +1,9 @@
 ---
 title: 'MCP'
-description: 'Exposes a devframe''s agent host as a Model Context Protocol server: agents call flagged RPCs and read resources.'
+description: 'Exposes a devframe''s agent-facing API as a Model Context Protocol server: coding agents call flagged RPCs and read resources.'
 ---
 
-Exposes a devframe's agent host as a [Model Context Protocol](https://modelcontextprotocol.io) server: agents call flagged RPCs and read resources.
+Exposes a devframe's agent-facing API as a [Model Context Protocol](https://modelcontextprotocol.io) server: coding agents call flagged RPCs and read resources.
 
 ```ts
 import { createMcpServer } from 'devframe/adapters/mcp'
@@ -12,11 +12,11 @@ import devframe from './devframe'
 await createMcpServer(devframe, { transport: 'stdio' })
 ```
 
-`@modelcontextprotocol/server` is a peer dependency; `createMcpServer` speaks `stdio`, spawned per session.
+`@modelcontextprotocol/server` is a peer dependency; `createMcpServer` speaks `stdio`, spawned per MCP session.
 
 ## Route-based server
 
-The dev server exposes the same surface over HTTP, live. Enable with `cli.mcp`:
+The dev server exposes the same MCP API over HTTP, live. Enable with `cli.mcp`:
 
 ```ts
 import { defineDevframe } from 'devframe'
@@ -29,9 +29,9 @@ export default defineDevframe({
 })
 ```
 
-The endpoint speaks Streamable-HTTP at `/__mcp` (`/__<id>/__mcp` under a host), sharing its origin/port. `--mcp` / `--no-mcp` override; `__connection.json` advertises it.
+The endpoint speaks Streamable-HTTP at `/__mcp` (`/__<id>/__mcp` under a host framework), sharing its origin/port. `--mcp` / `--no-mcp` override; `__connection.json` advertises it.
 
-Each session gets its own MCP server, keyed by `Mcp-Session-Id`. An origin gate requires `Origin` be loopback (or allow-listed) and rejects `Origin`-less requests. Widen for a tunnel/LAN origin with `cli: { mcp: { allowedOrigins: ['https://tunnel.example.com'] } }`.
+Each MCP session gets its own MCP server, keyed by `Mcp-Session-Id`. An origin gate requires `Origin` be loopback (or allow-listed) and rejects `Origin`-less requests. Widen for a tunnel/LAN origin with `cli: { mcp: { allowedOrigins: ['https://tunnel.example.com'] } }`.
 
 ### Hosted bridges
 
@@ -45,7 +45,7 @@ devframeViteBridge(devframe, { mcp: true })
 createDevframeNextHandler(devframe, { mcp: true })
 ```
 
-## Custom hosts
+## Custom host frameworks
 
 `createMcpFetchHandler(ctx, options)` returns the endpoint as a `Request → Response` handler plus a `dispose()` — mount on any fetch server.
 
@@ -75,8 +75,8 @@ The `devframe` bin ships an MCP **connector** ([next-devtools-mcp](https://githu
 Two gateway tools (`devframe:connect:*` ids — see [tool ids and wire names](/guide/agent-native#tool-ids-and-wire-names)):
 
 - **`devframe_connect_list-instances`** — list running dev servers and their MCP tools.
-- **`devframe_connect_call-tool`** — invoke one tool on an instance (`{ port, tool, args }`) over Streamable-HTTP.
+- **`devframe_connect_call-tool`** — invoke one tool on a running devframe (`{ port, tool, args }`) over Streamable-HTTP.
 
-Discovery reads the **instance registry**: every `createDevServer` writes `~/.devframe/instances/<pid>-<port>.json`, dialed with a loopback origin. In-process hosts register via `registerDevframeInstance` (`devframe/node`). `--port <n>` probes a port; `DEVFRAME_INSTANCES_DIR` relocates the registry, `DEVFRAME_DISABLE_INSTANCE_REGISTRY=1` opts out.
+Discovery reads the **instance registry**: every `createDevServer` writes `~/.devframe/instances/<pid>-<port>.json`, dialed with a loopback origin. In-process host frameworks register via `registerDevframeInstance` (`devframe/node`). `--port <n>` probes a port; `DEVFRAME_INSTANCES_DIR` relocates the registry, `DEVFRAME_DISABLE_INSTANCE_REGISTRY=1` opts out.
 
 See [Agent-Native](/guide/agent-native) for the API and safety model.

docs/content/2.adapters/index.md

@@ -26,7 +26,7 @@ SPA basePath depends on the adapter:
 | Adapter kind | Default basePath | Reason |
 |--------------|------------------|--------|
 | `cli`, `build` (standalone) | `/` | Owns the origin. |
-| `vite`, `embedded` (hosted) | `/__<id>/` | Shares a host's origin. |
+| `vite`, `embedded` (hosted) | `/__<id>/` | Shares a host framework's origin. |
 
 Override with `DevframeDefinition.basePath`:
 
@@ -38,4 +38,4 @@ defineDevframe({
 })
 ```
 
-The client discovers its SPA base at runtime — see [Client](/guide/client#runtime-basepath-discovery).
+The SPA discovers its base at runtime — see [Client](/guide/client#runtime-basepath-discovery).

docs/content/3.frameworks/1.vite.md

@@ -1,9 +1,9 @@
 ---
 title: 'Vite'
-description: '@devframes/vite splits into @devframes/vite/single (dev-serve one devframe''s SPA) and @devframes/vite/hub (mount a devframes-hub); the bare import throws.'
+description: '@devframes/vite splits into @devframes/vite/single (dev-serve one devframe''s SPA) and @devframes/vite/hub (mount a hub); the bare import throws.'
 ---
 
-`@devframes/vite` splits into **`@devframes/vite/single`** (dev-serve one devframe's SPA) and [**`@devframes/vite/hub`**](#mounting-a-hub) (mount a devframes-hub); the bare import throws.
+`@devframes/vite` splits into **`@devframes/vite/single`** (dev-serve one devframe's SPA) and [**`@devframes/vite/hub`**](#mounting-a-hub) (mount a hub); the bare import throws.
 
 `single` exports `devframeVitePlugin`, `devframeViteBridge`, and `devframeVite`; also used by [`@devframes/nuxt`](/frameworks/nuxt).
 
@@ -16,7 +16,7 @@ export default defineConfig({
   // Statically mounts the built SPA at `/__<id>/` — no RPC server:
   plugins: [devframeVitePlugin(devframe)],
   // Or bridge the RPC/WS backend into this dev server instead — the
-  // host app owns the SPA:
+  // user app owns the SPA:
   // plugins: [devframeViteBridge(devframe)],
 })
 ```
@@ -48,7 +48,7 @@ Devframe spawns a separate RPC + WS server and registers Vite middleware at `<ba
 
 ## Mounting a hub
 
-`@devframes/vite/hub` mounts a [devframes-hub](/guide/hub) with `viteDevframeHub()`: wraps `initHub`, shares Vite's HTTP server, defaults dock UI to `@devframes/hub-ui`.
+`@devframes/vite/hub` mounts a [hub](/guide/hub) with `viteDevframeHub()`: wraps `initHub`, shares Vite's HTTP server, defaults dock UI to `@devframes/hub-ui`.
 
 
 ```ts

docs/content/3.frameworks/2.nuxt.md

@@ -1,11 +1,11 @@
 ---
 title: 'Nuxt'
-description: '@devframes/nuxt splits into @devframes/nuxt/single (author one devframe) and @devframes/nuxt/hub (mount a devframes-hub); the bare import throws.'
+description: '@devframes/nuxt splits into @devframes/nuxt/single (author one devframe) and @devframes/nuxt/hub (mount a hub); the bare import throws.'
 ---
 
-`@devframes/nuxt` splits into `@devframes/nuxt/single` (author one devframe) and [`@devframes/nuxt/hub`](#mounting-a-hub) (mount a devframes-hub); the bare import throws.
+`@devframes/nuxt` splits into `@devframes/nuxt/single` (author one devframe) and [`@devframes/nuxt/hub`](#mounting-a-hub) (mount a hub); the bare import throws.
 
-The `single` module wires a Nuxt SPA as a devframe client and types `useNuxtApp().$rpc` as `DevframeRpcClient`.
+The `single` module wires a Nuxt SPA as a devframe's browser side and types `useNuxtApp().$rpc` as `DevframeRpcClient`.
 
 ## Install
 
@@ -67,7 +67,7 @@ export default defineNuxtConfig({
 - Runs `devframe.setup(ctx, { flags })`.
 - Cleans up on Vite restart, `nuxt dev` shutdown, and bundle close.
 
-On by default when `devframe` is set; disable it (client-only) with `devMiddleware: false`.
+On by default when `devframe` is set; disable it (browser side only) with `devMiddleware: false`.
 
 ### Customizing the bridge
 
@@ -116,7 +116,7 @@ At runtime the SPA fetches `./__connection.json` and branches on `backend` — `
 
 ## Mounting a hub
 
-`@devframes/nuxt/hub` mounts a whole [devframes-hub](/guide/hub) alongside `nuxt dev`, injecting `@devframes/hub-ui`'s dock. `ui` swaps the default; `ui: false` gives a headless hub via `@devframes/nuxt/hub/client`.
+`@devframes/nuxt/hub` mounts a whole [hub](/guide/hub) alongside `nuxt dev`, injecting `@devframes/hub-ui`'s dock. `ui` swaps the default; `ui: false` gives a headless hub via `@devframes/nuxt/hub/client`.
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({

docs/content/3.frameworks/3.next.md

@@ -8,7 +8,7 @@ description: '@devframes/next hosts devframes from a Next.js App Router app via
 
 `@devframes/next` hosts devframes from a Next.js App Router app via a route handler: one `fetch` handler serves each SPA and its `__connection.json` via [`serveStaticHandler`](/adapters/dev).
 
-It splits into `@devframes/next/single` and [`@devframes/next/hub`](#mounting-a-hub); the bare import throws. `single` gives **`withDevframe()`**, **`createDevframeNextHandler()`**, and a React client (`@devframes/next/single/client`).
+It splits into `@devframes/next/single` and [`@devframes/next/hub`](#mounting-a-hub); the bare import throws. `single` gives **`withDevframe()`**, **`createDevframeNextHandler()`**, and a React RPC-client helper (`@devframes/next/single/client`).
 
 ## Config
 
@@ -50,7 +50,7 @@ export const GET = handler.fetch
 
 ## Hosting a hub
 
-[`@devframes/hub`](/guide/hub)'s `initHub` mounts every frame under `<base><id>/` behind one `handler` (memoize on `globalThis`; see `examples/hub-next`):
+[`@devframes/hub`](/guide/hub)'s `initHub` mounts every devframe under `<base><id>/` behind one `handler` (memoize on `globalThis`; see `examples/hub-next`):
 
 ```ts [devframe/host.ts]
 import { DEVFRAMES_HUB_BASE, initHub } from '@devframes/hub/initiate'
@@ -76,7 +76,7 @@ export async function GET(request: Request): Promise<Response> {
 }
 ```
 
-## React client
+## React RPC client
 
 ```tsx [app/providers.tsx]
 'use client'

docs/content/3.frameworks/index.md

@@ -1,14 +1,14 @@
 ---
 title: 'Frameworks'
-description: 'The framework packages — @devframes/vite, @devframes/nuxt, @devframes/next — integrate devframe with a meta-framework''s dev server. Two subpaths:'
+description: 'The framework kits — @devframes/vite, @devframes/nuxt, @devframes/next — integrate devframe with a meta-framework''s dev server. Two subpaths:'
 ---
 
-The framework packages — [`@devframes/vite`](/frameworks/vite), [`@devframes/nuxt`](/frameworks/nuxt), [`@devframes/next`](/frameworks/next) — integrate devframe with a meta-framework's dev server. Two **subpaths**:
+The framework kits — [`@devframes/vite`](/frameworks/vite), [`@devframes/nuxt`](/frameworks/nuxt), [`@devframes/next`](/frameworks/next) — integrate devframe with a meta-framework's dev server. Two **subpaths**:
 
 | Scope | Subpath | You are… |
 |-------|---------|----------|
 | **single** | `.../single` | building & dev-serving a **single devframe's SPA** with that tool |
-| **hub** | `.../hub` | mounting a whole **[devframes-hub](/guide/hub)** (many integrations) inside that tool |
+| **hub** | `.../hub` | mounting a whole **[hub](/guide/hub)** (many devframes) inside that tool |
 
 The bare package root throws, pointing to the two subpaths.
 
@@ -22,8 +22,8 @@ The bare package root throws, pointing to the two subpaths.
 
 For framework-neutral CLI/build/embedded outputs, use the [adapters](/adapters) instead.
 
-## hub: mount a devframes-hub
+## hub: mount a hub
 
-Each `hub` entry wraps [`initHub`](/guide/hub-initiate) and defaults the UI to [`@devframes/hub-ui`](/guide/build-your-own-hub-ui)'s `createUi()` (`ui` to override, `ui: false` for headless). Per tool: **[Vite](/frameworks/vite#mounting-a-hub)**, **[Nuxt](/frameworks/nuxt#mounting-a-hub)**, **[Next](/frameworks/next#mounting-a-hub)**.
+Each `hub` scope wraps [`initHub`](/guide/hub-initiate) and defaults the UI to [`@devframes/hub-ui`](/guide/build-your-own-hub-ui)'s `createUi()` (`ui` to override, `ui: false` for headless). Per tool: **[Vite](/frameworks/vite#mounting-a-hub)**, **[Nuxt](/frameworks/nuxt#mounting-a-hub)**, **[Next](/frameworks/next#mounting-a-hub)**.
 
 `@devframes/vite/hub` and `@devframes/nuxt/hub` recommend the native viewers ([Vite DevTools](https://devtools.vite.dev), [Nuxt DevTools](https://devtools.nuxt.com)) once (silence with `{ quiet: true }`). Next has none, so `@devframes/next/hub` stays quiet.