chore: rename minimal-* example dirs, reorganize docs nav

Rename examples/minimal-next-devframe-hub -> examples/next-devframe-hub,
examples/minimal-vite-devframe-hub -> examples/vite-devframe-hub, and
examples/minimal-json-render -> examples/json-render, updating every
package name, identifier, workspace path, and doc link tied to the old
names.

Restructure the docs top nav: Plugins gets its own dedicated dropdown,
Helpers moves under Adapters, and Examples moves under Guide.

Author: antfubot

AGENTS.md

@@ -4,7 +4,7 @@
 
 **`devframe`** is the framework-neutral container for one devtool integration, portable across viewers. Build a single tool (its RPC, its SPA, its diagnostics, its CLI/build/spa/embedded outputs) without caring how it'll be displayed. A devframe app runs standalone (CLI, static deploy, embedded SPA) just as well as it mounts inside a hub.
 
-**`@devframes/hub`** is the framework-neutral hub layer that sits on top of devframe and provides the multi-integration orchestration (docks, terminals, messages, commands). It does not ship UI — implementers (e.g. `@vitejs/devtools-kit`) provide their own UI on top of the hub's RPC + shared-state protocol. It does ship a **headless client runtime** (`createDevframeClientHost()` from `@devframes/hub/client`): booted in the host page, it assembles the shared `DevframeClientContext` (panel, docks, commands, when) and imports each dock entry's client script (`action` / `custom-render` / iframe `clientScript`) into that page — how a plugin like the a11y inspector runs code inside the page being inspected. See `examples/minimal-vite-devframe-hub/` for a working ~120-line Vite host demonstrating the protocol end to end.
+**`@devframes/hub`** is the framework-neutral hub layer that sits on top of devframe and provides the multi-integration orchestration (docks, terminals, messages, commands). It does not ship UI — implementers (e.g. `@vitejs/devtools-kit`) provide their own UI on top of the hub's RPC + shared-state protocol. It does ship a **headless client runtime** (`createDevframeClientHost()` from `@devframes/hub/client`): booted in the host page, it assembles the shared `DevframeClientContext` (panel, docks, commands, when) and imports each dock entry's client script (`action` / `custom-render` / iframe `clientScript`) into that page — how a plugin like the a11y inspector runs code inside the page being inspected. See `examples/vite-devframe-hub/` for a working ~120-line Vite host demonstrating the protocol end to end.
 
 ## Stack & Structure
 

alias.ts

@@ -55,7 +55,7 @@ export const alias = {
   '@devframes/json-render-ui/components': r('json-render-ui/src/components/index.ts'),
   '@devframes/json-render-ui/spa': r('json-render-ui/src/spa.ts'),
   '@devframes/json-render-ui': r('json-render-ui/src/index.ts'),
-  'minimal-json-render/dashboard': fileURLToPath(new URL('./examples/minimal-json-render/src/dashboard.ts', import.meta.url)),
+  'json-render/dashboard': fileURLToPath(new URL('./examples/json-render/src/dashboard.ts', import.meta.url)),
   '@devframes/plugin-code-server/client': p('code-server/src/client/index.ts'),
   '@devframes/plugin-code-server/node': p('code-server/src/node/index.ts'),
   '@devframes/plugin-code-server/constants': p('code-server/src/constants.ts'),

docs/.vitepress/config.ts

@@ -79,11 +79,11 @@ function examplesItems(prefix: string) {
     { text: 'Overview', link: `${prefix}/examples/` },
     { text: 'Built with Devframe', link: `${prefix}/examples/built-with` },
     { text: 'files-inspector', link: `${prefix}/examples/files-inspector` },
-    { text: 'minimal-json-render', link: `${prefix}/examples/minimal-json-render` },
+    { text: 'json-render', link: `${prefix}/examples/json-render` },
     { text: 'streaming-chat', link: `${prefix}/examples/streaming-chat` },
     { text: 'next-runtime-snapshot', link: `${prefix}/examples/next-runtime-snapshot` },
-    { text: 'minimal-vite-devframe-hub', link: `${prefix}/examples/minimal-vite-devframe-hub` },
-    { text: 'minimal-next-devframe-hub', link: `${prefix}/examples/minimal-next-devframe-hub` },
+    { text: 'vite-devframe-hub', link: `${prefix}/examples/vite-devframe-hub` },
+    { text: 'next-devframe-hub', link: `${prefix}/examples/next-devframe-hub` },
   ] satisfies DefaultTheme.NavItemWithLink[]
 }
 
