BUG: bm_context returns empty for valid notes

[bm-clawd]

Problem

bm_context returns "No context found" for notes that exist and have observations/relations.

Reproduction

bm_context({ url: "memory://memory/2026-02-17" })  → No context found
bm_context({ url: "memory://claw/memory/2026-02-17" })  → No context found

The note memory/2026-02-17 exists, is indexed (readable via bm_read), and has content. Graph traversal returns nothing.

Impact

High. bm_context is the primary tool for navigating the knowledge graph by following relations. If it returns empty, the agent can't traverse connected knowledge — one of BM's core differentiators.

Notes

• May be related to notes not having explicit ## Relations sections in BM observation format
• Or the permalink format may not match what the context API expects
• Daily notes are mostly plain markdown, not structured with observations — could be a content format issue

Upstream Tracking (basic-memory)

• Upstream: BUG: build_context empty results on valid note identifiers (fallback resolution + diagnostics) basic-memory#582

[bm-clawd]

Fixed in commit e29d611 — bm_context now correctly handles mixed relation/entity types in related_results from BM MCP.