@openparachute/vault 0.7.3-rc.7 → 0.7.3-rc.9

package/README.md

@@ -30,7 +30,7 @@ For remote access from Claude Desktop or mobile apps, see [Deployment](#deployme
 
 A server on port 1940 with:
 
-- **MCP** — 9 tools for AI agents (notes, tags, graph, vault info)
+- **MCP** — tools for AI agents (notes, tags, graph, vault info, attachments)
 - **REST API** — Full CRUD for notes, tags, links, full-text search
 - **Wikilink auto-linking** — `[[wikilinks]]` in note content automatically create links in the graph
 - **Obsidian import/export** — Bidirectional interop with Obsidian vaults
@@ -252,12 +252,14 @@ parachute-vault backup --schedule daily        # hourly | daily | weekly | manua
 parachute-vault backup status                  # schedule, last run, destinations, next run
 ```
 
-## MCP tools (9)
+## MCP tools (13 core, + attachments + admin)
 
 **Notes**: `query-notes` (universal read — single by ID/path, filter, search, graph neighborhood), `create-note` (single or batch), `update-note` (single or batch — content, tags, links, metadata), `delete-note`
-**Tags**: `list-tags` (with optional schema detail), `update-tag` (upsert description + schema fields), `delete-tag`
+**Tags**: `list-tags` (with optional schema detail), `update-tag` (upsert description + schema fields), `delete-tag`, `rename-tag`, `merge-tags`
 **Graph**: `find-path` (BFS between two notes)
 **Vault**: `vault-info` (get/update description + stats)
+**Admin**: `prune-schema`, `doctor` (taxonomy/metadata integrity scan), `manage-token`
+**Attachments** (2, present when the door wires an attachment-ticket provider — always true on this server): `request-attachment-upload`, `request-attachment-download` — mint a short-lived, single-use ticket a runtime's shell spends directly at `/vault/{name}/tickets/{id}`; bytes never pass through the tool call. See [`docs/HTTP_API.md`](./docs/HTTP_API.md#attachment-tickets-vault611--wave-1-bun-only).
 
 ### Vault descriptions
 

package/core/src/display-title.test.ts

@@ -83,6 +83,47 @@ describe("computeDisplayTitle", () => {
     const result = computeDisplayTitle(emojiTitle)!;
     expect(Array.from(result).length).toBe(DISPLAY_TITLE_MAX_LEN);
   });
+
+  describe("leading frontmatter block (misuse path — direct create with raw frontmatter)", () => {
+    it("skips a closed frontmatter block and derives the first line of the DOCUMENT", () => {
+      expect(computeDisplayTitle("---\ntitle: X\n---\n# Real Title")).toBe("Real Title");
+    });
+
+    it("skips a closed frontmatter block with multiple fields + blank lines after", () => {
+      expect(
+        computeDisplayTitle("---\ntitle: X\ntags: [a, b]\n---\n\n\nReal Title\nbody"),
+      ).toBe("Real Title");
+    });
+
+    it("falls back to treating an UNTERMINATED opening `---` as ordinary content", () => {
+      // No closing fence anywhere in the content — a note whose real first
+      // line is literally "---" (e.g. a markdown horizontal rule opener)
+      // must not be mangled.
+      expect(computeDisplayTitle("---\nnot frontmatter, just a rule\nmore text")).toBe("---");
+    });
+
+    it("returns null when content is EXACTLY a closed frontmatter block (nothing after)", () => {
+      expect(computeDisplayTitle("---\ntitle: X\n---\n")).toBeNull();
+      expect(computeDisplayTitle("---\ntitle: X\n---")).toBeNull();
+    });
+
+    it("returns null when only blank lines follow a closed frontmatter block", () => {
+      expect(computeDisplayTitle("---\ntitle: X\n---\n\n  \n")).toBeNull();
+    });
+
+    it("does not treat a closing fence found past the bounded scan window as a frontmatter close", () => {
+      // Opening `---` with the closing fence past FRONTMATTER_SCAN_LINES
+      // (100): the scan gives up and falls back to ordinary-content
+      // behavior, deriving from line 0.
+      const filler = Array.from({ length: 150 }, (_, i) => `line ${i}`).join("\n");
+      expect(computeDisplayTitle(`---\n${filler}\n---\nReal Title`)).toBe("---");
+    });
+
+    it("normal content with no leading `---` is byte-identical to prior behavior", () => {
+      expect(computeDisplayTitle("# Grocery List\nmilk, eggs")).toBe("Grocery List");
+      expect(computeDisplayTitle("Just a note\nbody text")).toBe("Just a note");
+    });
+  });
 });
 
 describe("toNoteIndex — displayTitle wiring", () => {

package/core/src/notes.ts

@@ -2769,6 +2769,15 @@ export const NOTE_INDEX_PREVIEW_LEN = 120;
 /** Max code points in a computed `displayTitle` (title axis, ratified 2026-07-17). */
 export const DISPLAY_TITLE_MAX_LEN = 120;
 
+/**
+ * Bounded line-count a leading frontmatter block's closing fence is
+ * searched within (see `computeDisplayTitle`). Frontmatter blocks are a
+ * handful of lines in practice; capping the scan keeps a pathological
+ * "content starts with `---` but never closes it" note O(1)-ish rather
+ * than a full-content scan on every derivation.
+ */
+const FRONTMATTER_SCAN_LINES = 100;
+
 /**
  * Derive a note's display title: the first non-empty line of `content`,
  * with a leading markdown heading marker (`#` through `######`) and its
@@ -2783,11 +2792,33 @@ export const DISPLAY_TITLE_MAX_LEN = 120;
  * in place of a `null` title — is deliberately NOT this function's job; it
  * reports the honest content-derived value (or its absence) and leaves
  * rendering to the caller.
+ *
+ * Frontmatter skip: normal ingestion strips a YAML frontmatter block into
+ * `metadata` before create, so `content` never carries one — but a direct
+ * MCP/REST create can paste raw frontmatter-bearing text
+ * (`---\ntitle: X\n---\n# Real Title`), and the first line of that
+ * DOCUMENT is not the first line of its delimiter. When `content` opens
+ * with a `---` line, derivation starts after the matching CLOSING `---`
+ * (searched within the first `FRONTMATTER_SCAN_LINES` lines). An
+ * unterminated opening `---` falls back to the pre-existing behavior —
+ * scanning from line 0 — so a note whose real first line is literally
+ * `---` isn't mangled.
  */
 export function computeDisplayTitle(content: string | null | undefined): string | null {
   if (!content) return null;
-  for (const rawLine of content.split("\n")) {
-    const stripped = rawLine.replace(/^#{1,6}\s*/, "").trim();
+  const lines = content.split("\n");
+  let startIndex = 0;
+  if (lines[0]?.trim() === "---") {
+    const scanLimit = Math.min(lines.length, FRONTMATTER_SCAN_LINES);
+    for (let i = 1; i < scanLimit; i++) {
+      if (lines[i]?.trim() === "---") {
+        startIndex = i + 1;
+        break;
+      }
+    }
+  }
+  for (let i = startIndex; i < lines.length; i++) {
+    const stripped = lines[i]!.replace(/^#{1,6}\s*/, "").trim();
     if (stripped === "") continue;
     // Iterate by Unicode code points so we don't split surrogate pairs mid-character.
     const codePoints = Array.from(stripped);

package/core/src/search-title-boost.test.ts

@@ -104,4 +104,22 @@ describe("search title-boost", () => {
     const hits = await store.searchNotes("nonexistent_term_xyz");
     expect(hits).toEqual([]);
   });
+
+  it("boosts on the post-frontmatter title line, not the `---` delimiter (shares computeDisplayTitle's frontmatter skip)", async () => {
+    // Direct-create misuse path: raw frontmatter-bearing content. Without
+    // the frontmatter skip, the derived "title" would be the literal
+    // string "---", which never matches any query term, so this note
+    // would wrongly land in the body-only tier.
+    await store.createNote(
+      "---\ntitle: irrelevant\n---\n# Budget Review\nQ3 numbers",
+      { path: "frontmatter-led" },
+    );
+    await store.createNote(
+      "Weekly Standup\nsomewhere we discuss the budget in passing",
+      { path: "body-only" },
+    );
+
+    const hits = await store.searchNotes("budget review");
+    expect(hits[0].path).toBe("frontmatter-led");
+  });
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openparachute/vault",
-  "version": "0.7.3-rc.7",
+  "version": "0.7.3-rc.9",
   "description": "Agent-native knowledge graph. Notes, tags, links over MCP.",
   "module": "src/cli.ts",
   "type": "module",