revert(devframe): keep devframe/adapters/embedded

Restore the `devframe/adapters/embedded` entry point (`createEmbedded`) that the
0.9 surface reduction had removed — kept as a named, discoverable adapter
alongside cac/dev/build/mcp. Re-adds the export map / tsdown / alias plumbing,
the source, the docs page + nav + adapter tables, the SKILL row, and the tsnapi
snapshot, and drops the corresponding migration-0.9 note.

Co-authored-by: opencode <noreply@opencode.ai>

Author: antfubot

alias.ts

@@ -36,6 +36,7 @@ export const alias = {
   'devframe/adapters/dev': r('devframe/src/adapters/dev.ts'),
   'devframe/adapters/build': r('devframe/src/adapters/build.ts'),
   'devframe/helpers/vite': r('devframe/src/helpers/vite.ts'),
+  'devframe/adapters/embedded': r('devframe/src/adapters/embedded.ts'),
   'devframe/initiate': r('devframe/src/adapters/initiate.ts'),
   'devframe/adapters/mcp': r('devframe/src/adapters/mcp/index.ts'),
   '@devframes/hub/client': r('hub/src/client/index.ts'),

docs/.vitepress/config.ts

@@ -47,6 +47,7 @@ function adaptersItems(prefix: string) {
     { text: 'Initiate (middleware)', link: `${prefix}/adapters/initiate` },
     { text: 'Build', link: `${prefix}/adapters/build` },
     { text: 'Vite', link: `${prefix}/adapters/vite` },
+    { text: 'Embedded', link: `${prefix}/adapters/embedded` },
     { text: 'MCP', link: `${prefix}/adapters/mcp` },
   ] satisfies DefaultTheme.NavItemWithLink[]
 }

docs/adapters/embedded.md

@@ -0,0 +1,20 @@
+---
+outline: deep
+---
+
+# Embedded
+
+Register a devframe into an already-running context at runtime. Mirrors the [`vite`](./vite) adapter's plugin-scan, but for callers that need dynamic, post-startup registration. The host decides the mount path; `embedded` is a hosted adapter and inherits the `/__<id>/` default when one is needed.
+
+```ts
+import { createEmbedded } from 'devframe/adapters/embedded'
+import devframe from './devframe'
+
+await createEmbedded(devframe, { ctx: existingCtx })
+```
+
+| Option | Required | Description |
+|--------|----------|-------------|
+| `ctx` | ✓ | Target `DevframeNodeContext` the devframe is registered into. |
+
+Useful when a host loads devframes based on runtime conditions (feature flags, user opt-in, dynamic discovery) rather than static config.

docs/adapters/index.md

@@ -4,7 +4,7 @@ outline: deep
 
 # Adapters
 
