refactor!: remove deprecated APIs for 0.10 (#393)

Author: antfubot

alias.ts

@@ -96,7 +96,6 @@ export const alias = {
   '@devframes/plugin-terminals': p('terminals/src/node/index.ts'),
   '@devframes/plugin-git': p('git/src/node/index.ts'),
   'devframe/recipes/interactive-auth': r('devframe/src/recipes/interactive-auth.ts'),
-  'devframe/recipes/common-rpc-functions': r('devframe/src/recipes/common-rpc-functions.ts'),
   'devframe/client': r('devframe/src/client/index.ts'),
   'devframe': r('devframe/src'),
   '@devframes/plugin-data-inspector/inject': p('data-inspector/src/inject/index.ts'),

docs/content/1.guide/12.in-page-channel.md

@@ -66,7 +66,7 @@ Channel names are namespaced with the devframe id, like RPC ids. Function names
 
 The required `functions` option and optional `events` option declare every incoming name on the endpoint's protocol side; use `{}` for an empty direction. Functions require a `handler`. Events accept an optional `handler`, and `{}` registers an event for runtime subscriptions through `on()`. Handlers are contextually typed from the shared protocol and support Standard-Schema argument validation and `jsonSerializable` metadata. `defineChannelFunction` retains the named definition shape for lower-level authoring.
 
-`call()` accepts names from `functions`, including actions returning `void` or `Promise<void>`: callers can await completion and catch errors or timeouts. `emit()`, its deprecated alias `callEvent()`, and `on()` use the names declared in `events`. Function and event names have separate namespaces.
+`call()` accepts names from `functions`, including actions returning `void` or `Promise<void>`: callers can await completion and catch errors or timeouts. `emit()` and `on()` use the names declared in `events`. Function and event names have separate namespaces.
 
 ```ts
 import type { MyChannelProtocol } from '../shared/protocol'

docs/content/1.guide/18.hub-initiate.md

@@ -82,7 +82,7 @@ Registrations are validated fail-fast: one module per type (`DF8108`), an existi
 
 The hub's **single Auth** is one gate at the shared transport for every mounted devframe, built-ins, and the MCP route; one handshake (OTP, magic link, or pre-shared token) unlocks the namespace; `auth: false` disables it for localhost.
 
-The aggregate MCP route mounts through the `'auto'` default once any mounted devframe (or an agent-flagged hub command) exposes agent tools; `mcp: true` forces it on, `mcp: false` off. It has its own origin gate, independent of this RPC Auth: the mounted route trusts same-machine callers, and `mcp: { authorization }` adds an identity check when the hub is reachable beyond loopback. A mounted devframe's own `mcp` setting is ignored: the hub exposes one aggregate route over them all, and warns ([`DF8005`](/errors/DF8005)) when a devframe asks for MCP while the hub set `mcp: false`.
+The aggregate MCP route mounts through the `'auto'` default once any mounted devframe (or an agent-flagged hub command) exposes agent tools; `mcp: true` forces it on, `mcp: false` off. It has its own origin gate, independent of this RPC Auth: the mounted route trusts same-machine callers, and `mcp: { authorization }` adds an identity check when the hub is reachable beyond loopback. The hub exposes one aggregate route over every mounted devframe's tools.
 
 ## Singular vs hub mounting
 

docs/content/1.guide/6.client-assets.md

@@ -29,7 +29,7 @@ export default defineDevframe({
 
 devframe serves it with SPA fallback (unknown paths → `index.html`) and no-store dev caching. Build the SPA with a relative base (`vite: { base: './' }`); it reads its runtime base from `document.baseURI`.
 
-The [`dev`](/adapters/dev), [`build`](/adapters/build), and [Vite](/frameworks/vite) adapters share `clientAssets`; the deprecated `cli.distDir` is a fallback when it's unset.
+The [`dev`](/adapters/dev), [`build`](/adapters/build), and [Vite](/frameworks/vite) adapters all read `clientAssets`.
 
 ## Programmatic hosting from `setup`
 

docs/content/2.adapters/3.dev.md

@@ -27,7 +27,7 @@ Returns a `StartedServer`: origin, port, h3 app, WS server, RPC group, `close()`
 | `host` | `def.cli?.host ?? 'localhost'` | Bind host. |
 | `port` | resolved via `resolveDevServerPort` | Listen port. |
 | `flags` | `{}` | To `setup(ctx, { flags })`. |
-| `distDir` | `def.clientAssets` (falls back to deprecated `def.cli?.distDir`) | SPA dist; unset = bridge mode. |
+| `distDir` | `def.clientAssets` | SPA dist; unset = bridge mode. |
 | `basePath` | `resolveBasePath(def, 'standalone')` | Mount override. |
 | `app` | fresh h3 app | Mount onto. |
 | `openBrowser` | resolves from `flags.open` / `def.cli?.open` | `false` off; string opens a path. |

docs/content/5.add-ons/1.devframes/4.a11y.md

@@ -42,10 +42,10 @@ The hub serves the bundle same-origin and a client runtime imports it into the h
 A host can also mount the module itself, for example a Vite host via `/@fs/`:
 
 ```ts
-import createA11yDevframe, { a11yPageScriptBundlePath } from '@devframes/plugin-a11y'
+import createA11yDevframe, { a11yClientScriptBundlePath } from '@devframes/plugin-a11y'
 
 await ctx.install(createA11yDevframe(), {
-  dock: { clientScript: { importFrom: `/@fs/${a11yPageScriptBundlePath}` } },
+  dock: { clientScript: { importFrom: `/@fs/${a11yClientScriptBundlePath}` } },
 })
 ```
 

docs/content/6.errors/DF8005.md

@@ -97,7 +97,6 @@ Emitted by `@devframes/hub` while assembling and mounting the unified surface.
 | [DF8002](/errors/DF8002) | error | Both devframes and context Passed to initHub |
 | [DF8003](/errors/DF8003) | error | connectionMeta() Before Hub Instance Ready |
 | [DF8004](/errors/DF8004) | error | Devframe Id Is Not a Mountable URL Segment |
-| [DF8005](/errors/DF8005) | warning | Devframe MCP Ignored While Hub MCP Is Off |
 
 ## Hub: docks & mounting (DF81xx)
 

docs/content/6.errors/index.md

@@ -43,3 +43,21 @@ npm install @devframes/agentic
 ```
 
 Code that imported SDK types directly for devframe's MCP options no longer needs to: the full option surface is typed on `devframe/adapters/mcp` and `devframe/types` without any SDK types.
+
+## Removed deprecated APIs
+
+0.10 drops the symbols deprecated during the 0.9 line. Each has a drop-in replacement:
+
+| Removed | Use instead |
+| ------- | ----------- |
+| `cli.mcp` on a definition | Pass `mcp` to the host (`createCac` / `--mcp`, `createDevServer`, `initDevframe`, `initHub`) |
+| `cli.distDir` on a definition | Top-level `clientAssets` on the definition |
+| `resolveClientAssets` (from `devframe`) | Read `definition.clientAssets` directly |
+| `createDevframeClientHost`, `DevframeClientHost`, `DevframeClientHostOptions` (`@devframes/hub/client`) | `createDevframeClientRuntime`, `DevframeClientRuntime`, `DevframeClientRuntimeOptions` |
+| `coerceAgentPositionalArgs`, `AgentArgsFallback` (`devframe/internal`) | `toolInputToRpcArgs` / `toolInputToCommandArgs` |
+| `openInEditor`, `openInFinder`, `commonRpcFunctions` (`devframe/recipes/common-rpc-functions`) | The [`@devframes/service-open`](/add-ons/services/open) wire service |
+| `callEvent()` on an in-page channel | `emit()` |
+| `a11yPageScriptBundlePath`, `a11yAgentBundlePath` (`@devframes/plugin-a11y`) | `a11yClientScriptBundlePath` |
+| `AGENT_DISCOVERY_FILE`, `AgentDiscovery`, `DataInspectorAgent` (`@devframes/plugin-data-inspector/inject`) | `DISCOVERY_FILE`, `InjectDiscovery`, `DataInspectorEndpoint` |
+
+Dropping `cli.mcp` also removes the hub's `DF8005` warning: a hub's aggregate MCP route already covers every mounted devframe's tools, so a per-devframe MCP request no longer exists to conflict with it.

docs/content/7.migrations/1.migration-0.10.md

@@ -50,7 +50,7 @@ The values of `rpc.status`: [Handling connection and auth errors](/guide/client#
 
 The browser-only endpoint methods of the [in-page channel](/guide/in-page-channel). `emit()` sends to the opposite endpoint; `on()` handles events arriving from that endpoint.
 
-`InPageChannelProtocol` separates `functions` and `events`. Each section has optional `pageScript` and `panel` maps naming the receiving direction. Endpoint options require a complete `functions` map with handlers; `events` is optional, and when provided can include optional handlers (use `{}` to declare an event without a handler for `channel.on()`). `call()` uses function names regardless of return type, while `emit()`, `callEvent()` (deprecated), and `on()` use event names. A function returning `void` or `Promise<void>` remains an awaitable request/response call.
+`InPageChannelProtocol` separates `functions` and `events`. Each section has optional `pageScript` and `panel` maps naming the receiving direction. Endpoint options require a complete `functions` map with handlers; `events` is optional, and when provided can include optional handlers (use `{}` to declare an event without a handler for `channel.on()`). `call()` uses function names regardless of return type, while `emit()` and `on()` use event names. A function returning `void` or `Promise<void>` remains an awaitable request/response call.
 
 | Method or property | Page-script endpoint | Panel endpoint |
 |--------------------|-------------|-------|