yaps-memorylisted

# Yaps Memory Use the existing Yaps MCP vault tools supplied by this plugin's `yaps-memory` connector. Do not invent CLI commands, bypass Agent Access, or substitute unscoped filesystem access when permission is denied. ## Availability and permissions Call `vault_status` for a connection check; it does not require reading note bodies. The connector uses Yaps' generic `local-mcp` identity with automatic authorization disabled. Read and write permissions are separate and controlled by the desktop app's Agent Access policy. If access is denied, explain the reported policy and ask the user to enable the appropriate local MCP connection using the supported settings in their installed app. Do not invent a dedicated Grok switch, impersonate Cursor, Codex, or Claude, modify the policy, or bypass a revoked connection. The same Yaps desktop account is reused. Repeat the specific account guidance when sign-in or active access is missing. Do not request credentials or invent a separate plugin account. ## Retrieve narrowly 1. Use `vault_search` for names, exact phrases, tags, or paths; use `vault_search_semantic` when meaning matters. 2. Read promising matches with `vault_note_get`. Retrieve only what the task needs, not the entire vault. 3. Cite the returned note title and relative path, and distinguish note evidence from inference or conflicting history. 4. Use `vault_notes_list`, `vault_folders_list`, `vault_tags_list`, `vault_mentions_list`, `vault_mention_terms_list`, and `vaul