bug: dewey_promote MCP tool fails with 'Page not found' for compiled articles

[jflowers]

Summary

dewey_promote (MCP tool) and dewey promote (CLI) cannot locate pages stored via dewey_store_compiled. Both return "Page not found" for pages that exist in the internal SQLite store.

Reproduction

1. Store a compiled article via MCP:

   dewey_store_compiled(tag="gateway", content="...", sources=["gateway-2"])
   

2. Verify it exists:

   SELECT name, json_extract(properties, '$.tier') FROM pages
   WHERE name = 'compiled/gateway';
   -- Returns: compiled/gateway | draft

3. Attempt MCP promote:

   dewey_promote(page="compiled/gateway")  → "Page not found"
   dewey_promote(page="gateway")           → "Page not found"
   

4. Attempt CLI promote:

   dewey promote compiled/gateway --vault /path/to/repo
   # Returns: "another Dewey process is using this database"
   # (because the MCP server holds the SQLite lock)

Impact

• Compiled articles cannot be promoted from draft → validated via the intended API
• CLI fallback also fails because the MCP server holds the database lock
• Workaround: manually edit the frontmatter tier: draft → tier: validated in the .uf/dewey/compiled/*.md files (this does not update the SQLite store)

Expected Behavior

dewey_promote should locate pages in the internal store (learnings and compiled articles), not only in the Obsidian vault.

Related

• bug: MCP tools cannot access internal store pages (learnings, compiled articles) #90 (MCP tools cannot access internal store pages)