-An adapter takes a `DevframeDefinition` and deploys it into a specific runtime — a standalone CLI, a Vite plugin, a static snapshot, or an MCP server. Each adapter ships at its own entry point (`devframe/adapters/<name>`); the bundler pulls in only the ones you use. To register a definition into an already-running host, call its `setup` directly: `await def.setup(ctx)`.
+An adapter takes a `DevframeDefinition` and deploys it into a specific runtime — a standalone CLI, a Vite plugin, a static snapshot, an embedded host, or an MCP server. Each adapter ships at its own entry point (`devframe/adapters/<name>`); the bundler pulls in only the ones you use.
 
 Every adapter factory has the shape `createXxx(devframeDef, options?)`. Some adapters draw on an optional peer dependency, installed only when you opt into that adapter: `cac` pulls in [`cac`](https://github.com/cacjs/cac), and `mcp` pulls in [`@modelcontextprotocol/server`](https://github.com/modelcontextprotocol/typescript-sdk).
 
@@ -16,6 +16,7 @@ Every adapter factory has the shape `createXxx(devframeDef, options?)`. Some ada
 | [`dev`](./dev) | `devframe/adapters/dev` | `createDevServer(def, options?)` | Run the dev server programmatically — drive it from any CLI framework |
 | [`build`](./build) | `devframe/adapters/build` | `createBuild(def, options?)` | Offline reports, CI artifacts, deployable SPA snapshots |
 | [`vite`](./vite) | `@vitejs/devtools-kit/node` | `createPluginFromDevframe(def, options?)` | Mount the definition into Vite DevTools (or any compatible host) |
+| [`embedded`](./embedded) | `devframe/adapters/embedded` | `createEmbedded(def, { ctx })` | Runtime registration into an already-running host |
 | [`mcp`](./mcp) | `devframe/adapters/mcp` | `createMcpServer(def, options?)` | Exposing a devframe to coding agents |
 
 ## Mount paths
@@ -25,7 +26,7 @@ A devframe's SPA basePath depends on which adapter is running it:
 | Adapter kind | Default basePath | Reason |
 |--------------|------------------|--------|
 | `cli`, `spa`, `build` (standalone) | `/` | The devframe owns the origin. |
-| `vite`, embedding hosts (hosted) | `/__<id>/` | The devframe shares the origin with a host app and namespaces itself. |
+| `vite`, `embedded` (hosted) | `/__<id>/` | The devframe shares the origin with a host app and namespaces itself. |
 
 Override either side explicitly with `DevframeDefinition.basePath`:
 

docs/guide/index.md

@@ -15,7 +15,7 @@ Devframe keeps its surface focused on one tool, so the same definition stays por
 - **One tool per definition.** A devframe describes a single integration. Deploy it through any adapter; host-level features that only matter when several tools share a UI (palettes, cross-tool toasts, unified terminals) come from whichever host you mount into — Vite DevTools is one example.
 - **Headless.** Hook into `onReady`, `cli.configure`, and friends to print your own startup banners and styling — Devframe stays out of the way.
 - **App-owned file watching.** Wire your own watcher (chokidar, fs.watch, …) and signal change via `ctx.rpc.sharedState.set(...)` or event-typed RPCs.
-- **Context-aware mount paths.** Standalone adapters (`cli`, `spa`, `build`) serve at `/` by default; hosted contexts (`vite`, or a host that calls `setup`) serve at `/.<id>/`. Override via `DevframeDefinition.basePath`.
+- **Context-aware mount paths.** Standalone adapters (`cli`, `spa`, `build`) serve at `/` by default; hosted adapters (`vite`, `embedded`) serve at `/.<id>/`. Override via `DevframeDefinition.basePath`.
 - **SPAs own their base at runtime.** Build with relative asset paths (`vite.base: './'`); `connectDevframe` discovers the effective base from the executing script's location.
 - **CLI flags compose.** The `cac` instance is exposed to both the devframe (`cli.configure`) and the caller of `createCac`, so capability flags and app flags merge cleanly.
 
@@ -84,7 +84,7 @@ node ./my-devframe.js build  # self-contained static deploy in dist-static/
 node ./my-devframe.js mcp    # stdio MCP server (experimental)
 ```
 
-The CLI adapter serves the SPA at `/` by default. When the same devframe is embedded inside a host (`vite`, or a host that calls `setup`), the default becomes `/.my-devframe/`. Override either side via `defineDevframe({ basePath })`.
+The CLI adapter serves the SPA at `/` by default. When the same devframe is embedded inside a host (`vite`, `embedded`), the default becomes `/.my-devframe/`. Override either side via `defineDevframe({ basePath })`.
 
 ## Adapters at a glance
 
@@ -95,10 +95,9 @@ Devframe deploys the same `DevframeDefinition` through one of these adapters:
 | `cli` | `createCac(d).parse()` | Standalone CLI with dev / build / mcp subcommands |
 | `vite` | `createPluginFromDevframe(d, opts?)` *(from `@vitejs/devtools-kit/node`)* | Mount the devframe into Vite DevTools (or another compatible host) |
 | `build` | `createBuild(d, opts?)` | Self-contained static deploy with baked RPC dumps |
+| `embedded` | `createEmbedded(d, { ctx })` | Runtime registration into an existing host |
 | `mcp` | `createMcpServer(d, opts)` | Model Context Protocol server |
 
-To register a definition into an already-running host, call `await d.setup(ctx)` directly.
-
 See [Adapters](/adapters/) for the full reference.
 
 ## Framework- and build-tool-agnostic

docs/guide/migration-0.9.md

@@ -114,24 +114,6 @@ import { defineDevframe, defineRpcFunction } from 'devframe'
 
 `devframe/types` still resolves as the type-only subpath — useful for `declare module 'devframe/types'` augmentations — but `devframe` is the canonical import for both values and types.
 
-## `devframe/adapters/embedded` is removed
-
-`createEmbedded(def, { ctx })` was a one-line wrapper around the definition's own `setup`. Call `setup` directly to register a devframe into an already-running host context:
-
-```ts
-// 0.8.x
-import { createEmbedded } from 'devframe/adapters/embedded'
-
-await createEmbedded(def, { ctx })
-```
-
-```ts
-// 0.9
-await def.setup(ctx)
-```
-
-In a hub, `mountDevframe(ctx, def)` (from `@devframes/hub/node`) remains the way to register a devframe with the hub's dock/command wiring.
-
 ## `devframe/utils/{hash,promise,scope}` are removed
 
 Three utility subpaths with no integration consumers are removed:

packages/devframe/package.json

@@ -23,6 +23,7 @@
     "./adapters/build": "./dist/adapters/build.mjs",
     "./adapters/cac": "./dist/adapters/cac.mjs",
     "./adapters/dev": "./dist/adapters/dev.mjs",
+    "./adapters/embedded": "./dist/adapters/embedded.mjs",
     "./adapters/mcp": "./dist/adapters/mcp.mjs",
     "./client": "./dist/client/index.mjs",
     "./constants": "./dist/constants.mjs",

packages/devframe/src/adapters/embedded.ts

@@ -0,0 +1,20 @@
+import type { DevframeNodeContext } from '../types/context'
+import type { DevframeDefinition } from '../types/devframe'
+
+export interface CreateEmbeddedOptions {
+  /** Target context the devframe is registered into. Required. */
+  ctx: DevframeNodeContext
+}
+
+/**
+ * Register a devframe into an already-running devframe/Kit context at
+ * runtime. Mirrors what the Vite plugin scan does for devframes passed
+ * as plugin options, but exposes the same flow to callers that need
+ * dynamic, post-startup registration.
+ *
+ * The host owns the mount path; when a hosted mount is needed the
+ * effective default follows the hosted rule of `def.basePath ?? '/__<id>/'`.
+ */
+export async function createEmbedded(d: DevframeDefinition, options: CreateEmbeddedOptions): Promise<void> {
+  await d.setup(options.ctx)
+}

packages/devframe/tsdown.config.ts

@@ -102,6 +102,7 @@ const serverEntries = {
   'adapters/cac': 'src/adapters/cac.ts',
   'adapters/dev': 'src/adapters/dev.ts',
   'adapters/build': 'src/adapters/build.ts',
+  'adapters/embedded': 'src/adapters/embedded.ts',
   'adapters/initiate': 'src/adapters/initiate.ts',
   'adapters/mcp': 'src/adapters/mcp/index.ts',
   'cli/main': 'src/cli/main.ts',

plans/032-0.9-public-api-surface-reduction.md

@@ -67,7 +67,7 @@ guide).
 | `devframe/node/auth` | **Keep public** (low-level auth layer). |
 | `devframe/rpc/client` + `rpc/transports/ws-client` | **Keep both**, document as the low-level / test client. |
 | `devframe/rpc/server` + `rpc/transports/ws-server` | **Keep** (hand-rolled-server hosts use them). |
-| `devframe/adapters/embedded` | **Remove** (one-liner `d.setup(ctx)`). |
+| `devframe/adapters/embedded` | **Kept** (maintainer request — named, discoverable adapter for symmetry). |
 | `devframe/rpc/transports/ws-bun` | **Remove** (zero refs). |
 | `devframe/utils/hash`, `utils/promise`, `utils/scope` | **Remove** (zero refs). |
 | `devframe/utils/structured-clone` | **Keep**. |
@@ -90,9 +90,10 @@ consumer):
   hand-rolled-server host the ⚠️ note below anticipated. **Kept** (resolves the
   open question: keep it).
 
-Net effect: dead-subpath removals are `embedded`, `utils/hash`, `utils/promise`,
+Net effect: dead-subpath removals are `utils/hash`, `utils/promise`, and
 `utils/scope` (not `ws-bun`); the `devframe/node` trim drops **9** internal
-exports, not 12.
+exports, not 12. `devframe/adapters/embedded` was initially removed but restored
+on maintainer request — it stays as a named, discoverable adapter.
 
 ### ⚠️ One item to confirm during review