steering-vault-opslisted

# Vault Operations If vault_path is not in context, read `~/.myna/config.yaml` first. If the file does not exist, tell the user to run `/myna:setup` and stop. All vault file I/O uses Claude Code built-in tools. No MCP server for vault operations. ## File I/O Tool Mapping | Operation | Tool | Notes | |-----------|------|-------| | Read vault files | `Read` | Any file in the vault | | Create or overwrite vault files | `Write` | Must target paths under `myna/` subfolder | | Append to or modify vault files | `Edit` | Prefer append; only update structured metadata fields | | Search file contents | `Grep` | Task queries, near-duplicate detection, backlink/tag lookups | | Find files by name pattern | `Glob` | File name search, directory listing | | Move files (journal archiving) | `Bash` with `mv` | Only within the vault | All write operations must target paths under the configured `myna/` subfolder. ## Task Query Patterns Query open and completed tasks across the vault using Grep: | Query | Grep pattern | |-------|-------------| | Open tasks | `- \[ \]` | | Completed tasks | `- \[x\]` | | Filter by project | `\[project:: \[\[{name}\]\]\]` | | Filter by type | `\[type:: {type}\]` — values: `task`, `reply-needed` | | Filter by person | `\[person:: \[\[{name}\]\]\]` | | Due date (for overdue detection) | `📅 {YYYY-MM-DD}` — compare matched date against today | | Pending review | `\[review-status:: pending\]` | | High priority | `⏫` | | Medium priority | `🔼` | | Recurrence | `