[0.30.0] - 2026-04-27
Changed
burn mcp-serverruns an incrementalbuildArchive()at startup (#97) so the firstburn__sessionCost/burn__currentBlocktool call hits the SQL archive instead of re-walking the JSONL ledger. The MCP tool handlers themselves run another incremental build before each query so turns appended by hooks mid-session also show up in tool responses. The build is idempotent — a no-op when nothing has changed since the last build — and a build failure logs to stderr but never refuses to serve. Tool fallbacks toqueryAllare wired through the newonLoghook so any persistent archive breakage is visible in the MCP host's stderr stream.