BUG: bm_edit fails for notes not yet indexed by watcher

[bm-clawd]

Problem

bm_edit returns "Failed to edit note... It may not exist" for notes that exist on disk but haven't been indexed by bm watch yet.

Reproduction

1. Write a file directly to disk: memory/2026-02-18.md
2. Immediately call bm_edit({ identifier: 'memory/2026-02-18', operation: 'append', content: '...' })
3. Returns: "Failed to edit note 'memory/2026-02-18'. It may not exist."
4. The file is on disk and readable via cat

Root Cause

bm_edit looks up the note in the database (not the filesystem). If bm watch hasn't indexed it yet (see #15), the edit silently fails.

Impact

High. This breaks the natural write-then-edit workflow. The agent writes a daily note, then tries to append to it later — and can't, because the watcher is stale.

Workaround

Use the file-level Edit tool instead of bm_edit for notes written directly to disk. But this means the edit also won't be indexed until the watcher catches up.

Upstream Tracking (basic-memory)

• Upstream: Feature: edit-note recovery when note exists on disk but is not indexed yet basic-memory#581
• Dependency: BUG: watch service can go stale while process stays alive (self-heal + heartbeat) basic-memory#580