@agent-native/core 0.102.2 → 0.103.1

package/corpus/templates/clips/app/i18n/hi-IN.ts

@@ -1214,9 +1214,10 @@ Clips में उपयोगकर्ताओं को दिखने व
     visibilityOrg: "Organization (स्थानीयकृत)",
     visibilityPublic: "Public (स्थानीयकृत)",
     passwordProtection: "Password protection (स्थानीयकृत)",
-    passwordSetPlaceholder:
-      "Password is set — type to replace, leave empty + Save to clear (स्थानीयकृत)",
+    passwordSetPlaceholder: "Password is set — type to replace (स्थानीयकृत)",
     noPasswordPlaceholder: "No password (स्थानीयकृत)",
+    passwordWhitespaceOnly: "Spaces alone aren't a valid password. (स्थानीयकृत)",
+    removePassword: "Remove (स्थानीयकृत)",
     expiry: "Expiry (स्थानीयकृत)",
     viewerOptions: "Viewer options (स्थानीयकृत)",
     comments: "Comments (स्थानीयकृत)",

package/corpus/templates/clips/app/i18n/ja-JP.ts

@@ -1237,8 +1237,11 @@ Clips のユーザー向けの主な変更はここに記録されます。コ
     visibilityPublic: "Public (ローカライズ済み)",
     passwordProtection: "Password protection (ローカライズ済み)",
     passwordSetPlaceholder:
-      "Password is set — type to replace, leave empty + Save to clear (ローカライズ済み)",
+      "Password is set — type to replace (ローカライズ済み)",
     noPasswordPlaceholder: "No password (ローカライズ済み)",
+    passwordWhitespaceOnly:
+      "Spaces alone aren't a valid password. (ローカライズ済み)",
+    removePassword: "Remove (ローカライズ済み)",
     expiry: "Expiry (ローカライズ済み)",
     viewerOptions: "Viewer options (ローカライズ済み)",
     comments: "Comments (ローカライズ済み)",

package/corpus/templates/clips/app/i18n/ko-KR.ts

@@ -1224,9 +1224,10 @@ Clips의 모든 사용자 대상 변경 사항은 여기에 기록됩니다. 명
     visibilityOrg: "Organization (현지화됨)",
     visibilityPublic: "Public (현지화됨)",
     passwordProtection: "Password protection (현지화됨)",
-    passwordSetPlaceholder:
-      "Password is set — type to replace, leave empty + Save to clear (현지화됨)",
+    passwordSetPlaceholder: "Password is set — type to replace (현지화됨)",
     noPasswordPlaceholder: "No password (현지화됨)",
+    passwordWhitespaceOnly: "Spaces alone aren't a valid password. (현지화됨)",
+    removePassword: "Remove (현지화됨)",
     expiry: "Expiry (현지화됨)",
     viewerOptions: "Viewer options (현지화됨)",
     comments: "Comments (현지화됨)",

package/corpus/templates/clips/app/i18n/pt-BR.ts

@@ -1242,9 +1242,11 @@ Todas as mudanças visíveis para usuários do Clips são documentadas aqui. Voc
     visibilityOrg: "Organization (Localizado)",
     visibilityPublic: "Public (Localizado)",
     passwordProtection: "Password protection (Localizado)",
-    passwordSetPlaceholder:
-      "Password is set — type to replace, leave empty + Save to clear (Localizado)",
+    passwordSetPlaceholder: "Password is set — type to replace (Localizado)",
     noPasswordPlaceholder: "No password (Localizado)",
+    passwordWhitespaceOnly:
+      "Spaces alone aren't a valid password. (Localizado)",
+    removePassword: "Remove (Localizado)",
     expiry: "Expiry (Localizado)",
     viewerOptions: "Viewer options (Localizado)",
     comments: "Comments (Localizado)",

package/corpus/templates/clips/app/i18n/zh-CN.ts

@@ -1186,9 +1186,10 @@ Clips 中所有面向用户的重要更改都会记录在这里。你可以随
     visibilityOrg: "Organization (已本地化)",
     visibilityPublic: "Public (已本地化)",
     passwordProtection: "Password protection (已本地化)",
-    passwordSetPlaceholder:
-      "Password is set — type to replace, leave empty + Save to clear (已本地化)",
+    passwordSetPlaceholder: "Password is set — type to replace (已本地化)",
     noPasswordPlaceholder: "No password (已本地化)",
