@agent-native/core 0.182.0 → 0.182.1-nightly-20260916202735

package/corpus/templates/mail/.agents/skills/shadcn-ui/SKILL.md

@@ -1,10 +1,9 @@
 ---
 name: shadcn-ui
 description: >-
-  The shadcn CLI, component composition, theming, and registry workflow. Use
-  when adding, replacing, upgrading, or debugging a shadcn/ui primitive itself,
-  or when changing a theme or registry. Do not load it for ordinary edits to a
-  file that happens to import a shadcn component.
+  Project-aware shadcn/ui components, registry MCP, theming, and design-system
+  lint feedback. Use when adding or changing React/Tailwind UI, a primitive,
+  theme, registry, or component contract in an Agent-Native app.
 scope: dev
 source: https://ui.shadcn.com/docs/skills
 local-changes: >-
@@ -16,11 +15,18 @@ metadata:
 
 # shadcn/ui
 
-This skill keeps shadcn/ui work project-aware. Components are source files in the app, so always inspect the local project before adding, importing, or rewriting them.
+This skill keeps shadcn/ui work project-aware. Components are source files in the
+app, so always inspect the local project before adding, importing, or rewriting
+them. When `@shadcn/lint` is configured, treat its feedback as implementation
+guidance, not cosmetic noise. The framework repository runs it through the root
+Oxlint configuration; generated workspaces carry this skill and the MCP
+workflow, but do not automatically inherit that repository-only lint setup.
 
 ## First Steps
 
-1. Work from the app root that owns `components.json`.
+1. Work from the app root that owns `components.json`. In this monorepo, that is
+   the selected app/template directory (usually under `templates/`), not the
+   repository root.
 2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
@@ -29,6 +35,59 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
 
+## MCP Registry Workflow
+
+Each first-party app keeps the official shadcn MCP configuration in `.mcp.json`
+next to its `components.json`. Start the agent from that app root so the MCP
+server resolves the correct aliases, local UI directory, and Tailwind theme.
+Do not add a single repository-root server: the root is a workspace, not a
+shadcn project, and would make installs target the wrong project.
+
+- Use the shadcn MCP to search, inspect, and install registry items when it is
+  connected. Prefer the app's configured registries over copied source.
+- Use `pnpm dlx shadcn@latest info --json` for project context; the MCP has no
+  equivalent project-info tool.
+- If the MCP is unavailable, use the equivalent `pnpm dlx shadcn@latest`
+  command from the same app root and continue following this skill.
+- Keep registry URLs and aliases in that app's `components.json`. Never put
+  registry credentials in MCP config or checked-in source.
+
+## Design-System Lint Feedback
+
+In the framework repository, `pnpm lint` runs Oxlint with `@shadcn/lint` for the
+scoped template UI paths. Run it after UI changes and fix every `shadcn/*`
+finding before handing off. Template packages use the workspace lint
+configuration; do not create a second local lint configuration just for one
+app.
+
+Before claiming that shadcn lint ran in another workspace, inspect its root
+`package.json` and `.oxlintrc.json`. The generic generated workspace currently
+exposes `pnpm lint` as formatting-only and does not ship `@shadcn/lint` or the
+framework repository's Oxlint config. In that scaffold, use this skill plus the
+connected shadcn MCP (or the CLI fallback) for design-system guidance, and do
+not report `shadcn/*` checks as having run. If the workspace owner adopts the
+linter, add the dependency, scoped config, and lint script together.
+
+The Plan template is intentionally excluded from this rollout. Its files remain
+under `templates/plan/**`, but the root Oxlint ignore list keeps them out of the
+shadcn checks until that template has a separate lint baseline.
+
+- `no-restyle`: use the component's `variant`, `size`, and semantic props; put
+  layout on a parent and add a component variant only when the design system
+  genuinely needs a new treatment.
+- `no-raw-colors`: use the theme tokens in the app's `global.css`, not raw
+  Tailwind palette classes or hard-coded color attributes.
+- `no-arbitrary-values`: use the theme scale or a declared token instead of
+  one-off bracket values.
+- `no-inline-styles`: use classes or CSS custom properties for dynamic layout;
+  keep intentional editor/export exceptions scoped to their owning subsystem.
+- `no-unknown-classes` and `require-static-classes`: use classes Tailwind can
+  generate and keep class strings statically discoverable.
+
+The local primitive source is the contract boundary. Product code should consume
+its props and variants; update `packages/toolkit/src/ui/` or an app's
+`components/ui/` only when the design-system contract itself changes.
+
 ## Agent-Native Adapter Rule
 
 Pages, routes, and domain components import controls through the app's local UI

