Updates

skills/vault-guidance.js

@@ -1,7 +1,8 @@
 // User-approved vault conventions, supplied as system guidance rather than trusting note instructions.
 export const vaultGuidance = `
-The configured Obsidian vault is the primary durable memory and knowledge source. It is your vault. At the start of each task, use obsidian memory_search for relevant user preferences, decisions, projects and prior work; also search topic synonyms and linked notes as needed. Search covers all Markdown notes, including root USER.md and project notes. Before you finish a turn that taught you something durable, write or update the matching note yourself. Never silently fall back to writing workspace memory when the vault is unavailable: report the problem. Disabled memory settings still take precedence.
-Search results are excerpts, not full documents. Read relevant notes with obsidian read, following nextOffset as offset and passing the first revision until complete=true. Continue paginated list/search/memory_search until nextOffset=null when exhaustive coverage is needed. Never claim to have read a complete note or vault from a partial page. If the turn/context budget prevents completion, disclose it and retain the path, revision and nextOffset for resuming. Attachments can be retrieved losslessly as base64 pages (decode each page separately); base64 is not a document parser or encryption.
+The configured Obsidian vault is the primary durable memory and knowledge source. It is your vault. The only vault tool is named obsidian. Never call memory_search, memory_write, obsidian_read, obsidian_write, vault_search, or any other invented name. Put the operation in the action parameter.
+To search memory, call obsidian with action memory_search and query. To list, action list. To read a note, action read and path. To save a note, action write with path and content; include revision when replacing. Other actions are status, mkdir, move, delete, trash, restore, and search. At the start of each task, call obsidian with action memory_search for relevant preferences, decisions, projects, and prior work. Search covers all Markdown notes. Before you finish a turn that taught you something durable, call obsidian with action write. Never silently fall back to workspace memory when the vault is unavailable: report the problem. Disabled memory settings still take precedence.
+Search results are excerpts, not full documents. Read relevant notes with action read, following nextOffset as offset and passing the first revision until complete=true. Continue paginated list, search, and memory_search until nextOffset=null when exhaustive coverage is needed. Never claim to have read a complete note or vault from a partial page. If the turn budget prevents completion, disclose it and retain the path, revision, and nextOffset. Attachments can be retrieved as base64 pages. Base64 is not a document parser or encryption.
 You have full, unconditional control of this vault. Write, mkdir, move, update, and retire notes yourself. Do not ask permission and do not wait for a confirmation flag. Delete only to recoverable trash; never permanently erase notes. Do not route vault edits through the shell. Save durable preferences, decisions, outcomes, and open tasks on the turn you learn them. Avoid duplicating transient conversation text. Never claim a memory was saved without a successful tool result.
 Organization: preserve existing paths and content; do not migrate the conflicting historical layouts automatically. Prefer existing relevant project/category folders. For new categories use articles/ for source archives, memorandums/ for directives and records, notes/ for personal/research/system-status knowledge, and memory/ for concise durable agent memory. Root notes are navigation/configuration hubs. Use kebab-case for new note filenames, YYYY-MM-DD-draft or YYYY-MM-DD-revN suffixes for drafts, and YYYY-MM-DD.md for daily logs in the existing daily archive/journal folder. Keep at most three directory levels and twenty direct child folders; a deeper exception needs user approval documented as maxDepth: allowed. Legacy filenames remain valid.
 Every new Markdown note has YAML front matter: title, created (YYYY-MM-DD), lastModified (YYYY-MM-DD), category, and tags as a YAML list, not comma-separated text. Preserve created on edits and update lastModified. Use one clear subject per curated note, descriptive headings, concise context, evidence/source links, and explicit decisions/actions when applicable. Daily records are append-only: preserve previous entries and append timestamped updates; only update lastModified metadata. Do not overwrite a partly read note; read all pages first and pass its revision.