@xmachines/docs 1.0.0-beta.55 → 1.0.0-beta.57

package/examples/@xmachines/play-vue-demo/README.md

@@ -19,11 +19,11 @@ Vue 3 renderer demo for [`@xmachines/play-vue`](../../../api/@xmachines/play-vue
 From the repository root:
 
 ```bash
-npm install
-npm run dev -w @xmachines/play-vue-demo
+pnpm install
+pnpm --filter @xmachines/play-vue-demo run dev
 ```
 
-Then open `http://localhost:5173`.
+Then open `http://localhost:3004`.
 
 ## Step-by-Step Code Flow
 
@@ -53,7 +53,7 @@ app.mount("#app");
 <!-- src/App.vue -->
 <script setup lang="ts">
 import type { ComponentsMap } from "@xmachines/play-vue";
-import type { ActionFn } from "@json-render/vue";
+import type { ActionFn } from "@xmachines/json-render-vue";
 
 const typedActor = assertNonNullable(inject<AuthActor>("actor"), "actor");
 
@@ -115,7 +115,7 @@ const registryResult = computed(() =>
 
 - `src/main.ts` - actor creation/start and Vue app mount with actor injection
 - `src/App.vue` - typed `ComponentsMap` declaration, registry construction, and `PlayUIProvider` + `PlayRenderer` composition
-- `src/catalog.ts` - `authCatalog` built via `defineCatalog` with the `@json-render/vue` schema
+- `src/catalog.ts` - `authCatalog` built via `defineCatalog` with the `@xmachines/json-render-vue` schema
 - `src/components/` - demo view components bound to catalog component keys (Home, Login, Dashboard, Profile, etc.)
 - `src/index.ts` - re-exports all components and catalog for library-pattern testing
 - `test/library-pattern.test.ts` - architecture boundary and invariant assertions
@@ -149,21 +149,21 @@ Watcher notifications are one-shot. Cleanup is explicit: `actor.stop()` is calle
 
 These commands are defined in `package.json`:
 
-| Command                                            | Description                      |
-| -------------------------------------------------- | -------------------------------- |
-| `npm run dev -w @xmachines/play-vue-demo`          | Start Vite dev server            |
-| `npm run build -w @xmachines/play-vue-demo`        | Build production bundle          |
-| `npm run preview -w @xmachines/play-vue-demo`      | Preview built bundle             |
-| `npm run test -w @xmachines/play-vue-demo`         | Run Vitest test suite            |
-| `npm run test:browser -w @xmachines/play-vue-demo` | Run browser-focused Vitest suite |
+| Command                                                   | Description                                    |
+| --------------------------------------------------------- | ---------------------------------------------- |
+| `pnpm --filter @xmachines/play-vue-demo run dev`          | Start Vite dev server (http://localhost:3004/) |
+| `pnpm --filter @xmachines/play-vue-demo run build`        | Build production bundle                        |
+| `pnpm --filter @xmachines/play-vue-demo run preview`      | Preview built bundle                           |
+| `pnpm --filter @xmachines/play-vue-demo run test`         | Run Vitest test suite                          |
+| `pnpm --filter @xmachines/play-vue-demo run test:browser` | Run browser-focused Vitest suite               |
 
 ## Verification
 
 Use these checks to validate README claims against the current demo implementation:
 
 ```bash
-npm run test -w @xmachines/play-vue-demo
-npm run test:browser -w @xmachines/play-vue-demo
+pnpm --filter @xmachines/play-vue-demo run test
+pnpm --filter @xmachines/play-vue-demo run test:browser
 ```
 
 Expected result: library-pattern invariant tests pass and the browser renderer suite completes.

package/examples/@xmachines/play-vue-demo/type-aliases/AuthCatalog.md

@@ -6,4 +6,4 @@
 type AuthCatalog = typeof authCatalog;
 ```
 
-Defined in: [packages/play-vue/examples/demo/src/catalog.ts:6](https://gitlab.com/xmachin-es/xmachines-js/-/blob/v1.0.0-beta.55/packages/play-vue/examples/demo/src/catalog.ts#L6)
+Defined in: [packages/play-vue/examples/demo/src/catalog.ts:6](https://gitlab.com/xmachin-es/xmachines-js/-/blob/v1.0.0-beta.57/packages/play-vue/examples/demo/src/catalog.ts#L6)

package/examples/@xmachines/play-vue-demo/variables/App.md

@@ -6,4 +6,4 @@
 const App: DefineComponent<{}, {}, unknown>;
 ```
 
-Defined in: [packages/play-vue/examples/demo/src/env.d.ts:5](https://gitlab.com/xmachin-es/xmachines-js/-/blob/v1.0.0-beta.55/packages/play-vue/examples/demo/src/env.d.ts#L5)
+Defined in: [packages/play-vue/examples/demo/src/env.d.ts:5](https://gitlab.com/xmachin-es/xmachines-js/-/blob/v1.0.0-beta.57/packages/play-vue/examples/demo/src/env.d.ts#L5)

package/examples/@xmachines/play-vue-demo/variables/authCatalog.md

@@ -169,4 +169,4 @@ const authCatalog: Catalog<
 >;
 ```
 
-Defined in: [packages/play-vue/examples/demo/src/catalog.ts:5](https://gitlab.com/xmachin-es/xmachines-js/-/blob/v1.0.0-beta.55/packages/play-vue/examples/demo/src/catalog.ts#L5)
+Defined in: [packages/play-vue/examples/demo/src/catalog.ts:5](https://gitlab.com/xmachin-es/xmachines-js/-/blob/v1.0.0-beta.57/packages/play-vue/examples/demo/src/catalog.ts#L5)

package/examples/@xmachines/play-vue-router-demo/README.md

@@ -19,11 +19,11 @@ Vue Router integration demo for the XMachines Play architecture using Vue Compos
 From the repository root:
 
 ```bash
-npm install
-npm run dev -w @xmachines/play-vue-router-demo
+pnpm install
+pnpm --filter @xmachines/play-vue-router-demo run dev
 ```
 
-Then open `http://localhost:3001`.
+Then open `http://localhost:3010`.
 
 ## Step-by-Step Code Flow
 
@@ -114,21 +114,21 @@ Vue Router integration remains passive infrastructure. `RouterBridgeBase` owns s
 
 These commands are defined in `package.json`:
 
-| Command                                                   | Description                      |
-| --------------------------------------------------------- | -------------------------------- |
-| `npm run dev -w @xmachines/play-vue-router-demo`          | Start Vite dev server            |
-| `npm run build -w @xmachines/play-vue-router-demo`        | Build production bundle          |
-| `npm run preview -w @xmachines/play-vue-router-demo`      | Preview built bundle             |
-| `npm run test -w @xmachines/play-vue-router-demo`         | Run Vitest test suite            |
-| `npm run test:browser -w @xmachines/play-vue-router-demo` | Run browser-focused Vitest suite |
+| Command                                                          | Description                                    |
+| ---------------------------------------------------------------- | ---------------------------------------------- |
+| `pnpm --filter @xmachines/play-vue-router-demo run dev`          | Start Vite dev server (http://localhost:3010/) |
+| `pnpm --filter @xmachines/play-vue-router-demo run build`        | Build production bundle                        |
+| `pnpm --filter @xmachines/play-vue-router-demo run preview`      | Preview built bundle                           |
+| `pnpm --filter @xmachines/play-vue-router-demo run test`         | Run Vitest test suite                          |
+| `pnpm --filter @xmachines/play-vue-router-demo run test:browser` | Run browser-focused Vitest suite               |
 
 ## Verification
 
 Use these checks to validate README claims against the current demo implementation:
 
 ```bash
-npm run test -w @xmachines/play-vue-router-demo
-npm run test:browser -w @xmachines/play-vue-router-demo
+pnpm --filter @xmachines/play-vue-router-demo run test
+pnpm --filter @xmachines/play-vue-router-demo run test:browser
 ```
 
 Expected result: reactivity integration tests and the browser shared-demo suite both pass, confirming login/logout transitions update both view and URL correctly.

package/examples/README.md

@@ -58,16 +58,16 @@ The conceptual examples in this directory are TypeScript snippets. To run them:
 
 ```bash
 # Install dependencies (from the monorepo root)
-npm install @xmachines/play-xstate @xmachines/play-actor @xmachines/play-signals xstate
+pnpm add @xmachines/play-xstate @xmachines/play-actor @xmachines/play-signals xstate
 
 # Run with tsx
-npx tsx my-example.ts
+pnpm dlx tsx my-example.ts
 ```
 
 To run a complete demo application, use the workspace package name:
 
 ```bash
-npm run dev -w @xmachines/play-dom-router-demo
+pnpm --filter @xmachines/play-dom-router-demo run dev
 ```
 
 ## Key Packages

package/examples/form-validation.md

@@ -184,7 +184,7 @@ actor.stop();
 
 ## `$bindState` and `$state` Pattern
 
-`meta.view` uses the `@json-render/core` spec format (`PlaySpec`). Two special directives wire the component to a local per-state state store:
+`meta.view` uses the `@xmachines/json-render-core` spec format (`PlaySpec`). Two special directives wire the component to a local per-state state store:
 
 | Directive                     | Direction | Usage                                                       |
 | ----------------------------- | --------- | ----------------------------------------------------------- |
@@ -229,7 +229,7 @@ The machine spec above defines view structure — but nothing renders until you
 
 ```typescript
 import { createRenderer, schema } from "@xmachines/play-dom";
-import { defineCatalog } from "@json-render/core";
+import { defineCatalog } from "@xmachines/json-render-core";
 import { z } from "zod";
 import type { ComponentFn } from "@xmachines/play-dom";
 

package/guides/getting-started.md

@@ -20,13 +20,13 @@ Jump to the section that applies to you:
 
 You need the following installed before cloning the repository:
 
-| Requirement | Version              | Notes                                                        |
-| ----------- | -------------------- | ------------------------------------------------------------ |
-| Node.js     | `>= 22.0.0`          | Specified in all `package.json` `engines` fields             |
-| npm         | bundled with Node 22 | The project uses npm workspaces — no separate install needed |
-| Git         | any recent version   | Conventional commit format is enforced by CI                 |
+| Requirement | Version            | Notes                                                                                                                 |
+| ----------- | ------------------ | --------------------------------------------------------------------------------------------------------------------- |
+| Node.js     | `>= 22.0.0`        | Specified in all `package.json` `engines` fields                                                                      |
+| pnpm        | via corepack       | Enable with `corepack enable`; the version is pinned by the `packageManager` field. The project uses pnpm workspaces. |
+| Git         | any recent version | Conventional commit format is enforced by CI                                                                          |
 
-No global TypeScript install is needed — it is installed as a dev dependency via `npm ci`.
+No global TypeScript install is needed — it is installed as a dev dependency via `pnpm install --frozen-lockfile`.
 
 > **Node.js version manager tip:** If you manage multiple Node versions with `nvm` or `fnm`, install and activate Node 22 before proceeding.
 
@@ -41,18 +41,19 @@ cd xmachines-js
 
 #### 2. Install dependencies
 
-Always use `npm ci` (not `npm install`) to respect the lockfile exactly:
+Always use `pnpm install --frozen-lockfile` (not `pnpm install`) to respect the lockfile exactly:
 
 ```bash
-npm ci
+corepack enable
+pnpm install --frozen-lockfile
 ```
 
-This installs all workspace dependencies and automatically runs `patch-package` via the `postinstall` hook to apply the patches in `patches/`. The patch output is expected and required — do not skip it.
+This installs the exact versions recorded in the lockfile for all workspace packages.
 
 #### 3. Build all packages
 
 ```bash
-npm run build
+pnpm run build
 ```
 
 The root `tsc --build` command uses TypeScript project references to compile all packages in correct dependency order. Build outputs go to each package's `dist/` directory (gitignored).
@@ -62,7 +63,7 @@ The root `tsc --build` command uses TypeScript project references to compile all
 Verify your setup is working end-to-end:
 
 ```bash
-npm test
+pnpm test
 ```
 
 All tests should pass on a freshly cloned and built repository. If they do, your environment is correctly configured.
@@ -76,7 +77,7 @@ A fully configured dev container is provided at `.devcontainer/`. It uses Docker
 **CLI:**
 
 ```bash
-npm run devcontainer:up
+pnpm run devcontainer:up
 ```
 
 To customize the container, copy the sample env file:
@@ -98,20 +99,12 @@ Available variables:
 
 The test suite relies on TypeScript path aliases that resolve to source files. If aliases are not resolving:
 
-1. Run `npm run build` first — some packages need their `dist/` present even in development.
+1. Run `pnpm run build` first — some packages need their `dist/` present even in development.
 2. Confirm your package's `vitest.config.ts` uses `defineXmVitestConfig` from `@xmachines/shared/vitest`, which automatically configures the `@xmachines/*` path aliases.
 
 #### TypeScript errors about missing types after adding a dependency
 
-Run `npm ci` again to ensure all types are installed. If you added a workspace-local dependency, also add the correct `references` entry in the package's `tsconfig.base.json`.
-
-#### `patch-package` errors during install
-
-The patches in `patches/` are version-specific. If you updated a `@json-render` package, regenerate the patch:
-
-```bash
-npx patch-package <package-name>
-```
+Run `pnpm install --frozen-lockfile` again to ensure all types are installed. If you added a workspace-local dependency, also add the correct `references` entry in the package's `tsconfig.base.json`.
 
 #### Lint errors about import extensions
 
@@ -150,7 +143,7 @@ This section covers installing XMachines packages into your own application and
 ### Prerequisites
 
 - **Node.js** `>= 22.0.0`
-- **npm** `>= 10.0.0`
+- **pnpm** via corepack (`corepack enable`)
 - **TypeScript** `>= 5.7` (strict mode recommended)
 - **XState** `v5` (required peer dependency for [`@xmachines/play-xstate`](../api/@xmachines/play-xstate/README.md))
 
@@ -163,7 +156,7 @@ All packages are ES modules (`"type": "module"`). Use `.js` extensions in all Ty
 Every XMachines application needs these three packages plus XState:
 
 ```bash
-npm install xstate @xmachines/play-xstate @xmachines/play-actor @xmachines/play-signals
+pnpm add xstate @xmachines/play-xstate @xmachines/play-actor @xmachines/play-signals
 ```
 
 | Package                                                               | Role                                                                                                                                                                |
@@ -177,26 +170,26 @@ npm install xstate @xmachines/play-xstate @xmachines/play-actor @xmachines/play-
 
 ```bash
 # Provider pattern (framework-integrated routers)
-npm install @xmachines/play-tanstack-react-router   # TanStack Router (React)
-npm install @xmachines/play-tanstack-solid-router   # TanStack Router (SolidJS)
-npm install @xmachines/play-react-router            # React Router v7
-npm install @xmachines/play-vue-router              # Vue Router 4.x/5.x
-npm install @xmachines/play-solid-router            # SolidJS Router
+pnpm add @xmachines/play-tanstack-react-router   # TanStack Router (React)
+pnpm add @xmachines/play-tanstack-solid-router   # TanStack Router (SolidJS)
+pnpm add @xmachines/play-react-router            # React Router v7
+pnpm add @xmachines/play-vue-router              # Vue Router 4.x/5.x
+pnpm add @xmachines/play-solid-router            # SolidJS Router
 
 # connectRouter pattern (framework-agnostic)
-npm install @xmachines/play-dom-router              # Vanilla DOM (Browser History API)
-npm install @xmachines/play-sveltekit-router        # SvelteKit
-npm install @xmachines/play-svelte-spa-router       # Svelte SPA Router
+pnpm add @xmachines/play-dom-router              # Vanilla DOM (Browser History API)
+pnpm add @xmachines/play-sveltekit-router        # SvelteKit
+pnpm add @xmachines/play-svelte-spa-router       # Svelte SPA Router
 ```
 
 #### Step 3: Install a view renderer (pick one)
 
 ```bash
-npm install @xmachines/play-react    # React 18/19
-npm install @xmachines/play-vue      # Vue 3
-npm install @xmachines/play-solid    # SolidJS
-npm install @xmachines/play-svelte   # Svelte 5
-npm install @xmachines/play-dom      # Vanilla DOM
+pnpm add @xmachines/play-react    # React 18/19
+pnpm add @xmachines/play-vue      # Vue 3
+pnpm add @xmachines/play-solid    # SolidJS
+pnpm add @xmachines/play-svelte   # Svelte 5
+pnpm add @xmachines/play-dom      # Vanilla DOM
 ```
 
 ---
@@ -448,7 +441,7 @@ View renderers map `meta.view` specs from your machine states to real UI compone
 
 ```tsx
 import { PlayUIProvider, PlayRenderer, defineRegistry } from "@xmachines/play-react";
-import { defineCatalog } from "@json-render/core";
+import { defineCatalog } from "@xmachines/json-render-core";
 import { schema } from "@xmachines/play-react";
 import { z } from "zod";
 
@@ -495,7 +488,7 @@ function App() {
 
 <script setup lang="ts">
 	import { PlayUIProvider, PlayRenderer, defineRegistry } from "@xmachines/play-vue";
-	import { defineCatalog } from "@json-render/core";
+	import { defineCatalog } from "@xmachines/json-render-core";
 	import { schema } from "@xmachines/play-vue";
 	import { z } from "zod";
 
@@ -527,7 +520,7 @@ function App() {
 
 ```tsx
 import { PlayUIProvider, PlayRenderer, defineRegistry } from "@xmachines/play-solid";
-import { defineCatalog } from "@json-render/core";
+import { defineCatalog } from "@xmachines/json-render-core";
 import { schema } from "@xmachines/play-solid";
 import { z } from "zod";
 
@@ -566,7 +559,7 @@ function App() {
 
 ```typescript
 import { createPlayUI, defineRegistry, schema } from "@xmachines/play-dom";
-import { defineCatalog } from "@json-render/core";
+import { defineCatalog } from "@xmachines/json-render-core";
 import { z } from "zod";
 import type { ComponentFn } from "@xmachines/play-dom";
 
@@ -701,7 +694,7 @@ node --version
 | [`extractMachineRoutes`](../api/@xmachines/play-router/functions/extractMachineRoutes.md)             | Extracts a `RouteTree` from a state machine — used by framework-integrated router adapters                      |
 | [`createRouteMapFromTree`](../api/@xmachines/play-router/functions/createRouteMapFromTree.md)         | Builds a `RouteMap` from a `RouteTree` for bidirectional state ID ↔ URL lookups                                 |
 | [`connectRouter`](../api/@xmachines/play-dom-router/functions/connectRouter.md)                       | Connects a vanilla DOM router to an actor — returns a disconnect cleanup function                               |
-| [`PlayRouterProvider`](../api/@xmachines/play-tanstack-react-router/functions/PlayRouterProvider.md)  | React component that connects a `PlayerActor` to TanStack React Router                                          |
+| [`PlayRouterProvider`](../api/@xmachines/play-tanstack-react-router/variables/PlayRouterProvider.md)  | React component that connects a `PlayerActor` to TanStack React Router                                          |
 
 ---
 

package/guides/signals.md

@@ -158,8 +158,8 @@ Failing to clean up watchers causes memory leaks and stale callbacks firing afte
 
 ## See also
 
-- [Understanding the Actor Model](concepts-actor-model.md) — why the actor owns all signal writes
-- [Understanding State Machines](concepts-state-machines.md) — how state nodes produce the metadata that signals derive
+- [Understanding the Actor Model](actor-model.md) — why the actor owns all signal writes
+- [Understanding State Machines](state-machines.md) — how state nodes produce the metadata that signals derive
 - [Getting Started](getting-started.md) — hands-on walkthrough using signals to observe an actor
 - [@xmachines/play-signals](../api/@xmachines/play-signals/README.md) — API reference
 - [Play RFC](../rfc/play.md) — architectural specification

package/guides/state-machines.md

@@ -124,7 +124,7 @@ const appMachine = setup({
 
 `meta.route` is a string path. When the machine enters a state, `actor.currentRoute` (a `Signal.Computed`) derives this path and emits it. The router bridge reads it and updates the URL.
 
-`meta.view` is a [`PlaySpec`](../api/@xmachines/play-actor/interfaces/PlaySpec.md) — a `@json-render/core` spec object describing what to render. Use `typedSpec<TContext>(...)` from [`@xmachines/play-actor`](../api/@xmachines/play-actor/README.md) to validate `contextProps` entries at compile time. When the machine enters a state, `actor.currentView` is updated with this spec. The renderer reads it and projects it through framework components.
+`meta.view` is a [`PlaySpec`](../api/@xmachines/play-actor/interfaces/PlaySpec.md) — a `@xmachines/json-render-core` spec object describing what to render. Use `typedSpec<TContext>(...)` from [`@xmachines/play-actor`](../api/@xmachines/play-actor/README.md) to validate `contextProps` entries at compile time. When the machine enters a state, `actor.currentView` is updated with this spec. The renderer reads it and projects it through framework components.
 
 **The machine is the single source of truth for both routing and views.** There is no separate route configuration file. There is no switch statement in a component deciding what to render based on the URL. The state machine encodes all of that.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xmachines/docs",
-  "version": "1.0.0-beta.55",
+  "version": "1.0.0-beta.57",
   "description": "Documentation for XMachines",
   "keywords": [
     "documentation",
@@ -54,7 +54,7 @@
   "devDependencies": {
     "@testing-library/jest-dom": "^6.9.1",
     "@types/node": "^25.6.0",
-    "@xmachines/shared": "1.0.0-beta.55",
+    "@xmachines/shared": "1.0.0-beta.57",
     "oxfmt": "^0.47.0",
     "oxlint": "^1.62.0",
     "typedoc": "^0.28.19",

package/rfc/play.md

@@ -143,7 +143,7 @@ The base class requires only two abstract members: **reactive state** and **type
 ```ts
 import { Actor, type AnyActorLogic, type EventObject } from "xstate";
 import type { Signal } from "@xmachines/play-signals";
-import type { Spec } from "@json-render/core";
+import type { Spec } from "@xmachines/json-render-core";
 
 // Optional capability: Routing
 export interface Routable {
@@ -177,7 +177,7 @@ export abstract class AbstractActor<
 
 1. Not all actors need routing (e.g. embedded sub-actors)
 2. Not all actors need view rendering (e.g. background logic actors)
-3. Catalog/schema concerns are handled by the renderer layer (`@json-render/core`), not the actor
+3. Catalog/schema concerns are handled by the renderer layer (`@xmachines/json-render-core`), not the actor
 
 ### 5.2 Logic Layer
 
@@ -231,7 +231,7 @@ class PlayerActor<TMachine extends AnyStateMachine>
 }
 ```
 
-**Design Rationale:** The original design passed a `catalog` to `definePlayer` and returned `{ create, catalog }`. The implementation decoupled catalogs entirely — component schemas are defined via `@json-render/core`'s `defineCatalog` and bound to renderers via `defineRegistry`, not to actors. This means a single actor can be rendered by different component libraries without change.
+**Design Rationale:** The original design passed a `catalog` to `definePlayer` and returned `{ create, catalog }`. The implementation decoupled catalogs entirely — component schemas are defined via `@xmachines/json-render-core`'s `defineCatalog` and bound to renderers via `defineRegistry`, not to actors. This means a single actor can be rendered by different component libraries without change.
 
 ### 5.3 Router Layer
 
@@ -295,12 +295,12 @@ Each adapter extends `RouterBridgeBase` and implements the three abstract method
 
 Each view renderer provides a `PlayRenderer` component that passively observes the actor's `currentView` signal and projects the JSON spec into framework-native components via `@json-render`.
 
-| Package                 | Framework   | JSON-Render Backend  |
-| ----------------------- | ----------- | -------------------- |
-| `@xmachines/play-react` | React       | `@json-render/react` |
-| `@xmachines/play-vue`   | Vue 3       | `@json-render/vue`   |
-| `@xmachines/play-solid` | SolidJS     | `@json-render/solid` |
-| `@xmachines/play-dom`   | Vanilla DOM | `@json-render/core`  |
+| Package                 | Framework   | JSON-Render Backend            |
+| ----------------------- | ----------- | ------------------------------ |
+| `@xmachines/play-react` | React       | `@xmachines/json-render-react` |
+| `@xmachines/play-vue`   | Vue 3       | `@xmachines/json-render-vue`   |
+| `@xmachines/play-solid` | SolidJS     | `@xmachines/json-render-solid` |
+| `@xmachines/play-dom`   | Vanilla DOM | `@xmachines/json-render-core`  |
 
 **Shared Architecture (all renderers):**
 
@@ -337,7 +337,7 @@ export { useActor } from "./useActor";
 // Error handling
 export { PlayErrorBoundary } from "./PlayErrorBoundary";
 
-// Re-exports from @json-render/react
+// Re-exports from @xmachines/json-render-react
 export {
 	defineRegistry,
 	JSONUIProvider,
@@ -346,19 +346,19 @@ export {
 	VisibilityProvider,
 	ValidationProvider,
 	Renderer,
-} from "@json-render/react";
+} from "@xmachines/json-render-react";
 ```
 
-**Design Rationale:** `PlayRenderer` is now a **zero-prop leaf component** — it reads view context from the enclosing `ActorProvider` via `usePlayView()`. All mount-time concerns (actor bridging, signal subscription, store lifecycle, `onRenderError` injection) are centralised in `ActorProvider`. `PlayUIProvider` is the batteries-included composite that wraps `ActorProvider` + `JSONUIProvider` with a handler bridge. This mirrors the provider/renderer split in `@json-render/*` and makes the separation of concerns explicit.
+**Design Rationale:** `PlayRenderer` is now a **zero-prop leaf component** — it reads view context from the enclosing `ActorProvider` via `usePlayView()`. All mount-time concerns (actor bridging, signal subscription, store lifecycle, `onRenderError` injection) are centralised in `ActorProvider`. `PlayUIProvider` is the batteries-included composite that wraps `ActorProvider` + `JSONUIProvider` with a handler bridge. This mirrors the provider/renderer split in `@xmachines/json-render-*` and makes the separation of concerns explicit.
 
 ### 5.5 Schema Layer (External)
 
-Component schemas and UI vocabularies are defined via `@json-render/core`, an external package not in the `@xmachines` scope.
+Component schemas and UI vocabularies are defined via `@xmachines/json-render-core`, an external package not in the `@xmachines` scope.
 
 - `defineCatalog` — Defines available components and prop schemas (via Zod)
-- `defineRegistry` — Binds a catalog to framework-specific component implementations (available from each `@json-render/*` framework package)
+- `defineRegistry` — Binds a catalog to framework-specific component implementations (available from each `@xmachines/json-render-*` framework package)
 
-The original RFC proposed an `@xmachines/play-ui` package for this purpose. The implementation delegates to `@json-render/core` instead, which provides the same functionality with broader ecosystem support.
+The original RFC proposed an `@xmachines/play-ui` package for this purpose. The implementation delegates to `@xmachines/json-render-core` instead, which provides the same functionality with broader ecosystem support.
 
 ---
 
@@ -369,7 +369,7 @@ The original RFC proposed an `@xmachines/play-ui` package for this purpose. The
 Defines the **UI vocabulary** — available components and their prop schemas. No framework code.
 
 ```ts
-import { defineCatalog, z } from "@json-render/core";
+import { defineCatalog, z } from "@xmachines/json-render-core";
 
 export const catalog = defineCatalog({
 	components: {