package/corpus/templates/mail/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "shadcn": {
+      "command": "npx",
+      "args": ["shadcn@latest", "mcp"]
+    }
+  }
+}

package/corpus/templates/plan/.agents/skills/shadcn-ui/SKILL.md

@@ -1,10 +1,9 @@
 ---
 name: shadcn-ui
 description: >-
-  The shadcn CLI, component composition, theming, and registry workflow. Use
-  when adding, replacing, upgrading, or debugging a shadcn/ui primitive itself,
-  or when changing a theme or registry. Do not load it for ordinary edits to a
-  file that happens to import a shadcn component.
+  Project-aware shadcn/ui components, registry MCP, theming, and design-system
+  lint feedback. Use when adding or changing React/Tailwind UI, a primitive,
+  theme, registry, or component contract in an Agent-Native app.
 scope: dev
 source: https://ui.shadcn.com/docs/skills
 local-changes: >-
@@ -16,11 +15,18 @@ metadata:
 
 # shadcn/ui
 
-This skill keeps shadcn/ui work project-aware. Components are source files in the app, so always inspect the local project before adding, importing, or rewriting them.
+This skill keeps shadcn/ui work project-aware. Components are source files in the
+app, so always inspect the local project before adding, importing, or rewriting
+them. When `@shadcn/lint` is configured, treat its feedback as implementation
+guidance, not cosmetic noise. The framework repository runs it through the root
+Oxlint configuration; generated workspaces carry this skill and the MCP
+workflow, but do not automatically inherit that repository-only lint setup.
 
 ## First Steps
 
-1. Work from the app root that owns `components.json`.
+1. Work from the app root that owns `components.json`. In this monorepo, that is
+   the selected app/template directory (usually under `templates/`), not the
+   repository root.
 2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
@@ -29,6 +35,59 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
 
+## MCP Registry Workflow
+
+Each first-party app keeps the official shadcn MCP configuration in `.mcp.json`
+next to its `components.json`. Start the agent from that app root so the MCP
+server resolves the correct aliases, local UI directory, and Tailwind theme.
+Do not add a single repository-root server: the root is a workspace, not a
+shadcn project, and would make installs target the wrong project.
+
+- Use the shadcn MCP to search, inspect, and install registry items when it is
+  connected. Prefer the app's configured registries over copied source.
+- Use `pnpm dlx shadcn@latest info --json` for project context; the MCP has no
+  equivalent project-info tool.
+- If the MCP is unavailable, use the equivalent `pnpm dlx shadcn@latest`
+  command from the same app root and continue following this skill.
+- Keep registry URLs and aliases in that app's `components.json`. Never put
+  registry credentials in MCP config or checked-in source.
+
+## Design-System Lint Feedback
+
+In the framework repository, `pnpm lint` runs Oxlint with `@shadcn/lint` for the
+scoped template UI paths. Run it after UI changes and fix every `shadcn/*`
+finding before handing off. Template packages use the workspace lint
+configuration; do not create a second local lint configuration just for one
+app.
+
+Before claiming that shadcn lint ran in another workspace, inspect its root
+`package.json` and `.oxlintrc.json`. The generic generated workspace currently
+exposes `pnpm lint` as formatting-only and does not ship `@shadcn/lint` or the
+framework repository's Oxlint config. In that scaffold, use this skill plus the
+connected shadcn MCP (or the CLI fallback) for design-system guidance, and do
+not report `shadcn/*` checks as having run. If the workspace owner adopts the
+linter, add the dependency, scoped config, and lint script together.
+
+The Plan template is intentionally excluded from this rollout. Its files remain
+under `templates/plan/**`, but the root Oxlint ignore list keeps them out of the
+shadcn checks until that template has a separate lint baseline.
+
+- `no-restyle`: use the component's `variant`, `size`, and semantic props; put
+  layout on a parent and add a component variant only when the design system
+  genuinely needs a new treatment.
+- `no-raw-colors`: use the theme tokens in the app's `global.css`, not raw
+  Tailwind palette classes or hard-coded color attributes.
+- `no-arbitrary-values`: use the theme scale or a declared token instead of
+  one-off bracket values.
+- `no-inline-styles`: use classes or CSS custom properties for dynamic layout;
+  keep intentional editor/export exceptions scoped to their owning subsystem.
+- `no-unknown-classes` and `require-static-classes`: use classes Tailwind can
+  generate and keep class strings statically discoverable.
+
+The local primitive source is the contract boundary. Product code should consume
+its props and variants; update `packages/toolkit/src/ui/` or an app's
+`components/ui/` only when the design-system contract itself changes.
+
 ## Agent-Native Adapter Rule
 
 Pages, routes, and domain components import controls through the app's local UI

