neuro-vault-mcp 10.0.2 → 11.0.0

package/README.md

@@ -142,7 +142,7 @@ Two vaults cannot share the same directory basename — the basename doubles as
 With multiple vaults registered:
 
 - **Every tool** accepts an optional `vault: "<name>"` parameter to target a specific vault.
-- **`search_notes`, `query_notes`, `get_vault_overview`, `list_tags`, and `list_properties`** fan out across all registered vaults when `vault` is omitted. The response shape switches to `results_by_vault: [...]` (one entry per vault) plus `skipped_vaults: [...]` for any vault the tool could not reach and `failed_vaults: [...]` for per-vault runtime errors (`{ vault, error: { code, message, details? } }`). A single failed vault does not abort the whole call.
+- **`search_notes`, `query_notes`, `get_vault_overview`, and `list_tags`** fan out across all registered vaults when `vault` is omitted. The response shape switches to `results_by_vault: [...]` (one entry per vault) plus `skipped_vaults: [...]` for any vault the tool could not reach and `failed_vaults: [...]` for per-vault runtime errors (`{ vault, error: { code, message, details? } }`). A single failed vault does not abort the whole call.
 - **All other tools** (writes, reads of specific paths, single-vault diagnostics) require an explicit `vault` in multi-vault mode. Omitting it returns `VAULT_REQUIRED`.
 - **Semantic fan-out** silently skips vaults whose Smart Connections `.smart-env/multi/` index is unavailable. Targeting such a vault explicitly with `vault: "<name>"` returns `SEMANTIC_INDEX_NOT_FOUND`.
 
@@ -163,7 +163,7 @@ For other clients (Cursor / Windsurf / npx), see [docs/guide/installation.md](./
 User guide lives in [`docs/guide/`](./docs/guide/README.md):
 
 - [Installation](./docs/guide/installation.md)
-- [Semantic Search](./docs/guide/semantic-search.md) — `search_notes`, `get_similar_notes`, `find_duplicates`, `get_stats`
+- [Semantic Search](./docs/guide/semantic-search.md) — `search_notes`, `get_similar_notes`, `find_duplicates`
 - [Vault Operations](./docs/guide/vault-operations.md) — note CRUD, daily notes, properties, tags, structured queries (`query_notes`), vault snapshot (`get_vault_overview`)
 - [Routing Between Tools](./docs/guide/routing.md)
 - [Configuration](./docs/guide/configuration.md) — CLI args, troubleshooting, limitations, development

package/dist/cli.d.ts

@@ -161,13 +161,6 @@ interface SetPropertyInput {
     value: PropertyValue;
     type?: PropertyType;
 }
-interface ReadPropertyInput {
-    identifier: NoteIdentifier;
-    name: string;
-}
-interface ReadPropertyResult {
-    value: PropertyValue;
-}
 interface RemovePropertyInput {
     identifier: NoteIdentifier;
     name: string;
@@ -184,7 +177,6 @@ interface VaultProvider {
     createNote(input: CreateNoteInput): Promise<CreateNoteResult>;
     readDaily(): Promise<DailyNoteResult>;
     setProperty(input: SetPropertyInput): Promise<void>;
-    readProperty(input: ReadPropertyInput): Promise<ReadPropertyResult>;
     removeProperty(input: RemovePropertyInput): Promise<void>;
     listProperties(): Promise<PropertyListEntry[]>;
     listTags(): Promise<TagListEntry[]>;

package/dist/cli.js

@@ -14180,6 +14180,22 @@ function coerceFieldValue(schema, value, fieldName = "value") {
     }
     return value;
   }
+  if (inner instanceof external_exports.ZodArray && typeof value === "string") {
+    let parsed;
+    try {
+      parsed = JSON.parse(value);
+    } catch {
+      throw new CoerceError(
+        fieldName,
+        `expected array or JSON-string of one, failed to parse: ${JSON.stringify(value)}`
+      );
+    }
+    if (Array.isArray(parsed)) return parsed;
+    throw new CoerceError(
+      fieldName,
+      `expected array, parsed JSON resolved to ${describeJsonShape(parsed)}`
+    );
+  }
   return value;
 }
 function wrapField(field, fieldName) {
@@ -14530,7 +14546,7 @@ function normalizeScanPrefix(raw) {
 }
 
 // src/lib/obsidian/frontmatter.ts
-import { parse as parseYaml } from "yaml";
+import { parse as parseYaml, stringify as stringifyYaml } from "yaml";
 
 // src/lib/obsidian/in-place-edit.ts
 var FRONTMATTER_OPEN = /^---[ \t]*\r?\n/;
@@ -14611,6 +14627,11 @@ function splitFrontmatter(raw) {
   }
   return { frontmatter: parsed, content };
 }
+function serializeFrontmatter(fm) {
+  return `---
+${stringifyYaml(fm)}---
+`;
+}
 
 // src/lib/obsidian/wikilink.ts
 var WIKILINK_RE = /\[\[(.+?)\]\]/g;
@@ -15762,70 +15783,6 @@ function buildGetSimilarNotesTool(deps) {
   };
 }
 
