feat: Update documentation for memory vault integration and work items, clarifying usage of Obsidian CLI and resolving Fid4 dependency conflicts

This commit is contained in:
2026-04-17 14:42:00 -06:00
parent 4ea188739d
commit 696a1258b1
7 changed files with 35 additions and 7 deletions

View File

@@ -72,6 +72,7 @@ This gives agents an automatic destination for new notes without coupling the ru
- Use the memory interface when creating new canonical notes from a known type.
- Use the memory interface for broad search, Base queries, and vault health checks.
- Prefer Obsidian CLI property operations for frontmatter/property edits when available, especially on existing notes that appear in Bases, because the CLI reduces YAML formatting drift.
- Edit Markdown directly for precise memory curation, corrections, and content updates.
- Do not treat Obsidian CLI failure as project context.
- Do not require Obsidian to be running for core workspace operation.