package/corpus/templates/plan/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "shadcn": {
+      "command": "npx",
+      "args": ["shadcn@latest", "mcp"]
+    }
+  }
+}

package/corpus/templates/slides/.agents/skills/shadcn-ui/SKILL.md

@@ -1,10 +1,9 @@
 ---
 name: shadcn-ui
 description: >-
-  The shadcn CLI, component composition, theming, and registry workflow. Use
-  when adding, replacing, upgrading, or debugging a shadcn/ui primitive itself,
-  or when changing a theme or registry. Do not load it for ordinary edits to a
-  file that happens to import a shadcn component.
+  Project-aware shadcn/ui components, registry MCP, theming, and design-system
+  lint feedback. Use when adding or changing React/Tailwind UI, a primitive,
+  theme, registry, or component contract in an Agent-Native app.
 scope: dev
 source: https://ui.shadcn.com/docs/skills
 local-changes: >-
@@ -16,11 +15,18 @@ metadata:
 
 # shadcn/ui
 
-This skill keeps shadcn/ui work project-aware. Components are source files in the app, so always inspect the local project before adding, importing, or rewriting them.
+This skill keeps shadcn/ui work project-aware. Components are source files in the
+app, so always inspect the local project before adding, importing, or rewriting
+them. When `@shadcn/lint` is configured, treat its feedback as implementation
+guidance, not cosmetic noise. The framework repository runs it through the root
+Oxlint configuration; generated workspaces carry this skill and the MCP
+workflow, but do not automatically inherit that repository-only lint setup.
 
 ## First Steps
 
-1. Work from the app root that owns `components.json`.
+1. Work from the app root that owns `components.json`. In this monorepo, that is
+   the selected app/template directory (usually under `templates/`), not the
+   repository root.
 2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
@@ -29,6 +35,59 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
 
+## MCP Registry Workflow
+
+Each first-party app keeps the official shadcn MCP configuration in `.mcp.json`
+next to its `components.json`. Start the agent from that app root so the MCP
+server resolves the correct aliases, local UI directory, and Tailwind theme.
+Do not add a single repository-root server: the root is a workspace, not a
+shadcn project, and would make installs target the wrong project.
+
+- Use the shadcn MCP to search, inspect, and install registry items when it is
+  connected. Prefer the app's configured registries over copied source.
+- Use `pnpm dlx shadcn@latest info --json` for project context; the MCP has no
+  equivalent project-info tool.
+- If the MCP is unavailable, use the equivalent `pnpm dlx shadcn@latest`
+  command from the same app root and continue following this skill.
+- Keep registry URLs and aliases in that app's `components.json`. Never put
+  registry credentials in MCP config or checked-in source.
+
+## Design-System Lint Feedback
+
+In the framework repository, `pnpm lint` runs Oxlint with `@shadcn/lint` for the
+scoped template UI paths. Run it after UI changes and fix every `shadcn/*`
+finding before handing off. Template packages use the workspace lint
+configuration; do not create a second local lint configuration just for one
+app.
+
+Before claiming that shadcn lint ran in another workspace, inspect its root
+`package.json` and `.oxlintrc.json`. The generic generated workspace currently
+exposes `pnpm lint` as formatting-only and does not ship `@shadcn/lint` or the
+framework repository's Oxlint config. In that scaffold, use this skill plus the
+connected shadcn MCP (or the CLI fallback) for design-system guidance, and do
+not report `shadcn/*` checks as having run. If the workspace owner adopts the
+linter, add the dependency, scoped config, and lint script together.
+
+The Plan template is intentionally excluded from this rollout. Its files remain
+under `templates/plan/**`, but the root Oxlint ignore list keeps them out of the
+shadcn checks until that template has a separate lint baseline.
+
+- `no-restyle`: use the component's `variant`, `size`, and semantic props; put
+  layout on a parent and add a component variant only when the design system
+  genuinely needs a new treatment.
+- `no-raw-colors`: use the theme tokens in the app's `global.css`, not raw
+  Tailwind palette classes or hard-coded color attributes.
+- `no-arbitrary-values`: use the theme scale or a declared token instead of
+  one-off bracket values.
+- `no-inline-styles`: use classes or CSS custom properties for dynamic layout;
+  keep intentional editor/export exceptions scoped to their owning subsystem.
+- `no-unknown-classes` and `require-static-classes`: use classes Tailwind can
+  generate and keep class strings statically discoverable.
+
+The local primitive source is the contract boundary. Product code should consume
+its props and variants; update `packages/toolkit/src/ui/` or an app's
+`components/ui/` only when the design-system contract itself changes.
+
 ## Agent-Native Adapter Rule
 
 Pages, routes, and domain components import controls through the app's local UI

