devframe 0.9.9 → 0.9.10

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "devframe",
   "type": "module",
-  "version": "0.9.9",
+  "version": "0.9.10",
   "description": "Framework for building one portable devtool integration that runs in any viewer.",
   "author": "Anthony Fu <anthonyfu117@hotmail.com>",
   "license": "MIT",
@@ -77,21 +77,18 @@
   ],
   "peerDependencies": {
     "@modelcontextprotocol/client": "^2.0.0",
-    "@modelcontextprotocol/server": "^2.0.0",
     "cac": "^7.0.0"
   },
   "peerDependenciesMeta": {
     "@modelcontextprotocol/client": {
       "optional": true
     },
-    "@modelcontextprotocol/server": {
-      "optional": true
-    },
     "cac": {
       "optional": true
     }
   },
   "dependencies": {
+    "@modelcontextprotocol/server": "^2.0.0",
     "@standard-schema/spec": "^1.1.0",
     "birpc": "^4.2.0",
     "crossws": "^0.4.12",
@@ -103,7 +100,6 @@
   },
   "devDependencies": {
     "@modelcontextprotocol/client": "^2.0.0",
-    "@modelcontextprotocol/server": "^2.0.0",
     "cac": "^7.0.0",
     "get-port-please": "^3.2.0",
     "immer": "^11.1.18",

package/skills/devframe/SKILL.md

@@ -405,7 +405,9 @@ defineRpcFunction({
 })
 ```
 
-Or register tools / resources directly on `ctx.agent.registerTool({ id, description, safety, handler })` and `ctx.agent.registerResource({ id, name, mimeType, read })`. Expose the API over MCP:
+Or register tools / resources directly on `ctx.agent.registerTool({ id, description, safety, handler })` and `ctx.agent.registerResource({ id, name, mimeType, read })`.
+
+The dev server serves this surface over HTTP automatically: the `mcp: 'auto'` default mounts the Streamable-HTTP route at `<base>__mcp` once the agent surface is non-empty (`mcp: true` forces on, `mcp: false` off). For stdio:
 
 ```ts
 import { createMcpServer } from 'devframe/adapters/mcp'
@@ -413,7 +415,7 @@ import { createMcpServer } from 'devframe/adapters/mcp'
 await createMcpServer(myDevframe, { transport: 'stdio' })
 ```
 
-`@modelcontextprotocol/server` is a peer dependency. The CLI adapter also exposes `my-tool mcp` (route node-side logs to stderr - stdout is the transport). Safety classifications (`'read' | 'action' | 'destructive'`) drive MCP hint annotations that coding agents use to prompt for confirmation. In a hub, `ctx.commands` entries opt into the same agent-facing API with an `agent` field and reach MCP through the aggregate endpoint.
+The CLI adapter also exposes `my-tool mcp` (route node-side logs to stderr - stdout is the transport). Safety classifications (`'read' | 'action' | 'destructive'`) drive MCP hint annotations that coding agents use to prompt for confirmation. In a hub, `ctx.commands` entries opt into the same agent-facing API with an `agent` field and reach MCP through the aggregate endpoint.
 
 ## Author SPA
 
@@ -508,7 +510,7 @@ Plus broadcasts (`devframe:docks:activate`, `devframe:terminals:updated`, `devfr
 
 The hub is headless; `DevframeHubUi` is pure data (`viewer` / `embedded` / `assets` / `setup`). `@devframes/hub-ui`'s `createUi()` is the reference hub UI provider - a standalone devtools page plus a floating dock injected via one `<script type="module" src="/__devframes/embedded.js">` tag. It takes `branding`, `dockPreferences`, and `embeddedVisibility` (`'normal'` / `'passive'` / `'hidden'`). Another hub UI provider supplies a different object to the same slot and reuses all the infrastructure. Renderer modules for opt-in dock types compose at the hub via `initHub({ renderers })`.
 
-Two copyable reference hubs mount every built-in devframe behind an icon dock rail - the shape Vite DevTools wears, shrunk to the smallest thing you can build your own hub UI provider from: [`examples/hub-vite/`](https://github.com/devframes/devframe/tree/main/examples/hub-vite) (~120-line Vite host, vanilla DOM UI) and [`examples/hub-next/`](https://github.com/devframes/devframe/tree/main/examples/hub-next) (Next.js App Router). The `hub-*-minimal` family shows the default `createUi()` mount across Vite, Next, Nitro, Hono, Fastify, SvelteKit, Deno, and Rsbuild.
+Two copyable reference hubs mount every built-in devframe behind an icon dock rail - the shape Vite DevTools wears, shrunk to the smallest thing you can build your own hub UI provider from: [`examples/custom-hub-vite/`](https://github.com/devframes/devframe/tree/main/examples/custom-hub-vite) (~120-line Vite host, vanilla DOM UI) and [`examples/custom-hub-next/`](https://github.com/devframes/devframe/tree/main/examples/custom-hub-next) (Next.js App Router). The `hub-*` family (`hub-vite`, `hub-next`, `hub-deno`, `hub-fastify`, `hub-hono`, `hub-nitro`, `hub-rsbuild`, `hub-sveltekit`) shows the default `createUi()` mount across Vite, Next, Nitro, Hono, Fastify, SvelteKit, Deno, and Rsbuild.
 
 ## Framework kits: two scopes
 

package/dist/diagnostics-D0EVm5M6.mjs

@@ -1,39 +0,0 @@
-import { i as defineDiagnostics } from "./nostics-D0PvLZsn.mjs";
-//#region src/rpc/diagnostics.ts
-const diagnostics = defineDiagnostics({
-	docsBase: "https://devfra.me/errors",
-	codes: {
-		DF0019: {
-			why: (p) => `RPC function "${p.name}" has \`agent\` set but \`jsonSerializable\` is not \`true\`; MCP requires JSON-serializable data.`,
-			fix: "Set `jsonSerializable: true` if the payload is JSON-safe, or remove `agent` to keep it RPC-only."
-		},
-		DF0020: {
-			why: (p) => `RPC function "${p.name}" declares \`jsonSerializable: true\` but the value at "${p.path}" is a ${p.type}.`,
-			fix: "Either drop `jsonSerializable: true` (falls back to structured-clone) or change the value to a JSON-safe shape."
-		},
-		DF0021: {
-			why: (p) => `RPC function "${p.name}" is already registered`,
-			fix: "Use the `force` parameter to overwrite an existing registration."
-		},
-		DF0022: { why: (p) => `RPC function "${p.name}" is not registered. Use register() to add new functions.` },
-		DF0023: { why: (p) => `RPC function "${p.name}" is not registered` },
-		DF0024: { why: (p) => `Either handler or setup function must be provided for RPC function "${p.name}"` },
-		DF0025: { why: (p) => `Function "${p.name}" not found in dump store` },
-		DF0026: { why: (p) => `No dump match for "${p.name}" with args: ${p.args}` },
-		DF0027: { why: (p) => `Function "${p.name}" with type "${p.type}" cannot have dump configuration. Only "static" and "query" types support dumps.` },
-		DF0028: {
-			why: (p) => `Function "${p.name}" with type "${p.type}" cannot use \`snapshot: true\`. Only "query" functions support this sugar; "static" functions have equivalent default behavior already.`,
-			fix: "Remove `snapshot: true`, or change the function type to `query`."
-		},
-		DF0043: {
-			why: (p) => `RPC function "${p.name}" received an invalid argument at position ${p.index}: ${p.issues}`,
-			fix: "Pass a value that satisfies the `args` schema declared for this function."
-		},
-		DF0044: {
-			why: (p) => `RPC function "${p.name}" returned a value that failed its \`returns\` schema: ${p.issues}`,
-			fix: "Make the handler return a value that satisfies the `returns` schema, or relax the schema."
-		}
-	}
-});
-//#endregion
-export { diagnostics as t };

package/dist/{host-h3-BJ4siyz7.mjs → host-h3-BROI6SQ4.mjs}

@@ -1,5 +1,5 @@
-import process from "node:process";
 import { join } from "pathe";
+import process from "node:process";
 import { homedir } from "node:os";
 //#region src/node/host-h3.ts
 /**