@mulmoclaude/core 1.9.0 → 1.11.0

package/assets/helps/error-recovery.md

@@ -225,6 +225,91 @@ shipped registry repo's README. Common rejections:
 - `name` reuses the reserved value `official`.
 - `name` doesn't match `[A-Za-z0-9][A-Za-z0-9_-]{0,31}`.
 
+## A hand-placed custom role never appears in the list
+
+### Symptoms
+
+- The user put a file in `config/roles/` themselves (not via Settings →
+  Roles / `manageRoles`) and the role is absent from the role list.
+- Nothing failed in tool output — `manageRoles` with `action: "list"`
+  simply doesn't include it.
+
+### Cause + fix
+
+The loader reads **`config/roles/<id>.json` only**, and a file it cannot
+use is skipped rather than fatal — so one broken file can't take the
+whole list down. The reason is in the server log as a `[roles]` warning
+naming the file:
+
+- `role file is not valid JSON, skipping` — trailing comma, single
+  quotes, unquoted key.
+- `role file does not match the role schema, skipping` — the `issues`
+  field names each field, e.g. `icon: Invalid input: expected string,
+  received undefined`. All of `id`, `name`, `icon`, `prompt`,
+  `availablePlugins` are required; `availablePlugins` must be an array
+  even for one entry.
+- `role file is empty, skipping` — zero-length or whitespace only.
+- `role file could not be read, skipping` — permissions, or the path is
+  a directory.
+- `role file disappeared while loading, skipping` — the file was renamed
+  or deleted while the list was being read, or it is a broken symlink.
+  Re-running the load is enough if the file is there now.
+- `ignoring entries that are not .json files` — a `.md` / `.jsonc` /
+  `.json.txt` file is never read as a role.
+
+Ask the user for that warning line (or the file's contents) rather than
+guessing which of the six it is. Writing the role through
+`manageRoles` instead sidesteps all of them — it serializes the role, so
+the file is always valid.
+
+## A custom role is in the list but delete / update says it doesn't exist
+
+### Symptoms
+
+- `manageRoles` with `action: "list"` includes the role, but `delete` or
+  `update` on that same id returns `Role '<id>' not found.`
+- Or: `Cannot delete built-in roles.` for a role the user created.
+- Or: the user edited a role and the change had no effect, because
+  another file with the same id is the one that id resolves to.
+
+### Cause + fix
+
+The list shows the `id` from **inside** the file, while delete / update
+address the role by its **file name** — so `config/roles/designer.json`
+containing `"id": "myrole"` is listed as `myrole` but delete / update
+only accept `designer`. Two `[roles]` warnings in the server log name
+it:
+
+- `role id does not match its file name` — `fileName` and `id` are both in
+  the warning. Which repair is safe depends on which side is malformed:
+  role ids must match `[a-zA-Z0-9_-]+`, and nothing enforces that on a
+  hand-placed file. **Follow the variant the warning gives you** rather
+  than picking a repair yourself — the wrong one can leave the role
+  reachable under no name at all:
+  - no extra clause — both names are usable. Rename the file to
+    `<id>.json`, or change the `id` to the file's own name. Until then the
+    **file name** is a working handle: `delete <file name>` removes it.
+  - `… the file name is not a usable role id either` — e.g.
+    `my role.json`, rejected as `Invalid role id 'my role'.` Neither name
+    reaches the role. Renaming is the only fix.
+  - `… the id is not a usable role id` — the reverse, e.g. `"id": "my
+    role"` in `designer.json`. `delete designer` still works, and renaming
+    to `my role.json` would take that away. Change the `id`.
+  - `… neither is a usable role id` — pick one id that matches the pattern
+    and use it for the file name and the `id` together.
+  - an inner `id` equal to a built-in role's id — the file also shadows
+    that built-in, and `delete` on the listed id refuses it as built-in.
+    Renaming is the way out.
+- `more than one role file declares the same id` — both files load and
+  both appear in the list; `used` is the one that id resolves to
+  (readdir order, not a choice the user made) and `ignored` lists the
+  rest. Give each role a distinct id, or remove the extra file.
+
+Ask the user for the warning line rather than guessing which of the two
+it is. Both only happen to hand-placed or hand-renamed files:
+`manageRoles` writes `config/roles/<role.id>.json`, so file name and
+`id` always agree.
+
 ## Marp slide PDF — empty / image / font issues
 
 ### Symptoms

package/assets/helps/google-calendar-collection.md

@@ -10,17 +10,22 @@ for deleting events, use the `google` tool — see
 [The `google` tool](google.md). There is no bundled calendar collection: you
 author the schema when the user asks for one.
 
-## Both directions, but only one of them automatic
+## Both directions
 
 | Direction | How | When it runs |
 | --- | --- | --- |
 | Google → collection | the `googleCalendar` block | hourly, on creation, and on the **Sync** button |
-| collection → Google | the **Push to Google** button in the collection view | only when the user clicks it |
+| collection → Google | the **Push to Google** button | whenever the user clicks it |
+| collection → Google | `"autoPush": true` in the block | hourly, immediately before each pull |
 
-There is no automatic write-back and no setting that enables one. If a user
-asks for "two-way sync", tell them plainly: the pull is automatic, the push is
-a button they press. Do not go looking for a config key for it — there isn't
-one, and hunting for it is what makes this conversation go in circles.
+When a user asks for "two-way sync", `autoPush` is the answer: set it and each
+scheduled run pushes local edits up and then pulls Google's changes down, as one
+cycle. Without it the pull is automatic and the push is a button they must
+remember to press — which is why the order used to matter so much.
+
+It is **opt-in and off by default**, and that is deliberate: a push writes to a
+calendar other people may be reading, so turning it on is the user's call. Ask
+before you add it.
 
 ## Requirements
 
@@ -45,7 +50,8 @@ it isn't, sync silently does nothing until they link it in settings.
 
   "googleCalendar": {
     "calendarId": "primary",
-    "map": { "title": "summary", "on": "start", "until": "end" }
+    "map": { "title": "summary", "on": "start", "until": "end" },
+    "autoPush": true
   }
 }
 ```
@@ -58,9 +64,20 @@ it isn't, sync silently does nothing until they link it in settings.
   names suit the collection; the map absorbs the difference. Map at least one
   field: an empty map syncs records that carry only the event id, so the user
   would see rows with no content.
+- `autoPush` — push local edits on the sync schedule, just before each pull.
+  Omit it (the default) and the push stays a button. See "Both directions".
+
+Mappable event fields: `summary`, `start`, `end`, `description`, `location`,
+`htmlLink`, `colorId`, `status`.
+
+`description` is the event body, and Google stores limited **HTML** in it. It is
+kept verbatim — mirroring it through a plain-text field and pushing it back would
+strip the user's formatting. Give it a `text` field, and do not "clean it up" on
+the way in.
 
-Mappable event fields: `summary`, `start`, `end`, `htmlLink`, `colorId`,
-`status`.
+Mapping a column the user already filled by hand (a `notes` column, say) onto
+`description` means the next push sends that text to Google. That is usually what
+they want, but say so before you write the map.
 
 ## The primary field is the event id
 
@@ -82,8 +99,10 @@ the calendar day view then draws each record as a proportional time block.
 
 ## What sync does
 
-- New or edited events are written, keyed by event id (existing records are
-  replaced in place).
+- New or edited events are written, keyed by event id. Only the mapped columns
+  are overwritten: a column the map does not name (a local note the user keeps
+  next to the event) survives the pull. The flip side is that a field you REMOVE
+  from `map` keeps its last synced value rather than disappearing.
 - Events deleted in Google are **deleted** from the collection.
 - Only what changed since the last run is fetched, so a big calendar stays
   cheap after the first sync.
@@ -100,10 +119,10 @@ them like any other.
 The collection view has a **Push to Google** button next to Sync. It creates
 events for records added locally and updates events for records edited locally.
 
-**Order matters, and this is the one thing to warn users about.** A pull
-overwrites a locally edited record as soon as Google reports any change to that
-event. So: push first, then sync. Syncing first can discard the edit that was
-waiting to be pushed.
+**Order matters when the push is manual.** A pull overwrites a locally edited
+record as soon as Google reports any change to that event, so: push first, then
+sync. Syncing first can discard the edit that was waiting to be pushed. This is
+exactly the trap `autoPush` closes — it runs the two in that order for the user.
 
 What the button does and deliberately does not do:
 
@@ -115,9 +134,13 @@ What the button does and deliberately does not do:
   The count is reported so the user knows it was skipped; deleting for real is
   the `google` tool's `calendarDeleteEvent`, after confirming with them.
 - **Skips a record edited on both sides** and reports it, rather than picking a
-  winner. The user resolves it by editing one side to match.
-- Pushes only `summary`, `start`, `end` and `colorId` — `htmlLink` and `status`
-  are read-only in Google, so a column mapped to either is ignored.
+  winner. The user resolves it by editing one side to match. Under `autoPush`
+  the pull that follows leaves that record alone too, so the local edit is not
+  destroyed while it waits — the cost is that the record stays behind Google
+  until someone resolves it, and the host logs which records those are.
+- Pushes `summary`, `start`, `end`, `description`, `location` and `colorId` —
+  everything the pull can read except `htmlLink` and `status`, which are
+  read-only in Google, so a column mapped to either is ignored.
 
 Reasons a record can be reported as skipped:
 

package/dist/collection/core/schemaZ.d.ts

@@ -504,7 +504,7 @@ export declare const AgentIngestZ: z.ZodObject<{
 /** The Google event fields a collection may pull from. `id` is absent on
  *  purpose — it always lands in the primary field, since upsert-by-event-id
  *  is what makes the sync idempotent. */
-export declare const GOOGLE_CALENDAR_SOURCE_FIELDS: readonly ["summary", "start", "end", "htmlLink", "colorId", "status"];
+export declare const GOOGLE_CALENDAR_SOURCE_FIELDS: readonly ["summary", "start", "end", "htmlLink", "colorId", "status", "description", "location"];
 /** Marks a collection as the destination of the LLM-free Google Calendar
  *  sync (#2095). `map` is collectionField → Google event field, so the user's
  *  collection keeps whatever field names it already uses. */
@@ -517,7 +517,10 @@ export declare const GoogleCalendarSyncZ: z.ZodObject<{
         htmlLink: "htmlLink";
         colorId: "colorId";
         status: "status";
+        description: "description";
+        location: "location";
     }>>;
+    autoPush: z.ZodOptional<z.ZodBoolean>;
 }, z.core.$strip>;
 /** `ingest` is a discriminated union on `kind`: the three declarative
  *  retrievers fetch-and-map; `agent` dispatches a hidden worker. Optional on
@@ -1102,7 +1105,10 @@ declare const CollectionObjectZ: z.ZodObject<{
             htmlLink: "htmlLink";
             colorId: "colorId";
             status: "status";
+            description: "description";
+            location: "location";
         }>>;
+        autoPush: z.ZodOptional<z.ZodBoolean>;
     }, z.core.$strip>>;
     dynamicIcon: z.ZodOptional<z.ZodObject<{
         source: z.ZodObject<{
@@ -1578,7 +1584,10 @@ export declare const CollectionSchemaZ: z.ZodPreprocess<z.ZodObject<{
             htmlLink: "htmlLink";
             colorId: "colorId";
             status: "status";
+            description: "description";
+            location: "location";
         }>>;
+        autoPush: z.ZodOptional<z.ZodBoolean>;
     }, z.core.$strip>>;
     dynamicIcon: z.ZodOptional<z.ZodObject<{
         source: z.ZodObject<{

package/dist/collection/registry/server/index.cjs

@@ -4,9 +4,9 @@ const require_dist = require("../../../dist-pWpC-b04.cjs");
 const require_atomic = require("../../../atomic-C_7YpMiM.cjs");
 const require_relPath = require("../../../relPath-CgGi4-Nv.cjs");
 const require_utils_fetch = require("../../../utils/fetch.cjs");
-const require_discovery = require("../../../discovery-DYcR83qx.cjs");
+const require_discovery = require("../../../discovery-NRy3tyUA.cjs");
 const require_templatePath = require("../../../templatePath-27vUZowm.cjs");
-const require_server = require("../../../server-l4TZ5Lbf.cjs");
+const require_server = require("../../../server-7U-3DE2e.cjs");
 const require_skill_bridge_index = require("../../../skill-bridge/index.cjs");
 const require_types = require("../../../types-CNqkLT4M.cjs");
 let node_fs = require("node:fs");

package/dist/collection/registry/server/index.js

@@ -2,9 +2,9 @@ import { t as errorMessage } from "../../../dist-Cwk0e12G.js";
 import { t as writeFileAtomic } from "../../../atomic-DPpdrJzO.js";
 import { n as toPosixRelPath } from "../../../relPath-DW8MC8VO.js";
 import { fetchWithTimeout } from "../../../utils/fetch.js";
-import { K as collectionsRegistriesConfigPath, U as safeRecordId, X as log, r as loadCollection, s as CollectionSchemaZ, t as acceptParsedSchema } from "../../../discovery-_fjsluLx.js";
+import { K as collectionsRegistriesConfigPath, U as safeRecordId, X as log, r as loadCollection, s as CollectionSchemaZ, t as acceptParsedSchema } from "../../../discovery-B4CZvrXR.js";
 import { t as isSafeActionTemplatePath } from "../../../templatePath-k_WNbL_Q.js";
-import { g as ONE_SECOND_MS } from "../../../server-BlIrtGKl.js";
+import { g as ONE_SECOND_MS } from "../../../server-DdyIvFhz.js";
 import { claudeSkillDir, dataSkillDir, mirrorSkillWrite } from "../../../skill-bridge/index.js";
 import { n as parseRegistryIndex, r as isRecord, t as OFFICIAL_REGISTRY_NAME } from "../../../types-BKVZrtyc.js";
 import { readFileSync } from "node:fs";

package/dist/collection/server/index.cjs

@@ -1,8 +1,8 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 const require_calendarGrid = require("../../calendarGrid-CaS9er8i.cjs");
-const require_discovery = require("../../discovery-DYcR83qx.cjs");
+const require_discovery = require("../../discovery-NRy3tyUA.cjs");
 const require_templatePath = require("../../templatePath-27vUZowm.cjs");
-const require_server = require("../../server-l4TZ5Lbf.cjs");
+const require_server = require("../../server-7U-3DE2e.cjs");
 exports.BackendUnavailableError = require_discovery.BackendUnavailableError;
 exports.COMPUTED_TYPES = require_calendarGrid.COMPUTED_TYPES;
 exports.CollectionQueryZ = require_discovery.CollectionQueryZ;

package/dist/collection/server/index.js

@@ -1,5 +1,5 @@
 import { S as COMPUTED_TYPES } from "../../calendarGrid-CrGxeCOG.js";
-import { A as deleteItem, B as itemFilePath, C as compileCsvQuery, D as MAX_QUERY_ROWS, E as DEFAULT_QUERY_ROWS, F as resolveCreateItemId, H as resolveTemplatePath, I as writeItem, J as getWorkspaceRoot, L as SCHEMA_FILE, M as isRegularFile, N as listItems, O as BackendUnavailableError, P as readItem, Q as setCollectionChangePublisher, R as isContainedInRoot, T as CollectionQueryZ, U as safeRecordId, V as resolveDataDir, W as safeSlugName, X as log, Z as publishCollectionChange, _ as csvRowToItem, a as toDetail, b as encodeCsvRecordId, d as storeFor, h as MAX_CSV_ROWS, i as resolvePrimaryField, j as generateItemId, k as isBackendUnavailable, l as collectionWritable, m as projectItemFields, n as discoverCollections, o as toSummary, p as pageFromFullRead, q as configureCollectionHost, r as loadCollection, s as CollectionSchemaZ, t as acceptParsedSchema, u as readOnlyRefusal, v as decodeCsvRecordId, w as compileJsonlQuery, x as normalizeCsvValue, y as dedupeByRecordId, z as isContainedInWorkspace } from "../../discovery-_fjsluLx.js";
+import { A as deleteItem, B as itemFilePath, C as compileCsvQuery, D as MAX_QUERY_ROWS, E as DEFAULT_QUERY_ROWS, F as resolveCreateItemId, H as resolveTemplatePath, I as writeItem, J as getWorkspaceRoot, L as SCHEMA_FILE, M as isRegularFile, N as listItems, O as BackendUnavailableError, P as readItem, Q as setCollectionChangePublisher, R as isContainedInRoot, T as CollectionQueryZ, U as safeRecordId, V as resolveDataDir, W as safeSlugName, X as log, Z as publishCollectionChange, _ as csvRowToItem, a as toDetail, b as encodeCsvRecordId, d as storeFor, h as MAX_CSV_ROWS, i as resolvePrimaryField, j as generateItemId, k as isBackendUnavailable, l as collectionWritable, m as projectItemFields, n as discoverCollections, o as toSummary, p as pageFromFullRead, q as configureCollectionHost, r as loadCollection, s as CollectionSchemaZ, t as acceptParsedSchema, u as readOnlyRefusal, v as decodeCsvRecordId, w as compileJsonlQuery, x as normalizeCsvValue, y as dedupeByRecordId, z as isContainedInWorkspace } from "../../discovery-B4CZvrXR.js";
 import { i as isSafeTemplatePath, n as isSafeCustomViewI18nPath, r as isSafeCustomViewPath, t as isSafeActionTemplatePath } from "../../templatePath-k_WNbL_Q.js";
-import { A as buildCollectionActionSeedPrompt, C as validateRecordObject, D as enrichItems, E as runCollectionQuery, M as readCustomViewHtml, N as readCustomViewI18n, O as runQueryOverRows, P as readSkillTemplate, S as validateCollectionRecords, T as recordFieldProblem, _ as computeCollectionIcon, a as deleteCollection, b as applyMutateAction, c as computeSuccessor, d as isTriggerDue, f as maybeSpawnSuccessor, h as successorId, i as deleteCustomView, j as promptPathsFor, k as buildActionSeedPrompt, l as daysInMonth, m as resolveEvery, n as MAX_UNSELECTIVE_ITEMS, o as deleteCollectionRefusalMessage, p as parseCivil, r as makeManageCollectionTool, s as advanceTriggerDate, t as MAX_SCHEMA_ISSUES, u as formatCivil, v as buildWorkspaceOntology, w as compileRecordZ, x as firstMutateParamProblem, y as schemaRelations } from "../../server-BlIrtGKl.js";
+import { A as buildCollectionActionSeedPrompt, C as validateRecordObject, D as enrichItems, E as runCollectionQuery, M as readCustomViewHtml, N as readCustomViewI18n, O as runQueryOverRows, P as readSkillTemplate, S as validateCollectionRecords, T as recordFieldProblem, _ as computeCollectionIcon, a as deleteCollection, b as applyMutateAction, c as computeSuccessor, d as isTriggerDue, f as maybeSpawnSuccessor, h as successorId, i as deleteCustomView, j as promptPathsFor, k as buildActionSeedPrompt, l as daysInMonth, m as resolveEvery, n as MAX_UNSELECTIVE_ITEMS, o as deleteCollectionRefusalMessage, p as parseCivil, r as makeManageCollectionTool, s as advanceTriggerDate, t as MAX_SCHEMA_ISSUES, u as formatCivil, v as buildWorkspaceOntology, w as compileRecordZ, x as firstMutateParamProblem, y as schemaRelations } from "../../server-DdyIvFhz.js";
 export { BackendUnavailableError, COMPUTED_TYPES, CollectionQueryZ, CollectionSchemaZ, DEFAULT_QUERY_ROWS, MAX_CSV_ROWS, MAX_QUERY_ROWS, MAX_SCHEMA_ISSUES, MAX_UNSELECTIVE_ITEMS, SCHEMA_FILE, acceptParsedSchema, advanceTriggerDate, applyMutateAction, buildActionSeedPrompt, buildCollectionActionSeedPrompt, buildWorkspaceOntology, collectionWritable, compileCsvQuery, compileJsonlQuery, compileRecordZ, computeCollectionIcon, computeSuccessor, configureCollectionHost, csvRowToItem, daysInMonth, decodeCsvRecordId, dedupeByRecordId, deleteCollection, deleteCollectionRefusalMessage, deleteCustomView, deleteItem, discoverCollections, encodeCsvRecordId, enrichItems, firstMutateParamProblem, formatCivil, generateItemId, getWorkspaceRoot, isBackendUnavailable, isContainedInRoot, isContainedInWorkspace, isRegularFile, isSafeActionTemplatePath, isSafeCustomViewI18nPath, isSafeCustomViewPath, isSafeTemplatePath, isTriggerDue, itemFilePath, listItems, loadCollection, log, makeManageCollectionTool, maybeSpawnSuccessor, normalizeCsvValue, pageFromFullRead, parseCivil, projectItemFields, promptPathsFor, publishCollectionChange, readCustomViewHtml, readCustomViewI18n, readItem, readOnlyRefusal, readSkillTemplate, recordFieldProblem, resolveCreateItemId, resolveDataDir, resolveEvery, resolvePrimaryField, resolveTemplatePath, runCollectionQuery, runQueryOverRows, safeRecordId, safeSlugName, schemaRelations, setCollectionChangePublisher, storeFor, successorId, toDetail, toSummary, validateCollectionRecords, validateRecordObject, writeItem };

package/dist/collection-watchers/index.cjs

@@ -2,8 +2,8 @@ Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 const require_calendarGrid = require("../calendarGrid-CaS9er8i.cjs");
 const require_promptSafety = require("../promptSafety-FD8cQn3e.cjs");
 require("../collection/index.cjs");
-const require_discovery = require("../discovery-DYcR83qx.cjs");
-const require_server = require("../server-l4TZ5Lbf.cjs");
+const require_discovery = require("../discovery-NRy3tyUA.cjs");
+const require_server = require("../server-7U-3DE2e.cjs");
 const require_notifier = require("../notifier-tMsAXyXp.cjs");
 let node_fs_promises = require("node:fs/promises");
 //#region src/collection-watchers/config.ts

package/dist/collection-watchers/index.js

@@ -1,8 +1,8 @@
 import { k as fieldText } from "../calendarGrid-CrGxeCOG.js";
 import { E as whenMatches, f as itemIsDone } from "../promptSafety-C--op_6a.js";
 import "../collection/index.js";
-import { B as itemFilePath, Z as publishCollectionChange, d as storeFor, n as discoverCollections, r as loadCollection } from "../discovery-_fjsluLx.js";
-import { d as isTriggerDue, f as maybeSpawnSuccessor } from "../server-BlIrtGKl.js";
+import { B as itemFilePath, Z as publishCollectionChange, d as storeFor, n as discoverCollections, r as loadCollection } from "../discovery-B4CZvrXR.js";
+import { d as isTriggerDue, f as maybeSpawnSuccessor } from "../server-DdyIvFhz.js";
 import { d as publish, m as updateForPlugin, n as clear, s as listAll } from "../notifier-BdA5qzhe.js";
 import { access } from "node:fs/promises";
 //#region src/collection-watchers/config.ts

package/dist/{discovery-_fjsluLx.js → discovery-B4CZvrXR.js}

@@ -2183,8 +2183,16 @@ var GoogleCalendarSyncZ = z.object({
 		"end",
 		"htmlLink",
 		"colorId",
-		"status"
-	])).refine((map) => Object.keys(map).length > 0, { message: "map at least one field — a `googleCalendar` sync with an empty map writes records that carry only the event id" })
+		"status",
+		"description",
+		"location"
+	])).refine((map) => Object.keys(map).length > 0, { message: "map at least one field — a `googleCalendar` sync with an empty map writes records that carry only the event id" }),
+	/** Run the push on the sync schedule too, immediately before each pull, so
+	*  local edits reach Google without anyone pressing a button (#2620).
+	*
+	*  Opt-in and absent by default: a push writes to a calendar other people may
+	*  read, so turning it on is the user's decision, not a default. */
+	autoPush: z.boolean().optional()
 });
 /** `ingest` is a discriminated union on `kind`: the three declarative
 *  retrievers fetch-and-map; `agent` dispatches a hidden worker. Optional on
@@ -2666,4 +2674,4 @@ function toDetail(collection) {
 //#endregion
 export { skillsStagingDir as $, deleteItem as A, itemFilePath as B, compileCsvQuery as C, MAX_QUERY_ROWS as D, DEFAULT_QUERY_ROWS as E, resolveCreateItemId as F, archiveDir as G, resolveTemplatePath as H, writeItem as I, getWorkspaceRoot as J, collectionsRegistriesConfigPath as K, SCHEMA_FILE as L, isRegularFile as M, listItems as N, BackendUnavailableError as O, readItem as P, setCollectionChangePublisher as Q, isContainedInRoot as R, queryCsv as S, CollectionQueryZ as T, safeRecordId as U, resolveDataDir as V, safeSlugName as W, log as X, isPresetSlug as Y, publishCollectionChange as Z, csvRowToItem as _, toDetail as a, encodeCsvRecordId as b, resolveMutateSet as c, storeFor as d, createForwardingLogger as et, checkpointSqliteDatabase as f, cacheDir as g, MAX_CSV_ROWS as h, resolvePrimaryField as i, generateItemId as j, isBackendUnavailable as k, collectionWritable as l, projectItemFields as m, discoverCollections as n, toSummary as o, pageFromFullRead as p, configureCollectionHost as q, loadCollection as r, CollectionSchemaZ as s, acceptParsedSchema as t, createHostSlot as tt, readOnlyRefusal as u, decodeCsvRecordId as v, compileJsonlQuery as w, normalizeCsvValue as x, dedupeByRecordId as y, isContainedInWorkspace as z };
 
-//# sourceMappingURL=discovery-_fjsluLx.js.map
+//# sourceMappingURL=discovery-B4CZvrXR.js.map