package/corpus/templates/slides/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "shadcn": {
+      "command": "npx",
+      "args": ["shadcn@latest", "mcp"]
+    }
+  }
+}

package/corpus/templates/slides/server/plugins/collab.ts

@@ -23,6 +23,9 @@ export default createCollabPlugin({
   table: "decks",
   contentColumn: "data",
   idColumn: "id",
+  // These documents carry presence and cursors, not deck content. Seeding the
+  // full deck into every deck/slide presence document wastes cold-start work.
+  autoSeed: false,
   access: {
     mode: "resource",
     resourceType: "deck",

package/corpus/templates/tasks/.agents/skills/shadcn-ui/SKILL.md

@@ -1,10 +1,9 @@
 ---
 name: shadcn-ui
 description: >-
-  The shadcn CLI, component composition, theming, and registry workflow. Use
-  when adding, replacing, upgrading, or debugging a shadcn/ui primitive itself,
-  or when changing a theme or registry. Do not load it for ordinary edits to a
-  file that happens to import a shadcn component.
+  Project-aware shadcn/ui components, registry MCP, theming, and design-system
+  lint feedback. Use when adding or changing React/Tailwind UI, a primitive,
+  theme, registry, or component contract in an Agent-Native app.
 scope: dev
 source: https://ui.shadcn.com/docs/skills
 local-changes: >-
@@ -16,11 +15,18 @@ metadata:
 
 # shadcn/ui
 
-This skill keeps shadcn/ui work project-aware. Components are source files in the app, so always inspect the local project before adding, importing, or rewriting them.
+This skill keeps shadcn/ui work project-aware. Components are source files in the
+app, so always inspect the local project before adding, importing, or rewriting
+them. When `@shadcn/lint` is configured, treat its feedback as implementation
+guidance, not cosmetic noise. The framework repository runs it through the root
+Oxlint configuration; generated workspaces carry this skill and the MCP
+workflow, but do not automatically inherit that repository-only lint setup.
 
 ## First Steps
 
-1. Work from the app root that owns `components.json`.
+1. Work from the app root that owns `components.json`. In this monorepo, that is
+   the selected app/template directory (usually under `templates/`), not the
+   repository root.
 2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
@@ -29,6 +35,59 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
 
+## MCP Registry Workflow
+
+Each first-party app keeps the official shadcn MCP configuration in `.mcp.json`
+next to its `components.json`. Start the agent from that app root so the MCP
+server resolves the correct aliases, local UI directory, and Tailwind theme.
+Do not add a single repository-root server: the root is a workspace, not a
+shadcn project, and would make installs target the wrong project.
+
+- Use the shadcn MCP to search, inspect, and install registry items when it is
+  connected. Prefer the app's configured registries over copied source.
+- Use `pnpm dlx shadcn@latest info --json` for project context; the MCP has no
+  equivalent project-info tool.
+- If the MCP is unavailable, use the equivalent `pnpm dlx shadcn@latest`
+  command from the same app root and continue following this skill.
+- Keep registry URLs and aliases in that app's `components.json`. Never put
+  registry credentials in MCP config or checked-in source.
+
+## Design-System Lint Feedback
+
+In the framework repository, `pnpm lint` runs Oxlint with `@shadcn/lint` for the
+scoped template UI paths. Run it after UI changes and fix every `shadcn/*`
+finding before handing off. Template packages use the workspace lint
+configuration; do not create a second local lint configuration just for one
+app.
+
+Before claiming that shadcn lint ran in another workspace, inspect its root
+`package.json` and `.oxlintrc.json`. The generic generated workspace currently
+exposes `pnpm lint` as formatting-only and does not ship `@shadcn/lint` or the
+framework repository's Oxlint config. In that scaffold, use this skill plus the
+connected shadcn MCP (or the CLI fallback) for design-system guidance, and do
+not report `shadcn/*` checks as having run. If the workspace owner adopts the
+linter, add the dependency, scoped config, and lint script together.
+
+The Plan template is intentionally excluded from this rollout. Its files remain
+under `templates/plan/**`, but the root Oxlint ignore list keeps them out of the
+shadcn checks until that template has a separate lint baseline.
+
+- `no-restyle`: use the component's `variant`, `size`, and semantic props; put
+  layout on a parent and add a component variant only when the design system
+  genuinely needs a new treatment.
+- `no-raw-colors`: use the theme tokens in the app's `global.css`, not raw
+  Tailwind palette classes or hard-coded color attributes.
+- `no-arbitrary-values`: use the theme scale or a declared token instead of
+  one-off bracket values.
+- `no-inline-styles`: use classes or CSS custom properties for dynamic layout;
+  keep intentional editor/export exceptions scoped to their owning subsystem.
+- `no-unknown-classes` and `require-static-classes`: use classes Tailwind can
+  generate and keep class strings statically discoverable.
+
+The local primitive source is the contract boundary. Product code should consume
+its props and variants; update `packages/toolkit/src/ui/` or an app's
+`components/ui/` only when the design-system contract itself changes.
+
 ## Agent-Native Adapter Rule
 
 Pages, routes, and domain components import controls through the app's local UI

package/corpus/templates/tasks/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "shadcn": {
+      "command": "npx",
+      "args": ["shadcn@latest", "mcp"]
+    }
+  }
+}

package/dist/automation/index.d.ts

@@ -186,8 +186,8 @@ export declare function createAutomationCallbackHandler(runtime: AutomationRunti
     duplicate?: undefined;
     eventId?: undefined;
 } | {
+    error?: undefined;
     accepted: boolean;
     duplicate: boolean;
     eventId: string;
-    error?: undefined;
 }>;

package/dist/cli/create.js

@@ -1226,13 +1226,14 @@ function localPackageTarball(packageDir) {
     const npm = process.platform === "win32" ? "npm.cmd" : "npm";
     execFileSync(npm, ["pack", "--ignore-scripts", "--pack-destination", packDir], {
         cwd: packageDir,
-        encoding: "utf-8",
         env: {
             ...process.env,
             npm_config_cache: npmCacheDir,
             npm_config_ignore_scripts: "true",
         },
-        stdio: "pipe",
+        // npm pack prints one line per included file; piping that output through
+        // execFileSync can hit Node's 1 MiB buffer before the artifact exists.
+        stdio: "ignore",
     });
     const tarballs = fs
         .readdirSync(packDir)
@@ -1250,13 +1251,12 @@ function localPackageTarball(packageDir) {
     const repackNpmCacheDir = path.join(repackDir, "npm-cache");
     execFileSync(npm, ["pack", "--ignore-scripts", "--pack-destination", repackDir], {
         cwd: path.join(unpackDir, "package"),
-        encoding: "utf-8",
         env: {
             ...process.env,
             npm_config_cache: repackNpmCacheDir,
             npm_config_ignore_scripts: "true",
         },
-        stdio: "pipe",
+        stdio: "ignore",
     });
     const repackedTarballs = fs
         .readdirSync(repackDir)
@@ -1633,7 +1633,12 @@ function postProcessStandalone(name, targetDir, templateName, resolution) {
             ].some((deps) => Boolean(deps?.["node-pty"]));
             fs.writeFileSync(pkgPath, JSON.stringify(pkg, null, 2) + "\n");
         }
-        catch { }
+        catch (error) {
+            const detail = error instanceof Error ? error.message : String(error);
+            throw new Error(`Could not finalize ${pkgPath}: ${detail}`, {
+                cause: error,
+            });
+        }
     }
     // Write pnpm-workspace.yaml for pnpm v11 compatibility. pnpm v11 no longer
     // reads the pnpm field in package.json, so allowBuilds and overrides must

package/dist/collab/storage.d.ts

@@ -29,10 +29,8 @@ export declare function trySaveYDocState(docId: string, state: Uint8Array, textS
 export declare function trySaveYDocStateWithClient(client: DbExec, docId: string, state: Uint8Array, textSnapshot: string, expectedVersion: number | null): Promise<boolean>;
 /** Save Yjs state (Uint8Array) and a plain-text snapshot. */
 export declare function saveYDocState(docId: string, state: Uint8Array, textSnapshot: string): Promise<void>;
-/** Check if a document has collaborative state. */
+/** Check if a document has non-empty collaborative state. */
 export declare function hasCollabState(docId: string): Promise<boolean>;
-/** Load all existing document ids in one query for startup reconciliation. */
-export declare function listCollabDocIds(): Promise<Set<string>>;
 /** Delete collaborative state for a document. */
 export declare function deleteCollabState(docId: string): Promise<void>;
 declare function uint8ArrayToBase64(arr: Uint8Array): string;

package/dist/collab/storage.js

@@ -119,23 +119,16 @@ export async function saveYDocState(docId, state, textSnapshot) {
         args: [b64, textSnapshot, docId],
     });
 }
