v0.2.80

What's new in v0.2.80

A critical hotfix for users running v0.2.78 or v0.2.79.

Fixed: brain_recall could fail with "no such column" SQL error

v0.2.78 added 4 new diagnostic columns to the operation_log table
(exact_count, related_count, fallback_chain, vector_unavailable) via
migration v28. However, I forgot to bump the CURRENT_SCHEMA_VERSION
constant from 27 to 28 at the same time.

The migration trigger condition currentVersion < CURRENT_SCHEMA_VERSION
evaluates to 27 < 27 = false, so the migration silently never runs.
Meanwhile, logOperation was upgraded to write 12 columns including the new
4 — against a database that still only has the old 8 columns. Every recall
call hits SQLite error: no such column: exact_count.

If you were on v0.2.78 or v0.2.79 and brain_recall was failing for you,
that's what was happening.

This release:

• Bumps CURRENT_SCHEMA_VERSION to 28 so the migration runs on startup.
• No other code changes.

Impact

• Fresh installs on v0.2.80: clean (the schema baseline already includes the
  4 columns).
• Upgrades from v0.2.77 → v0.2.80: migration runs once, columns get added.
• Upgrades from v0.2.78 or v0.2.79 → v0.2.80: migration runs once (it was
  blocked before), columns get added.

After updating, restart any external agents (Claude Desktop / Claude Code /
Cursor / etc.) once more to make their MCP server subprocess reconnect to
the now-migrated database.

Apology

Sorry for the noise across three back-to-back releases (v0.2.77 / v0.2.78 /
v0.2.79). The release verifier checks that the cloud reports the new version
and the update API returns it, but it does not exercise the local database
migration path. That gap is now in the backlog.