feat(assets): vault_read_asset + vault_list_assets — read and browse non-markdown vault files

.devin/wiki.json

@@ -40,7 +40,7 @@
     },
     {
       "title": "Obsidian Markdown Parsing",
-      "purpose": "The pure parser layer in obsidian-markdown/ — no filesystem I/O, just domain knowledge about the Obsidian/Markdown format. Covers: links.ts (link grammar, fence-aware extraction, resolution for wikilinks, markdown links, embeds, frontmatter links, and relative path-from-current-file links — all three of Obsidian's 'New link format' modes); lines.ts (CRLF-safe line splitting, the consolidated fence state machine, classifyLines for identifying fenced regions); frontmatter.ts (gray-matter parse/stringify, frontmatter merge); callouts.ts (leading-callout parser for > [!type] blocks); headings.ts (shared H1-H6 section-span parser used by both read and patch operations); tasks.ts (Tasks-plugin task-line grammar covering emoji signifiers and Dataview inline fields); memory-entries.ts (memory-entry grammar — parses the dated-bullet format of About Me/ memory files into individual entries for vault_memory_recall's entry-granular index); plaintext.ts (strips Obsidian/Markdown syntax to produce plain text for the embedding pipeline). This layer is architecturally significant — it encodes the Obsidian-parity behavior that distinguishes Vault Cortex from simpler file-based integrations.",
+      "purpose": "The pure parser layer in obsidian-markdown/ — no filesystem I/O, just domain knowledge about the Obsidian/Markdown format. Covers: links.ts (link grammar, fence-aware extraction, resolution for wikilinks, markdown links, embeds, frontmatter links, and relative path-from-current-file links — all three of Obsidian's 'New link format' modes); canvas.ts (JSON Canvas 1.0 linearizer — spatial group containment, reading-order node sort, id-resolved edge lists — pure string-to-string despite parsing JSON, same leaf layer); lines.ts (CRLF-safe line splitting, the consolidated fence state machine, classifyLines for identifying fenced regions); frontmatter.ts (gray-matter parse/stringify, frontmatter merge); callouts.ts (leading-callout parser for > [!type] blocks); headings.ts (shared H1-H6 section-span parser used by both read and patch operations); tasks.ts (Tasks-plugin task-line grammar covering emoji signifiers and Dataview inline fields); memory-entries.ts (memory-entry grammar — parses the dated-bullet format of About Me/ memory files into individual entries for vault_memory_recall's entry-granular index); plaintext.ts (strips Obsidian/Markdown syntax to produce plain text for the embedding pipeline). This layer is architecturally significant — it encodes the Obsidian-parity behavior that distinguishes Vault Cortex from simpler file-based integrations.",
       "parent": "Architecture",
       "page_notes": [
         {
@@ -50,7 +50,7 @@
     },
     {
       "title": "Vault Operations",
-      "purpose": "The filesystem I/O layer in vault-operations/ that reads, writes, and transforms vault content. Safety primitives: atomic writes (atomicWriteFile temp-then-rename, atomicWriteFileExclusive link-based no-clobber for TOCTOU-safe creates), per-file write locking (file-write-lock.ts — serializing, fail-fast, and multi-file fail-fast modes), path traversal prevention (resolveSafePath resolve + prefix check, toVaultRelativePath normalization), and protected-path enforcement (PROTECTED_PATHS checked after normalization). Covers: vault-filesystem.ts (read/write/list/delete .md files, outline and section reads, protected-path validation); vault-patcher.ts (surgical edits — heading-targeted patch with prepend/append/replace operations, and find-and-replace with optional replace-all); note-mover.ts (move/rename a note and rewrite every vault-wide link that pointed to it, using the link resolution engine from obsidian-markdown/links.ts — preflight-then-commit design with multi-file exclusive locking); memory-store.ts (About Me/ heading-aware read/append/delete with shrink guard, idempotency guard, and ambiguity guard — see Memory Layer page); daily-notes.ts (daily note config reader and path resolver — see Memory Layer page). All functions follow the (params, logger) two-argument pattern.",
+      "purpose": "The filesystem I/O layer in vault-operations/ that reads, writes, and transforms vault content. Asset use-case: asset-operations.ts (per-type read dispatch — image fitting, canvas linearize/raw, strict-UTF-8 text passthrough, structured errors — plus browsing: extension filter, per-extension counts, capped statted slice) composes the vaultFs primitives readAsset (binary read with .md rejection and stat-first size cap), listAssets (folder-scoped non-md walk), and statAssets (bounded-concurrency stat) behind the vault_read_asset/vault_list_assets tools. Safety primitives: atomic writes (atomicWriteFile temp-then-rename, atomicWriteFileExclusive link-based no-clobber for TOCTOU-safe creates), per-file write locking (file-write-lock.ts — serializing, fail-fast, and multi-file fail-fast modes), path traversal prevention (resolveSafePath resolve + prefix check, toVaultRelativePath normalization), and protected-path enforcement (PROTECTED_PATHS checked after normalization). Covers: vault-filesystem.ts (read/write/list/delete .md files, outline and section reads, protected-path validation); vault-patcher.ts (surgical edits — heading-targeted patch with prepend/append/replace operations, and find-and-replace with optional replace-all); note-mover.ts (move/rename a note and rewrite every vault-wide link that pointed to it, using the link resolution engine from obsidian-markdown/links.ts — preflight-then-commit design with multi-file exclusive locking); memory-store.ts (About Me/ heading-aware read/append/delete with shrink guard, idempotency guard, and ambiguity guard — see Memory Layer page); daily-notes.ts (daily note config reader and path resolver — see Memory Layer page). All functions follow the (params, logger) two-argument pattern.",
       "parent": "Architecture"
     },
     {
@@ -69,7 +69,7 @@
     },
     {
       "title": "Tool Reference",
-      "purpose": "The MCP tools, now organized in domain group modules under mcp-core/tools/: vault-crud-tools.ts (read, write, patch, replace, delete-span, list, delete, move, update-properties), search-tools.ts (search, search-by-tag, search-by-folder, recent-notes, list-tags, list-property-keys, list-property-values, search-by-property, get-backlinks, get-outgoing-links, find-orphans), task-tools.ts (list-tasks, update-task), memory-tools.ts (get-memory, update-memory, list-memory-files, delete-memory, memory-recall; conditionally registered when MEMORY_ENABLED=true), and daily-note-tools.ts (get-daily-note). vault_list_tasks and vault_update_task in task-tools.ts provide Kanban-aware task management: vault_list_tasks is a vault-wide task index with structured filters (status, 6 date fields, priority, folder/tag/heading/path scope), array params for multi-lane queries, date cascade sorting, and position sorting for board order; vault_update_task applies status, priority, and/or lane changes in a single call — marking done auto-detects the done lane (via **Complete** markers, falling back to 'Done' heading), stamps/removes completion dates, and writes in the user's configured Tasks plugin format (emoji or Dataview). The orchestrator in tool-definitions.ts composes TOOL_NAMES from each group and calls register functions. Each tool description includes Example, When to use, Returns, and Errors sections — optimized against Glama's TDQS (Tool Description Quality Score) model to ensure agents select and invoke the right tool efficiently.",
+      "purpose": "The MCP tools, now organized in domain group modules under mcp-core/tools/: vault-crud-tools.ts (read, write, patch, replace, delete-span, list, delete, move, update-properties), search-tools.ts (search, search-by-tag, search-by-folder, recent-notes, list-tags, list-property-keys, list-property-values, search-by-property, get-backlinks, get-outgoing-links, find-orphans), task-tools.ts (list-tasks, update-task), memory-tools.ts (get-memory, update-memory, list-memory-files, delete-memory, memory-recall; conditionally registered when MEMORY_ENABLED=true), daily-note-tools.ts (get-daily-note), and asset-tools.ts (read-asset — images as MCP image blocks via a sharp fit-to-byte-budget pipeline, .canvas linearized via obsidian-markdown/canvas.ts, text formats verbatim; list-assets — filesystem-backed discovery with folder/extension filters and per-extension counts). vault_list_tasks and vault_update_task in task-tools.ts provide Kanban-aware task management: vault_list_tasks is a vault-wide task index with structured filters (status, 6 date fields, priority, folder/tag/heading/path scope), array params for multi-lane queries, date cascade sorting, and position sorting for board order; vault_update_task applies status, priority, and/or lane changes in a single call — marking done auto-detects the done lane (via **Complete** markers, falling back to 'Done' heading), stamps/removes completion dates, and writes in the user's configured Tasks plugin format (emoji or Dataview). The orchestrator in tool-definitions.ts composes TOOL_NAMES from each group and calls register functions. Each tool description includes Example, When to use, Returns, and Errors sections — optimized against Glama's TDQS (Tool Description Quality Score) model to ensure agents select and invoke the right tool efficiently.",
       "parent": "MCP Interface"
     },
     {

.env.example

@@ -101,6 +101,12 @@ TZ=UTC
 # Enables polling for the file watcher and rename-based moves across
 # the Docker Desktop/WSL2 bridge.
 # WINDOWS_MODE=false
+#
+# Largest asset file vault_read_asset will read, in bytes (default: 52428800 = 50 MiB).
+# MAX_ASSET_BYTES=52428800
+# Byte budget for images returned by vault_read_asset, in binary bytes before
+# base64 encoding (default: 49152 = 48 KiB, sized for Claude Code's response cap).
+# MAX_IMAGE_OUTPUT_BYTES=49152
 # Enable or disable the memory layer (default: true).
 # Set to false to hide memory tools, skip auto-initialization, and omit
 # memory references from server metadata. MEMORY_DIR is ignored when false.