+    passwordWhitespaceOnly: "Spaces alone aren't a valid password. (已本地化)",
+    removePassword: "Remove (已本地化)",
     expiry: "Expiry (已本地化)",
     viewerOptions: "Viewer options (已本地化)",
     comments: "Comments (已本地化)",

package/corpus/templates/clips/app/i18n/zh-TW.ts

@@ -1171,9 +1171,10 @@ const messages = {
     visibilityOrg: "組織",
     visibilityPublic: "公開",
     passwordProtection: "密碼保護",
-    passwordSetPlaceholder:
-      "已設定密碼。輸入新密碼即可取代；留空並儲存即可清除。",
+    passwordSetPlaceholder: "已設定密碼。輸入新密碼即可取代。",
     noPasswordPlaceholder: "無密碼",
+    passwordWhitespaceOnly: "只有空格不是有效的密碼。",
+    removePassword: "移除",
     expiry: "到期時間",
     viewerOptions: "觀看者選項",
     comments: "留言",

package/corpus/templates/clips/app/routes/r.$recordingId.tsx

@@ -20,6 +20,7 @@ import {
   isLoomEmbedBackedRecording,
   isLoomRecordingSource,
 } from "@shared/loom";
+import { CLIP_SHARE_REF, REF_PARAM } from "@shared/share-attribution";
 import {
   IconShare3,
   IconArrowLeft,
@@ -336,6 +337,31 @@ export default function RecordingPage() {
     },
   );
 
+  const playerDataAccessStatus = playerDataQ.isError
+    ? (playerDataQ.error as { status?: number } | undefined)?.status
+    : undefined;
+  // Signed-out requests never even reach `resolveAccess` — the action route's
+  // default auth gate rejects them with 401 first. Authenticated viewers with
+  // no share grant (or a deleted/mismatched id) get 403 from `resolveAccess`
+  // inside `get-recording-player-data`. Both mean "can't open the direct
+  // owner/editor route here".
+  const playerDataForbidden =
+    playerDataAccessStatus === 401 || playerDataAccessStatus === 403;
+
+  // A direct `/r/:id` visit without edit/view access (signed out, no share
+  // grant, wrong org) can't do anything useful here — send the visitor to the
+  // public share flow instead, which knows how to prompt for sign-in or a
+  // password.
+  useEffect(() => {
+    if (!recordingId || !playerDataForbidden) return;
+    navigate(
+      `/share/${encodeURIComponent(recordingId)}?${REF_PARAM}=${CLIP_SHARE_REF}`,
+      {
+        replace: true,
+      },
+    );
+  }, [recordingId, playerDataForbidden, navigate]);
+
   const recording = playerDataQ.data?.recording;
   const role = playerDataQ.data?.role as
     | "owner"
@@ -717,7 +743,7 @@ export default function RecordingPage() {
 
   if (!recordingId) return null;
 
-  if (playerDataQ.isLoading) {
+  if (playerDataQ.isLoading || playerDataForbidden) {
     return (
       <div className="flex items-center justify-center h-screen w-full bg-background">
         <Spinner className="h-8 w-8" />

package/corpus/templates/clips/server/lib/share-password.ts

@@ -18,13 +18,16 @@ import {
 } from "@agent-native/core/secrets/crypto";
 
 /**
- * Encrypt a share password for storage. Empty / nullish clears it (returns
- * null), matching the prior `args.password ?? null` semantics.
+ * Encrypt a share password for storage. Empty / nullish / whitespace-only
+ * input clears it (returns null), matching the prior `args.password ?? null`
+ * semantics while also rejecting spaces-only "passwords". Real values are
+ * trimmed so accidental leading/trailing whitespace doesn't get baked into
+ * the stored password.
  */
 export function encryptSharePassword(
   raw: string | null | undefined,
 ): string | null {
-  const value = typeof raw === "string" ? raw : "";
+  const value = typeof raw === "string" ? raw.trim() : "";
   if (!value) return null;
   return encryptSecretValue(value);
 }

package/corpus/templates/content/.agents/skills/content/SKILL.md

@@ -3,7 +3,7 @@ name: content
 description: >-
   Use Content for repo-backed Markdown/MDX docs, blogs, resources, rich
   document editing, Notion-style databases and boards, structured intake
-  forms, local components, shareable copies, and Content local-file workspaces.
+  forms, local components, shareable copies, and connected local folders.
   Prefer Content actions over raw filesystem writes when available.
 metadata:
   visibility: exported
@@ -17,7 +17,7 @@ marketing pages, internal notes, and local MDX components. Also use Content for
 Notion-style databases, tables, boards, structured request intake, and forms
 whose submissions become database row pages. Content gives the agent a document
 tree, a rich editor, structured database properties and views, normal document
-actions, and an optional local-file source of truth.
+actions, and local folders that sync into the same database model.
 
 ## Choose The Path
 
@@ -33,9 +33,9 @@ actions, and an optional local-file source of truth.
   its exact title, then inspect it with `get-content-database` before creating
   or submitting anything. Do not create a second database when the canonical
   one already exists.
-- In Local File Mode, Content actions read and write the repo files declared in
-  `agent-native.json`; SQL remains cache/history/search glue, not the source of
-  truth for those pages.
+- Local folders are sources attached to a space's canonical Files database.
+  Imported pages are normal SQL-backed Content documents; the trusted local
+  bridge handles pull, export, stable file identity, and conflict review.
 - If Content tools are not visible and no local Content app or Desktop bridge is
   running, treat this skill as repo-editing guidance. Edit configured
   `.md`/`.mdx` files directly, preserve frontmatter and MDX imports, and tell
@@ -47,10 +47,10 @@ Prefer JSON input for action calls:
 
 ```bash
 pnpm action list-documents
-pnpm action get-document '{"id":"local-file:..."}'
-pnpm action edit-document '{"id":"local-file:...","find":"old copy","replace":"new copy"}'
-pnpm action update-document '{"id":"local-file:...","content":"# Updated\n\nBody"}'
-pnpm action share-local-file-document '{"id":"local-file:..."}'
+pnpm action get-document '{"id":"<document-id>"}'
+pnpm action edit-document '{"id":"<document-id>","find":"old copy","replace":"new copy"}'
+pnpm action update-document '{"id":"<document-id>","content":"# Updated\n\nBody"}'
+pnpm action connect-local-folder-source '{"connectionId":"<opaque-bridge-id>","label":"Docs","createSourceBackedSpace":true,"truthPolicy":"source_primary"}'
 ```
 
 Run `refresh-list` after create/update/delete operations when you need the open
@@ -132,7 +132,7 @@ guesswork:
   writing. If a named person cannot be resolved unambiguously, clarify in the
   originating Slack thread; never omit, downgrade, or silently drop the person.
 
-## Local File Mode
+## Local Folder Sources
 
 Install into an existing repo with:
 
@@ -140,40 +140,27 @@ Install into an existing repo with:
 npx @agent-native/core@latest skills add content --mode local-files --scope project
 ```
 
-The installer copies this skill and writes or updates `agent-native.json` with
-Content roots for `docs/`, `blog/`, `content/`, and `resources/`, plus a
-`components/` folder for local MDX components. A typical manifest looks like:
+The compatibility spelling still installs the skill, but it no longer enables
+a separate data mode. The CLI writes or updates `agent-native.json` with
+declarative local-folder sources and launches normal database-backed Content.
+A typical root looks like:
 
 ```json
 {
   "version": 1,
   "apps": {
     "content": {
-      "mode": "local-files",
       "roots": [
         {
           "name": "Docs",
           "path": "docs",
           "kind": "docs",
-          "extensions": [".md", ".mdx"]
-        },
-        {
-          "name": "Blog",
-          "path": "blog",
-          "kind": "blog",
-          "extensions": [".md", ".mdx"]
-        },
-        {
-          "name": "Content",
-          "path": "content",
-          "kind": "content",
-          "extensions": [".md", ".mdx"]
-        },
-        {
-          "name": "Resources",
-          "path": "resources",
-          "kind": "resources",
-          "extensions": [".md", ".mdx"]
+          "extensions": [".md", ".mdx"],
+          "source": {
+            "type": "local-folder",
+            "connectionId": "local-folder:<opaque-id>",
+            "truthPolicy": "source_primary"
+          }
         }
       ],
       "components": "components",
@@ -184,9 +171,10 @@ Content roots for `docs/`, `blog/`, `content/`, and `resources/`, plus a
 }
 ```
 
-Local File Mode does not make the host language model local, and the hosted
-Content app cannot read private repo files by itself. File access requires a
-local Content app, Agent Native Desktop, or another trusted local bridge.
+Content never stores an absolute local path or raw file body in source metadata.
+File access still requires a local Content app, Agent Native Desktop, or another
+trusted bridge. Disconnecting a folder leaves the SQL pages and disk files in
+place. Concurrent edits and missing source files require explicit review.
 
 ## MDX And Components
 
@@ -202,9 +190,8 @@ local Content app, Agent Native Desktop, or another trusted local bridge.
 
 ## Boundaries
 
-- Moving, renaming, and reordering local-file pages are not first-class Content
-  UI operations yet. Use normal file operations when the user asks for those,
-  then let Content rediscover the file tree.
+- Preserve a page's frontmatter `id` when renaming a source file so the next
+  sync recognizes it as the same global Content page.
 - Do not push/pull Notion, Builder.io, or other provider-backed content unless
   the user explicitly asks for provider sync.
 - Do not paste secrets, private provider data, or credential-looking values into

package/corpus/templates/content/AGENTS.md

@@ -96,6 +96,11 @@ cd templates/content && pnpm action <name> [args]
 | `list-documents`                            | `[--format json]`                                                                                                                                                                                  | List document metadata/tree; no full bodies                                                                                                                                       |
 | `export-content-source`                     | `[--format json]`                                                                                                                                                                                  | Export editable docs as `content/*.mdx` source files                                                                                                                              |
 | `import-content-source`                     | `--files <json> [--dryRun true\|false]`                                                                                                                                                            | Import `.md`/`.mdx` source files into editable docs                                                                                                                               |
+| `connect-local-folder-source`               | `--connectionId <opaque-id> --label <name> [--spaceId <id>\|--databaseId <id>\|--createSourceBackedSpace true] [--truthPolicy database_primary\|source_primary\|reviewed_bidirectional]`           | Connect a trusted browser/Desktop folder registry entry to canonical Files without storing its path or handle in SQL                                                              |
+| `sync-local-folder-source`                  | `--sourceId <id> --files <json> [--dryRun true\|false]`                                                                                                                                            | Materialize a connected folder through Files source rows and record concurrent changes for review                                                                                 |
+| `sync-manifest-local-folder-source`         | `--connectionId <opaque-id> [--file <relative-path>] [--spaceId <id>] [--dryRun true\|false]`                                                                                                      | Use the trusted local server bridge to materialize a manifest-declared folder into normal SQL-backed Content                                                                      |
+| `resolve-local-folder-conflict`             | `--changeSetId <id> --decision keep_content\|accept_source [--sourceContent <text>]`                                                                                                               | Resolve a reviewed folder conflict; accepting requires the exact hashed folder revision                                                                                           |
+| `disconnect-local-folder-source`            | `--sourceId <id>`                                                                                                                                                                                  | Disconnect a folder adapter without deleting local files or its SQL-backed Content pages                                                                                          |
 | `list-builder-docs`                         | `[--model docs-content\|blog-article] [--limit <n>]`                                                                                                                                               | List Builder docs/blog entries available for `.builder.mdx` pull                                                                                                                  |
 | `pull-builder-doc`                          | `--model <model> --entryId <builder-entry-id> [--dryRun true\|false]`                                                                                                                              | Pull one Builder entry into Content and return `.builder.mdx` plus `content/builder/.raw` sidecar files                                                                           |
 | `check-builder-doc`                         | `--files <json> [--path <file.builder.mdx>]` or `--documentId <id>`                                                                                                                                | Validate Builder MDX round-trip, sidecar hashes, and remote conflict status before push                                                                                           |
@@ -112,7 +117,10 @@ cd templates/content && pnpm action <name> [args]
 | `remove-local-file-source`                  | `[--sourceRootPath <path>]`                                                                                                                                                                        | Unlink local-file sources from Content without deleting local Markdown/MDX files                                                                                                  |
 | `list-local-component-files`                |                                                                                                                                                                                                    | List registered local MDX component source files                                                                                                                                  |
 | `write-local-component-file`                | `--workspaceId <id> --path <relative-component-path> --content <source>`                                                                                                                           | Create or update a file in a registered local `components/` folder                                                                                                                |
-| `create-content-database`                   | `[--documentId <id>] [--parentId <id>] [--title <text>] [--description <text>]`                                                                                                                    | Create a described database page or convert an existing page into a database                                                                                                      |
+| `ensure-content-spaces`                     |                                                                                                                                                                                                    | Idempotently provision the signed-in user's personal and current organization Content spaces, system databases, and catalog references                                            |
+| `backfill-content-files`                    |                                                                                                                                                                                                    | Assign legacy pages to Content spaces and reconcile exactly one canonical Files database membership per non-system page                                                           |
+| `list-content-spaces`                       |                                                                                                                                                                                                    | List already-provisioned Content spaces authorized by the signed-in user's current ownership or organization memberships                                                          |
+| `create-content-database`                   | `[--documentId <id>] [--spaceId <id>] [--parentId <id>] [--title <text>] [--description <text>]`                                                                                                   | Create a described database page in a Content space or convert an existing page into a database                                                                                   |
 | `create-inline-content-database`            | `--hostDocumentId <id> [--title <text>] [--description <text>]`                                                                                                                                    | Create a described database owned by an inline database block in the host document                                                                                                |
 | `get-content-database`                      | `--databaseId <id>` or `--documentId <id>`                                                                                                                                                         | Get a database with its description, property/option schema guidance, item pages, and computed ancestry context                                                                   |
 | `list-trashed-content-databases`            |                                                                                                                                                                                                    | List soft-deleted databases visible in the sidebar Trash surface                                                                                                                  |
@@ -193,37 +201,24 @@ strip of the markdown.
 
 ### Local Source Files
 
-Content has two file workflows:
+Content has one database-backed document model with optional folder sources:
 
-- **Database mode local folders:** the `/local-files` view links one or more
+- **Local folder sources:** the `/local-files` view links one or more
   browser or Agent Native Desktop folders to SQL-backed documents. The UI uses
-  folder rows: **Pull** reads local `.md`/`.mdx` files through
-  `import-content-source`, **Check** runs the same import as `--dryRun true`,
-  and **Push** uses `export-content-source` to write Content documents back to
-  the chosen folder. Files with known `id` values update existing docs only
-  when the caller has editor access, and files without ids create new private
-  docs for the current user. Imported rows keep `source.mode: "local-files"`
-  and `source.path`, so `list-documents`/`get-document` can distinguish them
-  from ordinary private pages and the sidebar can show them under Local files.
-  With one linked folder, imported paths stay flat (`content/page.mdx`); with
-  multiple linked folders, paths are prefixed by folder name so Local files can
-  group them by folder. Once a source folder is linked, the selected
-  `.md`/`.mdx` file is authoritative: opening the page reads the file, editor
-  saves write the file first, and SQL is updated afterward as
-  cache/history/search glue. Use `--dryRun true` before a large import when the
-  source folder may contain unexpected files.
-- **Local File Mode editing:** when the app runs with `AGENT_NATIVE_MODE=local-files`
-  or an `agent-native.json` whose app config enables local files, the standard
-  Content editor reads and writes configured repo files directly. The left
-  sidebar is populated from local roots such as `docs/`, `blog/`, `content/`,
-  and `resources/`; selecting a file opens `/page/<local-file-id>` and
-  `update-document` writes the selected `.md`/`.mdx` file. The document id is
-  derived from the file path, and unknown frontmatter is preserved when title,
-  content, icon, or favorite state changes.
-  Repos can opt into `profile: "docs/no-bookkeeping"` to keep docs edits from
-  adding absent `updatedAt`, `icon`, or `isFavorite` frontmatter. Content-only
-  edits under that profile preserve existing frontmatter but do not create new
-  bookkeeping keys; explicit title/icon/favorite edits still persist.
+  folder rows: **Pull** calls `sync-local-folder-source`, **Check** runs the
+  same action with `dryRun: true`, and **Push** uses the source-scoped
+  `export-content-source`. Imported files become ordinary SQL documents in the
+  target space's canonical Files database. Preserve frontmatter `id` across
+  renames; missing files and concurrent changes become reviewable incoming
+  change sets instead of silently deleting or overwriting a page. SQL stores
+  only opaque connection identity, relative paths, and hashes. Disconnecting a
+  folder keeps both the Content pages and disk files.
+- **Manifest/CLI bridge:** `agent-native content local-files <target>` remains
+  as a compatibility spelling, but it launches normal database-backed Content.
+  `agent-native.json` declares `source.type: "local-folder"` and an opaque
+  `connectionId`; it does not select a separate application mode. The trusted
+  local server bridge materializes that source through
+  `sync-manifest-local-folder-source`.
 - **Local MDX components:** local file workspaces can expose React components
   from the configured `components` folder. Export PascalCase components such as
   `ImpactCounter` from `.tsx` files, then use `<ImpactCounter />` in MDX or pick

package/corpus/templates/content/actions/_builder-docs-client.ts

@@ -36,6 +36,12 @@ import {
   type BuilderCmsSourceEntry,
 } from "./_builder-cms-source-adapter.js";
 import { executeBuilderCmsWrite } from "./_builder-cms-write-client.js";
+import { ensureDocumentFilesMembership } from "./_content-files.js";
+import {
+  organizationContentSpaceId,
+  personalContentSpaceId,
+  provisionContentSpaces,
+} from "./_content-spaces.js";
 import { flushOpenDocumentEditorToSql } from "./_document-flush.js";
 
 type FetchLike = typeof fetch;
@@ -524,6 +530,17 @@ export async function pullBuilderDocIntoContent(args: {
   if (!ownerEmail) throw new Error("no authenticated user");
   const orgId = getRequestOrgId() ?? null;
   const db = getDb();
+  const provisioned = args.dryRun
+    ? null
+    : await provisionContentSpaces(db, ownerEmail);
+  const targetSpaceId = orgId
+    ? organizationContentSpaceId(orgId)
+    : personalContentSpaceId(ownerEmail);
+  if (provisioned && !provisioned.spaceIds.includes(targetSpaceId)) {
+    throw new Error(
+      "The active organization does not have a writable Content space.",
+    );
+  }
   const entry = await readFullBuilderDocsEntry({
     model: args.model,
     entryId: args.entryId,
@@ -554,6 +571,9 @@ export async function pullBuilderDocIntoContent(args: {
       `Requires editor access to update document "${documentId}".`,
     );
   }
+  if (existing?.spaceId && existing.spaceId !== targetSpaceId) {
+    throw new Error("Builder document belongs to a different Content space.");
+  }
 
   const sourceFields = builderDocumentSourceFields(bundle, now);
 
@@ -562,6 +582,7 @@ export async function pullBuilderDocIntoContent(args: {
       await db
         .update(schema.documents)
         .set({
+          spaceId: existing.spaceId ?? targetSpaceId,
           title: bundle.mdx.title,
           content: bundle.mdx.body,
           updatedAt: now,
@@ -571,6 +592,7 @@ export async function pullBuilderDocIntoContent(args: {
     } else {
       await db.insert(schema.documents).values({
         id: documentId,
+        spaceId: targetSpaceId,
         ownerEmail,
         orgId,
         parentId: null,
@@ -586,6 +608,7 @@ export async function pullBuilderDocIntoContent(args: {
         ...sourceFields,
       });
     }
+    await ensureDocumentFilesMembership(db, documentId, now);
     await replaceBuilderDocumentSidecars({
       db,
       documentId,

package/corpus/templates/content/actions/_content-database-source-adapters.ts

@@ -68,13 +68,31 @@ const notionDatabaseAdapter: ContentDatabaseSourceAdapter = {
   read: readNotionDatabaseSource,
 };
 
+const localFolderAdapter: ContentDatabaseSourceAdapter = {
+  sourceType: "local-folder",
+  async read() {
+    return {
+      state: "error",
+      entries: [],
+      fields: [],
+      fetchedAt: new Date().toISOString(),
+      message:
+        "Local folder refresh requires the trusted browser or Desktop bridge.",
+      metadata: { bridgeRequired: true },
+    };
+  },
+};
+
 const adapters = new Map<
   ContentDatabaseSourceType,
   ContentDatabaseSourceAdapter
 >(
-  [builderCmsAdapter, localTableAdapter, notionDatabaseAdapter].map(
-    (adapter) => [adapter.sourceType, adapter],
-  ),
+  [
+    builderCmsAdapter,
+    localTableAdapter,
+    notionDatabaseAdapter,
+    localFolderAdapter,
+  ].map((adapter) => [adapter.sourceType, adapter]),
 );
 
 export function getContentDatabaseSourceAdapter(