docs: warn before deleting local cloud sync files

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

Author: phernandez

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

@@ -108,6 +108,10 @@ The full command walkthrough — sign-in options, API keys, workspaces, routing,
 
 Cloud project removal keeps note files by default. Use `--delete-notes` when you also want to purge the project's active cloud storage:
 
+::warning
+If the project has a configured local sync directory, `--cloud --delete-notes` also removes that local directory. Back up any local files you need before running the destructive command. Deletion is irreversible for active project storage; existing point-in-time snapshots may still contain historical copies until those snapshots are deleted or expire.
+::
+
 ```bash
 # Stop tracking the project, but retain its cloud files
 bm project remove research --cloud
@@ -120,10 +124,6 @@ The `--cloud` flag is optional when `research` is already configured as a cloud-
 
 The MCP `delete_project` tool provides the same behavior with `delete_notes=true`. Its response reports the pending deletion status and background job ID.
 
-::warning
-Deleting with `--delete-notes` is irreversible for active project storage. Existing point-in-time snapshots may still contain historical copies until those snapshots are deleted or expire.
-::
-
 ---
 
 ## Upload Files to Cloud