-// src/modules/semantic/tools/get-stats.ts
-function readEmbeddingDimension(sources) {
-  let dimension;
-  for (const source of sources) {
-    if (dimension === void 0) {
-      dimension = source.embedding.length;
-      continue;
-    }
-    if (source.embedding.length !== dimension) {
-      throw new ToolHandlerError(
-        "DEPENDENCY_ERROR",
-        "Loaded corpus contains mixed embedding dimensions",
-        {
-          details: {
-            expectedDimension: dimension,
-            actualDimension: source.embedding.length,
-            path: source.path
-          }
-        }
-      );
-    }
-  }
-  return dimension ?? 0;
-}
-function buildGetStatsTool(deps) {
-  const { registry: registry2, modelKey } = deps;
-  const inputSchema = external_exports.object({ ...vaultParamShape(registry2) });
-  return {
-    name: "get_stats",
-    title: "Get Stats",
-    description: "Report corpus and embedding statistics." + describeMultiVault(
-      registry2,
-      'Pass `vault: "<name>"` to target a specific vault when multiple are registered.'
-    ),
-    inputSchema,
-    handler: async (input) => {
-      const entry = resolveSemanticVault(input, registry2, {
-        tool: "get_stats"
-      });
-      const corpus = entry.corpus;
-      try {
-        const { sources } = await corpus.snapshot();
-        let totalBlocks = 0;
-        for (const source of sources.values()) {
-          totalBlocks += source.blocks.length;
-        }
-        return {
-          vault: entry.name,
-          totalNotes: sources.size,
-          totalBlocks,
-          embeddingDimension: readEmbeddingDimension(sources.values()),
-          modelKey
-        };
-      } catch (error48) {
-        if (error48 instanceof ToolHandlerError) throw error48;
-        throw new ToolHandlerError("DEPENDENCY_ERROR", "Failed to get corpus stats", {
-          details: { modelKey, operation: "get_stats" },
-          cause: error48
-        });
-      }
-    }
-  };
-}
-
 // src/lib/fan-out.ts
 function findFatalRejection(settled) {
   for (const outcome of settled) {
@@ -16354,8 +16311,7 @@ function buildSemanticTools(deps) {
   return [
     registerTool(buildSearchNotesTool(deps)),
     registerTool(buildGetSimilarNotesTool(deps)),
-    registerTool(buildFindDuplicatesTool(deps)),
-    registerTool(buildGetStatsTool(deps))
+    registerTool(buildFindDuplicatesTool(deps))
   ];
 }
 
@@ -16472,8 +16428,7 @@ function normalizePath(raw) {
     throw invalidArgument(err.message, "path");
   }
 }
-var VALID_FIELDS = ["frontmatter", "content"];
-var DEFAULT_FIELDS = ["frontmatter", "content"];
+var VALID_CONTENT_MODES = ["full", "preview", "frontmatter"];
 function validateReadNotesInput(input) {
   let paths;
   if (typeof input.paths === "string") {
@@ -16489,24 +16444,18 @@ function validateReadNotesInput(input) {
   if (paths.length < 1 || paths.length > 50) {
     throw invalidArgument("paths must contain between 1 and 50 entries", "paths");
   }
-  let fields;
-  if (input.fields === void 0) {
-    fields = DEFAULT_FIELDS;
+  let content;
+  if (input.content === void 0) {
+    content = void 0;
+  } else if (VALID_CONTENT_MODES.includes(input.content)) {
+    content = input.content;
   } else {
-    if (!Array.isArray(input.fields) || input.fields.length === 0) {
-      throw invalidArgument("fields must be a non-empty array when provided", "fields");
-    }
-    for (const f of input.fields) {
-      if (!VALID_FIELDS.includes(f)) {
-        throw invalidArgument(
-          `unknown field '${String(f)}'; allowed: ${VALID_FIELDS.join(", ")}`,
-          "fields"
-        );
-      }
-    }
-    fields = input.fields;
+    throw invalidArgument(
+      `unknown content mode '${String(input.content)}'; allowed: ${VALID_CONTENT_MODES.join(", ")}`,
+      "content"
+    );
   }
-  return { paths, fields };
+  return { paths, content };
 }
 
 // src/modules/operations/tools/create-note.ts
@@ -16517,12 +16466,13 @@ function buildCreateNoteTool(deps) {
     name: external_exports.string().optional(),
     path: external_exports.string().optional(),
     content: external_exports.string().optional(),
+    frontmatter: external_exports.record(external_exports.string(), external_exports.unknown()).optional(),
     overwrite: external_exports.boolean().optional()
   });
   return {
     name: "create_note",
     title: "Create Note",
-    description: "Create a new note. Provide `name` or `path` (exactly one). Optionally provide `content` (raw markdown for the note body and frontmatter). Paths without an extension are treated as `.md` notes.\n\nBefore composing `content`, sample 1\u20132 similar notes from the vault to mimic existing conventions instead of inventing your own. A reliable pattern: `search_notes` for the topic (or `query_notes` with a tag/folder filter that fits) to find candidates, then `read_notes` on the closest match to inspect its frontmatter shape, tag values, heading layout, and folder placement. Match those conventions \u2014 the user almost always prefers a new note that looks like its neighbours. Be especially careful with the `type` frontmatter field: vaults tend to use a small closed set (e.g. project / task / idea / reflection / daily / review / inbox / resource); pick from what other notes use rather than coining a new value.\n\nTemplates are not handled by this tool \u2014 render any template yourself (Obsidian Core Templates, Templater, or anything else) and pass the result as `content`." + describeMultiVault(
+    description: "Create a new note. Provide `name` or `path` (exactly one). Optionally provide `content` (raw markdown for the note body) and/or `frontmatter` (an object of frontmatter properties, serialized to a YAML block and prepended to the note \u2014 prefer this over hand-writing a `---` block inside `content`; it quotes `[[wikilinks]]`, formats dates, and renders tag lists correctly). If `content` also begins with its own `---` block, the two are merged key-by-key and the `frontmatter` parameter wins on any key collision (the body is kept). Paths without an extension are treated as `.md` notes.\n\nBefore composing `content`, sample 1\u20132 similar notes from the vault to mimic existing conventions instead of inventing your own. A reliable pattern: `search_notes` for the topic (or `query_notes` with a tag/folder filter that fits) to find candidates, then `read_notes` on the closest match to inspect its frontmatter shape, tag values, heading layout, and folder placement. Match those conventions \u2014 the user almost always prefers a new note that looks like its neighbours. Be especially careful with the `type` frontmatter field: vaults tend to use a small closed set (e.g. project / task / idea / reflection / daily / review / inbox / resource); pick from what other notes use rather than coining a new value.\n\nTemplates are not handled by this tool \u2014 render any template yourself (Obsidian Core Templates, Templater, or anything else) and pass the result as `content`." + describeMultiVault(
       registry2,
       'Pass `vault: "<name>"` to target a specific vault when multiple are registered.'
     ) + " If a note with this path/name might already exist and the user has not explicitly asked to replace it, ask the user before passing `overwrite: true` \u2014 overwrite is destructive. Default behavior fails when the note exists.",
@@ -16548,7 +16498,14 @@ function buildCreateNoteTool(deps) {
         }
       }
       if (input.overwrite !== void 0) passthrough.overwrite = input.overwrite;
-      if (input.content !== void 0) passthrough.content = input.content;
+      const hasFrontmatter = input.frontmatter !== void 0 && Object.keys(input.frontmatter).length > 0;
+      if (hasFrontmatter) {
+        const { frontmatter: contentFm, content: body } = splitFrontmatter(input.content ?? "");
+        const merged = { ...contentFm ?? {}, ...input.frontmatter };
+        passthrough.content = serializeFrontmatter(merged) + body;
+      } else if (input.content !== void 0) {
+        passthrough.content = input.content;
+      }
       const result = await entry.provider.createNote(passthrough);
       return { vault: entry.name, ...result };
     }
@@ -16739,7 +16696,7 @@ function buildGetVaultOverviewTool(deps) {
   return {
     name: "get_vault_overview",
     title: "Get Vault Overview",
-    description: "Returns a single snapshot of vault structure: top-level folders with note counts, top tags, frontmatter properties, total note count, and the top 10 notes by inbound wikilinks. Call this once at the start of a session to orient yourself before reaching for `list_tags`, `list_properties`, or exploratory `query_notes`." + describeMultiVault(
+    description: "Returns a single snapshot of vault structure: top-level folders with note counts, top tags, frontmatter properties, total note count, and the top 10 notes by inbound wikilinks. Call this once at the start of a session to orient yourself before reaching for `list_tags` or exploratory `query_notes`." + describeMultiVault(
       registry2,
       'In multi-vault mode, omit `vault:` to fan out across all registered vaults \u2014 the response shape switches to `results_by_vault: [...]` with `skipped_vaults: [...]`. Pass `vault: "<name>"` to target a specific vault when multiple are registered.'
     ),
@@ -16755,35 +16712,8 @@ function buildGetVaultOverviewTool(deps) {
   };
 }
 
-// src/modules/operations/tools/list-properties.ts
-async function runForEntry(entry) {
-  const results = await entry.provider.listProperties();
-  return { results };
-}
-function buildListPropertiesTool(deps) {
-  const { registry: registry2 } = deps;
-  const inputSchema = external_exports.object({ ...vaultParamShape(registry2) });
-  return {
-    name: "list_properties",
-    title: "List Properties",
-    description: "List all frontmatter properties used across the vault, sorted by occurrence count desc. Returns `{ vault, results: [{name, count}] }`. Useful for understanding the vault's metadata ontology." + describeMultiVault(
-      registry2,
-      'In multi-vault mode, omit `vault:` to fan out across all registered vaults \u2014 the response shape switches to `results_by_vault: [...]`. Pass `vault: "<name>"` to target a specific vault.'
-    ),
-    inputSchema,
-    handler: async (input) => {
-      if (input.vault === void 0 && registry2.isMulti()) {
-        return await runFanOut(registry2, runForEntry);
-      }
-      const entry = resolveVault(input, registry2, { tool: "list_properties" });
-      const { results } = await runForEntry(entry);
-      return { vault: entry.name, results };
-    }
-  };
-}
-
 // src/modules/operations/tools/list-tags.ts
-async function runForEntry2(entry) {
+async function runForEntry(entry) {
   const results = await entry.provider.listTags();
   return { results };
 }
@@ -16800,10 +16730,10 @@ function buildListTagsTool(deps) {
     inputSchema,
     handler: async (input) => {
       if (input.vault === void 0 && registry2.isMulti()) {
-        return await runFanOut(registry2, runForEntry2);
+        return await runFanOut(registry2, runForEntry);
       }
       const entry = resolveVault(input, registry2, { tool: "list_tags" });
-      const { results } = await runForEntry2(entry);
+      const { results } = await runForEntry(entry);
       return { vault: entry.name, results };
     }
   };
@@ -16953,26 +16883,39 @@ function formatLocalDate(d) {
   return `${y}-${m}-${day}`;
 }
 
+// src/modules/operations/preview-body.ts
+var PREVIEW_CHAR_CAP = 500;
+var PREVIEW_MARKER = "\u2026";
+function previewBody(body) {
+  if (body.length <= PREVIEW_CHAR_CAP) {
+    return { content: body, truncated: false };
+  }
+  const segment = body.slice(0, PREVIEW_CHAR_CAP + 1);
+  const lastWs = Math.max(segment.lastIndexOf(" "), segment.lastIndexOf("\n"));
+  const cutAt = lastWs !== -1 ? lastWs : PREVIEW_CHAR_CAP;
+  const slice = body.slice(0, cutAt).trimEnd();
+  return { content: slice + PREVIEW_MARKER, truncated: true };
+}
+
 // src/modules/operations/tools/read-notes.ts
-var readNotesFieldSchema = external_exports.enum(["frontmatter", "content"]);
 function buildReadNotesTool(deps) {
   const { registry: registry2 } = deps;
   const inputSchema = external_exports.object({
     ...vaultParamShape(registry2),
     paths: external_exports.union([external_exports.string().min(1), external_exports.array(external_exports.string()).min(1).max(50)]),
-    fields: external_exports.array(readNotesFieldSchema).min(1).optional()
+    content: external_exports.enum(["full", "preview", "frontmatter"]).optional()
   });
   return {
     name: "read_notes",
     title: "Read Notes",
-    description: "Read one or more notes in one call. `paths` is a vault-relative POSIX path string or an array of 1\u201350 such paths; duplicates are de-duplicated and results returned in input order. `fields` projects which parts of each note to return \u2014 choose from `frontmatter` and `content`; default `['frontmatter','content']`. One missing or unreadable path does not fail the others \u2014 per-item errors come back inline. A single MCP roundtrip with parallel disk reads. Reads are direct from disk and do not require Obsidian to be running." + describeMultiVault(
+    description: "Read one or more notes in one call. `paths` is a vault-relative POSIX path string or an array of 1\u201350 such paths; duplicates are de-duplicated and results returned in input order. `content` controls how much of each note's body comes back: `full` returns the complete body, `preview` returns a bounded slice plus a `truncated` flag, `frontmatter` returns no body at all. Frontmatter is always returned. The default is derived from the number of distinct paths: one path \u2192 `full`, two or more \u2192 `preview`; passing `content` explicitly overrides this. Re-read a previewed note with `content: 'full'` before citing or editing it. One missing or unreadable path does not fail the others \u2014 per-item errors come back inline. A single MCP roundtrip with parallel disk reads. Reads are direct from disk and do not require Obsidian to be running." + describeMultiVault(
       registry2,
       'Pass `vault: "<name>"` to target a specific vault when multiple are registered.'
     ),
     inputSchema,
     handler: async (input) => {
       const entry = resolveVault(input, registry2, { tool: "read_notes" });
-      const { paths, fields } = validateReadNotesInput(input);
+      const { paths, content } = validateReadNotesInput(input);
       const seen = /* @__PURE__ */ new Set();
       const deduped = [];
       for (const p of paths) {
@@ -16981,6 +16924,8 @@ function buildReadNotesTool(deps) {
           deduped.push(p);
         }
       }
+      const effective = content ?? (deduped.length === 1 ? "full" : "preview");
+      const fields = effective === "frontmatter" ? ["frontmatter"] : ["frontmatter", "content"];
       const slots = deduped.map((raw) => {
         try {
           const normalized = normalizePath(raw);
@@ -17000,13 +16945,15 @@ function buildReadNotesTool(deps) {
           return item;
         }
         const out = {
-          path: item.path
+          path: item.path,
+          frontmatter: item.frontmatter
         };
-        if (fields.includes("frontmatter")) {
-          out.frontmatter = item.frontmatter;
-        }
-        if (fields.includes("content")) {
+        if (effective === "full") {
           out.content = item.content;
+        } else if (effective === "preview") {
+          const { content: c, truncated } = previewBody(item.content);
+          out.content = c;
+          out.truncated = truncated;
         }
         return out;
       });
@@ -17021,35 +16968,6 @@ function buildReadNotesTool(deps) {
   };
 }
 
-// src/modules/operations/tools/read-property.ts
-function buildReadPropertyTool(deps) {
-  const { registry: registry2 } = deps;
-  const inputSchema = external_exports.object({
-    ...vaultParamShape(registry2),
-    name: external_exports.string().optional(),
-    path: external_exports.string().optional(),
-    key: external_exports.string()
-  });
-  return {
-    name: "read_property",
-    title: "Read Property",
-    description: "Read a frontmatter property value from a note. Provide `name` or `path`, plus `key`. Returns `{ vault, value }`. Use `read_notes` if you need the full frontmatter or accurate type information." + describeMultiVault(
-      registry2,
-      'Pass `vault: "<name>"` to target a specific vault when multiple are registered.'
-    ),
-    inputSchema,
-    handler: async (input) => {
-      const entry = resolveVault(input, registry2, { tool: "read_property" });
-      const identifier = resolveIdentifier(input.name, input.path);
-      if (!input.key || input.key.trim() === "") {
-        throw invalidArgument("key must not be empty", "key");
-      }
-      const result = await entry.provider.readProperty({ identifier, name: input.key.trim() });
-      return { vault: entry.name, ...result };
-    }
-  };
-}
-
 // src/modules/operations/tools/remove-property.ts
 function buildRemovePropertyTool(deps) {
   const { registry: registry2 } = deps;
@@ -17120,9 +17038,7 @@ function buildOperationsTools(deps) {
     registerTool(buildEditNoteTool(deps)),
     registerTool(buildReadDailyTool(deps)),
     registerTool(buildSetPropertyTool(deps)),
-    registerTool(buildReadPropertyTool(deps)),
     registerTool(buildRemovePropertyTool(deps)),
-    registerTool(buildListPropertiesTool(deps)),
     registerTool(buildListTagsTool(deps)),
     registerTool(buildGetNoteLinksTool(deps)),
     registerTool(buildGetVaultOverviewTool(deps))
@@ -17423,13 +17339,6 @@ var ObsidianCLIProvider = class {
     tokens.push(identifierToArg(input.identifier));
     await this.runCommand("property:set", tokens);
   }
-  async readProperty(input) {
-    const { stdout } = await this.runCommand("property:read", [
-      `name=${input.name}`,
-      identifierToArg(input.identifier)
-    ]);
-    return { value: this.parsePropertyValue(stdout) };
-  }
   async removeProperty(input) {
     try {
       await this.runCommand("property:remove", [
@@ -17451,20 +17360,6 @@ var ObsidianCLIProvider = class {
     const { stdout } = await this.runCommand("tags", ["counts", "sort=count", "format=json"]);
     return this.parseJsonList(stdout, "tags");
   }
-  // Best-effort: a `text` property whose value happens to be "true" or "42"
-  // will be coerced to boolean/number. Callers needing ground-truth types should
-  // use read_notes and parse frontmatter directly.
-  parsePropertyValue(stdout) {
-    const trimmed = stdout.trim();
-    if (trimmed === "") return "";
-    if (trimmed === "true") return true;
-    if (trimmed === "false") return false;
-    if (/^-?\d+(\.\d+)?$/.test(trimmed)) return Number(trimmed);
-    if (trimmed.includes("\n")) {
-      return trimmed.split("\n").map((s) => s.trim()).filter((s) => s.length > 0);
-    }
-    return trimmed;
-  }
   serializeValue(value) {
     if (Array.isArray(value)) return value.map((v) => String(v)).join(",");
     return String(value);
@@ -17533,7 +17428,7 @@ var ObsidianCLIProvider = class {
         { details: { stderr }, cause: error48 }
       );
     }
-    if ((command === "property:read" || command === "property:remove") && /property not found|not set/i.test(stderr)) {
+    if (command === "property:remove" && /property not found|not set/i.test(stderr)) {
       return new ToolHandlerError(
         "PROPERTY_NOT_FOUND",
         `Property not found: ${stderr.trim() || "unknown"}`,
@@ -17641,7 +17536,7 @@ This vault is the user's personal knowledge base \u2014 planning notes, brainsto
 
 You don't know on your own how the user scopes notes for the current project \u2014 the same vault is typically connected to many, and different users organise differently (a tag, a folder, a frontmatter property like \`project\`, or a combination). The user's project-level instructions should name that scope and tell you how to query for it. If they don't, you have three ways forward, in order of preference:
 
-1. **Probe the vault structure** via \`get_vault_overview\` \u2014 a single-call snapshot of top-level folders with counts, top tags, frontmatter properties with inferred types, and the top-linked notes. Common conventions (a \`project\` frontmatter field, a \`Projects/\` folder, a recurring tag) usually surface immediately. Fall back to \`list_tags\`, \`list_properties\`, or exploratory \`query_notes\` only when the overview misses what you need.
+1. **Probe the vault structure** via \`get_vault_overview\` \u2014 a single-call snapshot of top-level folders with counts, top tags, frontmatter properties with inferred types, and the top-linked notes. Common conventions (a \`project\` frontmatter field, a \`Projects/\` folder, a recurring tag) usually surface immediately. Fall back to \`list_tags\` or exploratory \`query_notes\` only when the overview misses what you need.
 2. **Use \`search_notes\`** with the project name and key concepts as a fuzzy entry point \u2014 relevant material may exist under unrelated names.
 3. **Ask the user**, and the first time they save project-specific notes propose a scoping scheme so future sessions have an explicit entry point.
 
@@ -17665,11 +17560,11 @@ Use \`query_notes\` for multi-criteria questions that combine tags, frontmatter
 
 ### Frontmatter properties
 
-Use \`set_property\`, \`read_property\`, \`remove_property\` when the user asks to read or modify a single YAML frontmatter field (status, due date, priority, etc.). Use \`list_properties\` to see what property names are already in use across the vault \u2014 useful before introducing a new one.
+Use \`set_property\`, \`remove_property\` when the user asks to set or remove a single YAML frontmatter field (status, due date, priority, etc.).
 
 \`set_property\` infers \`type\` from the JS value (string\u2192text, number\u2192number, boolean\u2192checkbox, array\u2192list). For \`date\`/\`datetime\` you MUST pass \`type\` explicitly AND use ISO format (\`YYYY-MM-DD\` or \`YYYY-MM-DDTHH:mm:ss[.sss][Z|\xB1HH:mm]\`) \u2014 non-ISO values are silently dropped by the CLI, so the tool rejects them up front. Existing values are overwritten without asking.
 
-If you need frontmatter for one or more notes, call \`read_notes\` with \`fields: ['frontmatter']\` \u2014 that single batch call replaces N \`read_property\` calls when you have a list of paths.
+To read a single frontmatter value, or the full frontmatter of one or more notes, call \`read_notes\` with \`content: 'frontmatter'\` \u2014 a single batch call returns each note's frontmatter object with accurate types.
 
 ### Tags
 
@@ -17718,7 +17613,7 @@ For tag-driven questions ("which notes are tagged X?", "show me everything in #a
 `;
 var GET_VAULT_OVERVIEW_HINT = `## Orientation
 
-Before reaching for \`list_tags\`, \`list_properties\`, or exploratory \`query_notes\`, call \`get_vault_overview\` once at the start of a session. It returns the top-level folder layout with counts, the top tags, frontmatter properties with inferred types, the total note count, and the top 10 notes by inbound wikilinks \u2014 enough to orient yourself in a single call. The same payload is available as the MCP resource \`vault://overview\` for clients that auto-load resources.`;
+Before reaching for \`list_tags\` or exploratory \`query_notes\`, call \`get_vault_overview\` once at the start of a session. It returns the top-level folder layout with counts, the top tags, frontmatter properties with inferred types, the total note count, and the top 10 notes by inbound wikilinks \u2014 enough to orient yourself in a single call. The same payload is available as the MCP resource \`vault://overview\` for clients that auto-load resources.`;
 async function buildServerInstructions(registry2) {
   let result = STATIC_SERVER_INSTRUCTIONS;
   result += "\n\n" + GET_VAULT_OVERVIEW_HINT;
@@ -17728,7 +17623,7 @@ async function buildServerInstructions(registry2) {
 
 ## Multi-vault mode
 
-This server is registered with multiple vaults: ${names}. Every tool accepts an optional \`vault\` parameter. For broad recall, \`search_notes\`, \`query_notes\`, \`get_vault_overview\`, \`list_tags\`, and \`list_properties\` fan out across all vaults when \`vault\` is omitted; other tools (reads of specific paths, writes, single-vault diagnostics) require an explicit \`vault\` \u2014 omitting it returns \`VAULT_REQUIRED\`. Fan-out responses include \`results_by_vault\`, \`skipped_vaults\` (vaults pre-filtered out, e.g. missing semantic index), and \`failed_vaults\` (per-vault runtime errors with \`{ code, message, details? }\`) \u2014 a single failed vault does not abort the whole call. Path-shaped parameters (\`path\`, \`paths\`, \`path_prefix\`) remain vault-relative; vault identity is always carried by \`vault\`.`;
+This server is registered with multiple vaults: ${names}. Every tool accepts an optional \`vault\` parameter. For broad recall, \`search_notes\`, \`query_notes\`, \`get_vault_overview\`, and \`list_tags\` fan out across all vaults when \`vault\` is omitted; other tools (reads of specific paths, writes, single-vault diagnostics) require an explicit \`vault\` \u2014 omitting it returns \`VAULT_REQUIRED\`. Fan-out responses include \`results_by_vault\`, \`skipped_vaults\` (vaults pre-filtered out, e.g. missing semantic index), and \`failed_vaults\` (per-vault runtime errors with \`{ code, message, details? }\`) \u2014 a single failed vault does not abort the whole call. Path-shaped parameters (\`path\`, \`paths\`, \`path_prefix\`) remain vault-relative; vault identity is always carried by \`vault\`.`;
   }
   for (const entry of registry2.list()) {
     const extra = await readExternalAgentInstructions(entry.path);