add tool prompting and doc updates for strict mode in edit/move, and sync_status tool

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

Author: phernandez

docs/AI Assistant Guide.md

@@ -80,19 +80,21 @@ read_note("memory://specs/search")      # By memory URL
 **Incremental editing** (v0.13.0):
 ```
 edit_note(
-    identifier="Search Design",
+    identifier="Search Design",         # Must be EXACT title/permalink (strict matching)
     operation="append",                 # append, prepend, find_replace, replace_section
     content="\n## New Section\nContent here..."
 )
 ```
+**⚠️ Important:** `edit_note` requires exact identifiers (no fuzzy matching). Use `search_notes()` first if uncertain.
 
 **File organization** (v0.13.0):
 ```
 move_note(
-    identifier="Old Note",
+    identifier="Old Note",              # Must be EXACT title/permalink (strict matching)
     destination="archive/old-note.md"   # Folders created automatically
 )
 ```
+**⚠️ Important:** `move_note` requires exact identifiers (no fuzzy matching). Use `search_notes()` first if uncertain.
 
 ### Project Management (v0.13.0)
 
@@ -364,6 +366,20 @@ When creating relations:
 - If information seems outdated, suggest `basic-memory sync`
 - Use `recent_activity()` to check if content is current
 
+**Strict Mode for Edit/Move Operations:**
+- `edit_note()` and `move_note()` require **exact identifiers** (no fuzzy matching for safety)
+- If identifier not found: use `search_notes()` first to find the exact title/permalink
+- Error messages will guide you to find correct identifiers
+- Example workflow:
+  ```
+  # ❌ This might fail if identifier isn't exact
+  edit_note("Meeting Note", "append", "content")
+  
+  # ✅ Safe approach: search first, then use exact result
+  results = search_notes("meeting")
+  edit_note("Meeting Notes 2024", "append", "content")  # Use exact title from search
+  ```
+
 ## Best Practices
 
 1. **Proactively Record Context**

src/basic_memory/mcp/tools/edit_note.py

@@ -185,7 +185,7 @@ async def edit_note(
         edit_note("Meeting Notes", "append", "\\n- Follow up on action items")  # exact title
         edit_note("docs/meeting-notes", "append", "\\n- Follow up tasks")       # exact permalink
         edit_note("docs/Meeting Notes", "append", "\\n- Next steps")           # exact folder/title
-        
+
         # If uncertain about identifier, search first:
         # search_notes("meeting")  # Find available notes
         # edit_note("docs/meeting-notes-2025", "append", "content")  # Use exact result

src/basic_memory/mcp/tools/move_note.py

@@ -232,13 +232,13 @@ async def move_note(
     Examples:
         # Move to new folder (exact title match)
         move_note("My Note", "work/notes/my-note.md")
-        
+
         # Move by exact permalink
         move_note("my-note-permalink", "archive/old-notes/my-note.md")
-        
+
         # Specify project with exact identifier
         move_note("My Note", "archive/my-note.md", project="work-project")
-        
+
         # If uncertain about identifier, search first:
         # search_notes("my note")  # Find available notes
         # move_note("docs/my-note-2025", "archive/my-note.md")  # Use exact result

src/basic_memory/services/link_resolver.py

@@ -26,9 +26,11 @@ def __init__(self, entity_repository: EntityRepository, search_service: SearchSe
         self.entity_repository = entity_repository
         self.search_service = search_service
 
-    async def resolve_link(self, link_text: str, use_search: bool = True, strict: bool = False) -> Optional[Entity]:
+    async def resolve_link(
+        self, link_text: str, use_search: bool = True, strict: bool = False
+    ) -> Optional[Entity]:
         """Resolve a markdown link to a permalink.
-        
+
         Args:
             link_text: The link text to resolve
             use_search: Whether to use search-based fuzzy matching as fallback