-/** Check if a document has collaborative state. */
+/** Check if a document has non-empty collaborative state. */
 export async function hasCollabState(docId) {
     await ensureTable();
     const client = getDbExec();
     const { rows } = await client.execute({
-        sql: `SELECT 1 FROM _collab_docs WHERE doc_id = ?`,
+        sql: `SELECT 1 FROM _collab_docs WHERE doc_id = ? AND yjs_state <> ''`,
         args: [docId],
     });
     return rows.length > 0;
 }
-/** Load all existing document ids in one query for startup reconciliation. */
-export async function listCollabDocIds() {
-    await ensureTable();
-    const client = getDbExec();
-    const { rows } = await client.execute("SELECT doc_id FROM _collab_docs");
-    return new Set(rows.flatMap((row) => typeof row.doc_id === "string" && row.doc_id ? [row.doc_id] : []));
-}
 /** Delete collaborative state for a document. */
 export async function deleteCollabState(docId) {
     await ensureTable();

package/dist/collab/ydoc-manager.d.ts

@@ -121,7 +121,7 @@ export declare function getIncUpdate(docId: string, clientStateVector: Uint8Arra
  * Seed a document from existing text content (for migration).
  * Only seeds if no collab state exists yet.
  */
-export declare function seedFromText(docId: string, text: string, fieldName?: string): Promise<void>;
+export declare function seedFromText(docId: string, text: string, fieldName?: string, client?: DbExec): Promise<void>;
 /**
  * Apply a full JSON update to a document. Computes the minimal diff
  * and converts it to Yjs operations on Y.Map/Y.Array.
@@ -139,7 +139,7 @@ export declare function getJson(docId: string, fieldName?: string): Promise<any>
  * Seed a document from existing JSON content (for migration).
  * Only seeds if no collab state exists yet.
  */
-export declare function seedFromJson(docId: string, json: any, fieldName?: string, type?: "map" | "array"): Promise<void>;
+export declare function seedFromJson(docId: string, json: any, fieldName?: string, type?: "map" | "array", client?: DbExec): Promise<void>;
 /**
  * Release a document from the in-memory cache.
  */

package/dist/collab/ydoc-manager.js

@@ -21,7 +21,7 @@
 import * as Y from "yjs";
 import { emitCollabUpdate } from "./emitter.js";
 import { applyJsonDiff, applyJsonPatch, yDocToJson, initYDocWithJson, } from "./json-to-yjs.js";
-import { loadYDocRecord, loadYDocState, loadYDocVersion, trySaveYDocState, trySaveYDocStateWithClient, } from "./storage.js";
+import { loadYDocRecord, loadYDocRecordWithClient, loadYDocVersion, trySaveYDocState, trySaveYDocStateWithClient, } from "./storage.js";
 import { uint8ArrayToBase64 } from "./storage.js";
 import { applyTextToYDoc, initYDocWithText } from "./text-to-yjs.js";
 import { searchAndReplaceInYXml, extractTextFromYXml } from "./xml-ops.js";
@@ -527,27 +527,44 @@ export async function getIncUpdate(docId, clientStateVector) {
  * Seed a document from existing text content (for migration).
  * Only seeds if no collab state exists yet.
  */
-export async function seedFromText(docId, text, fieldName = DEFAULT_FIELD) {
+export async function seedFromText(docId, text, fieldName = DEFAULT_FIELD, client) {
     return withDocWriteLock(docId, async () => {
-        const existing = await loadYDocState(docId);
-        if (existing && existing.length > 0)
+        const existing = client
+            ? await loadYDocRecordWithClient(client, docId)
+            : await loadYDocRecord(docId);
+        if (existing && existing.state.length > 0)
             return; // Already seeded
+        const expectedVersion = existing ? existing.version : null;
         const { doc, state } = initYDocWithText(fieldName, text);
         let saved;
         try {
-            saved = await trySaveYDocState(docId, state, text, null);
+            saved = client
+                ? await trySaveYDocStateWithClient(client, docId, state, text, expectedVersion)
+                : await trySaveYDocState(docId, state, text, expectedVersion);
         }
         catch (error) {
             doc.destroy();
             throw error;
         }
         if (!saved) {
+            releaseDoc(docId);
+            doc.destroy();
+            return;
+        }
+        releaseDoc(docId);
+        // A caller-owned transaction may still roll back after this function
+        // returns, so never publish its uncommitted doc into the process cache.
+        if (client) {
             doc.destroy();
             return;
         }
         // Cache the doc
         evictIfNeeded();
-        _cache.set(docId, { doc, lastAccess: Date.now(), syncedVersion: 0 });
+        _cache.set(docId, {
+            doc,
+            lastAccess: Date.now(),
+            syncedVersion: existing ? existing.version + 1 : 0,
+        });
     });
 }
 // ─── Structured JSON Operations ─────────────────────────────────────
@@ -599,27 +616,44 @@ export async function getJson(docId, fieldName = "data") {
  * Seed a document from existing JSON content (for migration).
  * Only seeds if no collab state exists yet.
  */
-export async function seedFromJson(docId, json, fieldName = "data", type = "map") {
+export async function seedFromJson(docId, json, fieldName = "data", type = "map", client) {
     return withDocWriteLock(docId, async () => {
-        const existing = await loadYDocState(docId);
-        if (existing && existing.length > 0)
+        const existing = client
+            ? await loadYDocRecordWithClient(client, docId)
+            : await loadYDocRecord(docId);
+        if (existing && existing.state.length > 0)
             return; // Already seeded
+        const expectedVersion = existing ? existing.version : null;
         const { doc, state } = initYDocWithJson(fieldName, json, type);
         let saved;
         try {
-            saved = await trySaveYDocState(docId, state, JSON.stringify(json), null);
+            saved = client
+                ? await trySaveYDocStateWithClient(client, docId, state, JSON.stringify(json), expectedVersion)
+                : await trySaveYDocState(docId, state, JSON.stringify(json), expectedVersion);
         }
         catch (error) {
             doc.destroy();
             throw error;
         }
         if (!saved) {
+            releaseDoc(docId);
+            doc.destroy();
+            return;
+        }
+        releaseDoc(docId);
+        // See seedFromText: a transaction-owned seed becomes cacheable only after
+        // its commit, when the route reads the now-durable state.
+        if (client) {
             doc.destroy();
             return;
         }
         // Cache the doc
         evictIfNeeded();
-        _cache.set(docId, { doc, lastAccess: Date.now(), syncedVersion: 0 });
+        _cache.set(docId, {
+            doc,
+            lastAccess: Date.now(),
+            syncedVersion: existing ? existing.version + 1 : 0,
+        });
     });
 }
 /**