manage-deletelisted

# manage-delete Call the obsidian-router `delete_file` MCP tool with arguments parsed from $ARGUMENTS. ## Arguments **Required**: - `path` — file path relative to vault root. - `confirm` — must be EXACTLY `true`. Any other value blocks the deletion. **Optional**: - `vault` — omit for default. - `ifMatch` — a `contentSha256` from a prior `get_file`. Refuses the delete with a 409 conflict if the file changed since you read it. Use it when deleting a file you inspected earlier and another session could have edited in between — it stops you from deleting someone's just-made changes. ## Argument parsing from $ARGUMENTS - bare path → `path`. **DO NOT** auto-set `confirm=true`. The first call should fail with the guard message; only set `confirm=true` when the user re-issues the command with explicit confirmation. - `<path> --yes` or `<path> confirm=true` → set `confirm=true` ## Safety protocol 1. **First invocation without `confirm=true`**: - Show the user the path that's about to be deleted - Optionally call `get_file` to show a preview (first 10 lines) so they know what they're deleting - Ask: *"Confirm delete? Re-run with `confirm=true` to proceed."* - DO NOT call `delete_file` with `confirm=true` on the user's behalf. 2. **Second invocation with `confirm=true`**: - Call the tool - Report `vault`, `path`, `deleted: true` If the user clearly types `confirm=true` from the start, you can call directly — but err on the side of confirming. This guard exis