feat: Obsidian integration via cli scripts

vault/00-start/obsidian-usage.md

@@ -10,6 +10,8 @@ tags:
 
 Use Obsidian to navigate and review workspace memory. Do not use it as a separate memory database.
 
+Obsidian is the current interface over canonical Markdown memory. The workspace-level abstraction is `scripts/memory/`, so agents should use Obsidian-specific commands only through that adapter when possible.
+
 ---
 
 ## Recommended Start
@@ -126,3 +128,26 @@ For normal onboarding, keep them hidden and navigate through the named maps.
 - Templates may contain the final note `type` so newly created notes are useful immediately, but Bases must exclude the template folder so template files do not appear as data rows.
 - Role mapping files such as `04-people/manager.md` should use `type: role-map`, not `type: person`.
 - Bookmarks should keep `00-start/start-here.md`, `00-start/onboarding.md`, current work, work items, people, and high-value Bases easy to open.
+
+---
+
+## CLI And Templates
+
+The official Obsidian CLI can create notes from templates, query Bases, inspect properties, and search the vault.
+
+In this workspace, prefer the platform-agnostic memory wrapper:
+
+```bash
+bash scripts/memory/memory.sh create work-item pdiap-15999 "Example title"
+bash scripts/memory/memory.sh search "PDIAP-15765"
+bash scripts/memory/memory.sh base-query work-items
+bash scripts/memory/memory.sh health
+```
+
+The wrapper owns note type routing, so a `work-item` goes to `02-work-items/`, a `person` goes to `04-people/`, a `decision` goes to `05-decisions/`, and so on.
+
+Use Obsidian CLI directly only when debugging Obsidian-specific behavior:
+
+```bash
+bash scripts/obsidian/cli.sh help
+```