docs: qualify MCP cloud deletion routing

Signed-off-by: phernandez <paul@basicmachines.co>

Author: phernandez

content/03.cloud/01.cloud-guide.md

@@ -123,9 +123,12 @@ bm project remove research --cloud --delete-notes
 Keep the explicit `--cloud` flag on the destructive `--delete-notes` command so the CLI also removes any configured local sync directory. Omitting `--cloud` from a cloud-routed project still purges hosted storage, but leaves the local sync copy intact. Hosted deletion is asynchronous: the project is hidden from cloud workspace operations when deletion is accepted, then a background job removes its database rows. A local routing or sync configuration entry can still appear as a config-only row in the combined `bm project list`; that does not mean the hosted project remains. With `--delete-notes`, the background job also removes indexed and unindexed objects under the project's exact storage prefix.
 
 The MCP `delete_project` tool provides the same hosted-storage purge with
-`delete_notes=true`. It does not remove a configured local sync directory; use the explicit
-CLI command above when you need to delete both copies. The MCP response reports the pending
-deletion status and background job ID.
+`delete_notes=true` when the MCP session is hosted or explicitly cloud-routed. From a local
+stdio MCP session, also pass `workspace` to route the request to that cloud workspace;
+`delete_notes=true` alone does not switch a local request to Cloud. MCP deletion does not
+remove a configured local sync directory, so use the explicit CLI command above when you need
+to delete both copies. The MCP response reports the pending deletion status and background
+job ID.
 
 ---