@@ -114,17 +114,21 @@ export function devframeSidebar(prefix = ''): DefaultTheme.SidebarItem[] {
 
 export function devframeNav(prefix = ''): DefaultTheme.NavItem[] {
   return [
-    { text: 'Guide', items: guideItems(prefix) },
-    { text: 'Adapters', items: adaptersItems(prefix) },
     {
-      text: 'Resources',
+      text: 'Guide',
+      items: [
+        ...guideItems(prefix),
+        { text: 'Examples', items: examplesItems(prefix) },
+      ],
+    },
+    {
+      text: 'Adapters',
       items: [
-        { text: 'Examples', link: `${prefix}/examples/` },
-        { text: 'Built with Devframe', link: `${prefix}/examples/built-with` },
+        ...adaptersItems(prefix),
         { text: 'Helpers', items: helpersItems(prefix) },
-        { text: 'Plugins', items: pluginsItems(prefix) },
       ],
     },
+    { text: 'Plugins', items: pluginsItems(prefix) },
     { text: 'Errors', link: `${prefix}/errors/` },
     {
       text: `v${pkg.version}`,

docs/examples/index.md

@@ -9,11 +9,11 @@ End-to-end examples that exercise the full adapter surface, each a runnable app
 | Example | UI framework | What it shows |
 |---------|--------------|---------------|
 | [files-inspector](./files-inspector) | Preact | Lists files in the cwd via RPC; exercises the CLI dev / build / spa surfaces. |
-| [minimal-json-render](./minimal-json-render) | Vue | A server-authored JSON-render view rendered by `@devframes/json-render-ui`, with live state and an action bridge. |
+| [json-render](./json-render) | Vue | A server-authored JSON-render view rendered by `@devframes/json-render-ui`, with live state and an action bridge. |
 | [streaming-chat](./streaming-chat) | Preact | Streams synthetic chat tokens server → client, with history kept in shared state. |
 | [next-runtime-snapshot](./next-runtime-snapshot) | React (Next.js) | A Next.js App Router SPA over RPC, surfacing the host Node runtime. |
-| [minimal-vite-devframe-hub](./minimal-vite-devframe-hub) | Vanilla TypeScript (Vite) | A ~120-line Vite host wiring `@devframes/hub` end to end. |
-| [minimal-next-devframe-hub](./minimal-next-devframe-hub) | React (Next.js) | The same hub protocol, hosted from a Next.js route handler. |
+| [vite-devframe-hub](./vite-devframe-hub) | Vanilla TypeScript (Vite) | A ~120-line Vite host wiring `@devframes/hub` end to end. |
+| [next-devframe-hub](./next-devframe-hub) | React (Next.js) | The same hub protocol, hosted from a Next.js route handler. |
 
 ## Run any example
 

docs/examples/minimal-json-render.md docs/examples/json-render.mddocs/examples/minimal-json-render.md renamed to docs/examples/json-render.md

@@ -2,13 +2,13 @@
 outline: deep
 ---
 
-# minimal-json-render
+# json-render
 
 A standalone devframe that serves a **JSON-render view**: the server authors an
 `@json-render/core` spec once, and the prebuilt `@devframes/json-render-ui` SPA
 renders it — the app ships no client build of its own.
 
-Package: `minimal-json-render` · frontend: **prebuilt `@devframes/json-render-ui/spa`**
+Package: `json-render` · frontend: **prebuilt `@devframes/json-render-ui/spa`**
 
 ## What it shows
 
@@ -29,12 +29,12 @@ Package: `minimal-json-render` · frontend: **prebuilt `@devframes/json-render-u
 ## Run it
 
 ```sh
-pnpm --filter minimal-json-render dev         # CLI dev server (live RPC)
-pnpm --filter minimal-json-render cli:build   # static deploy → dist/static
+pnpm --filter json-render dev         # CLI dev server (live RPC)
+pnpm --filter json-render cli:build   # static deploy → dist/static
 ```
 
-The dev server serves the SPA at `/__minimal-json-render/`.
+The dev server serves the SPA at `/__json-render/`.
 
 ## Source
 
-[`examples/minimal-json-render`](https://github.com/devframes/devframe/tree/main/examples/minimal-json-render)
+[`examples/json-render`](https://github.com/devframes/devframe/tree/main/examples/json-render)

…cs/examples/minimal-next-devframe-hub.md docs/examples/next-devframe-hub.mddocs/examples/minimal-next-devframe-hub.md renamed to docs/examples/next-devframe-hub.md docs/examples/minimal-next-devframe-hub.md renamed to docs/examples/next-devframe-hub.md

@@ -2,11 +2,11 @@
 outline: deep
 ---
 
-# minimal-next-devframe-hub
+# next-devframe-hub
 
-The same hub protocol as the [Vite host](./minimal-vite-devframe-hub), hosted from a **Next.js** App Router app. It wires [`@devframes/hub`](/guide/hub) by lazily starting a side-car RPC / WebSocket server from a Node route handler — proof that the hub is host-runtime-agnostic.
+The same hub protocol as the [Vite host](./vite-devframe-hub), hosted from a **Next.js** App Router app. It wires [`@devframes/hub`](/guide/hub) by lazily starting a side-car RPC / WebSocket server from a Node route handler — proof that the hub is host-runtime-agnostic.
 
-Package: `minimal-next-devframe-hub` · framework: **React (Next.js)**
+Package: `next-devframe-hub` · framework: **React (Next.js)**
 
 ## What it proves
 
@@ -22,7 +22,7 @@ Package: `minimal-next-devframe-hub` · framework: **React (Next.js)**
 
 ```sh
 pnpm install
-pnpm --filter minimal-next-devframe-hub dev
+pnpm --filter next-devframe-hub dev
 ```
 
 Open the printed URL to see the docks, commands, messages, and terminals lists, plus a button that dispatches a sample command through `hub:commands:execute`.
@@ -33,4 +33,4 @@ Open the printed URL to see the docks, commands, messages, and terminals lists,
 
 ## Source
 
-[`examples/minimal-next-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/minimal-next-devframe-hub)
+[`examples/next-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/next-devframe-hub)

…cs/examples/minimal-vite-devframe-hub.md docs/examples/vite-devframe-hub.mddocs/examples/minimal-vite-devframe-hub.md renamed to docs/examples/vite-devframe-hub.md docs/examples/minimal-vite-devframe-hub.md renamed to docs/examples/vite-devframe-hub.md

@@ -2,11 +2,11 @@
 outline: deep
 ---
 
-# minimal-vite-devframe-hub
+# vite-devframe-hub
 
 A protocol-witness host: roughly 120 lines of Vite plugin code that wire [`@devframes/hub`](/guide/hub) into a Vite dev server. The browser UI is plain **vanilla TypeScript**, so nothing distracts from the hub protocol itself. Every framework's hub host follows the same shape.
 
-Package: `minimal-vite-devframe-hub` · framework: **Vanilla TypeScript (Vite)**
+Package: `vite-devframe-hub` · framework: **Vanilla TypeScript (Vite)**
 
 ## What it proves
 
@@ -22,11 +22,11 @@ Package: `minimal-vite-devframe-hub` · framework: **Vanilla TypeScript (Vite)**
 
 ```sh
 pnpm install
-pnpm --filter minimal-vite-devframe-hub dev
+pnpm --filter vite-devframe-hub dev
 ```
 
 Open the printed URL to see the docks, commands, messages, and terminals lists the hub exposes, plus a button that dispatches a sample command through `hub:commands:execute`.
 
 ## Source
 
-[`examples/minimal-vite-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/minimal-vite-devframe-hub)
+[`examples/vite-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/vite-devframe-hub)

docs/guide/client-context.md

@@ -186,4 +186,4 @@ state.domElements.iframe = iframeEl
 state.events.emit('dom:iframe:mounted', iframeEl)
 ```
 
-That announcement is what the adapter attaches to. Both minimal hubs wire this end to end — see the "Tabbed Tool" in [`examples/minimal-vite-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/minimal-vite-devframe-hub) and [`examples/minimal-next-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/minimal-next-devframe-hub), including the SPA's `postMessage` shim.
+That announcement is what the adapter attaches to. Both minimal hubs wire this end to end — see the "Tabbed Tool" in [`examples/vite-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/vite-devframe-hub) and [`examples/next-devframe-hub`](https://github.com/devframes/devframe/tree/main/examples/next-devframe-hub), including the SPA's `postMessage` shim.

docs/guide/hub.md

@@ -152,7 +152,7 @@ Each mounted SPA is served at `/__<id>/` and references its assets relatively (`
 export default { skipTrailingSlashRedirect: true }
 ```
 
-[`examples/minimal-next-devframe-hub/`](https://github.com/devframes/devframe/tree/main/examples/minimal-next-devframe-hub) is a working Next.js App Router host that mounts the built-in plugins this way.
+[`examples/next-devframe-hub/`](https://github.com/devframes/devframe/tree/main/examples/next-devframe-hub) is a working Next.js App Router host that mounts the built-in plugins this way.
 
 ### Duplicate devframes
 
@@ -260,8 +260,8 @@ The hub also ships a headless browser runtime, `createDevframeClientHost()` from
 
 Two minimal, copyable hubs mount every built-in plugin (git, terminals, code-server, inspect, a11y) behind an icon dock — the same shape [vite-devtools](https://github.com/vitejs/devtools) wears as the full Vite viewer, shrunk to the smallest thing you can build your own viewer from:
 
-- [`examples/minimal-vite-devframe-hub/`](https://github.com/devframes/devframe/tree/main/examples/minimal-vite-devframe-hub) — a ~120-line Vite plugin host with a vanilla DOM UI.
-- [`examples/minimal-next-devframe-hub/`](https://github.com/devframes/devframe/tree/main/examples/minimal-next-devframe-hub) — the same protocol hosted from a Next.js App Router app.
+- [`examples/vite-devframe-hub/`](https://github.com/devframes/devframe/tree/main/examples/vite-devframe-hub) — a ~120-line Vite plugin host with a vanilla DOM UI.
+- [`examples/next-devframe-hub/`](https://github.com/devframes/devframe/tree/main/examples/next-devframe-hub) — the same protocol hosted from a Next.js App Router app.
 
 Both also mount a "Tabbed Tool" that demonstrates [shared-iframe soft navigation](./client-context#shared-iframe-soft-navigation) — one SPA whose tabs surface as separate docks sharing a single iframe.
 

docs/guide/json-render.md

@@ -211,8 +211,8 @@ the browser and render it with no shared state at all (see [client-only
 docks](./client-context#client-only-docks)). The client host disposes the
 renderer when the dock deactivates.
 
-Both hub example shells dogfood this end to end: the [Vite hub](/examples/minimal-vite-devframe-hub)
-registers `@devframes/json-render-ui` (Vue), and the [Next hub](/examples/minimal-next-devframe-hub)
+Both hub example shells dogfood this end to end: the [Vite hub](/examples/vite-devframe-hub)
+registers `@devframes/json-render-ui` (Vue), and the [Next hub](/examples/next-devframe-hub)
 registers a small in-example React registry — the same dock, two frontends.
 
 ## Swapping the frontend
@@ -228,5 +228,5 @@ placeholder — showing the component type and a gist of its prop keys (`{ label
 onPress }`) — and logs a `console.warn`, while the rest of the view renders
 normally.
 
-See the [`minimal-json-render` example](/examples/minimal-json-render) for a
+See the [`json-render` example](/examples/json-render) for a
 runnable end-to-end app.