agentacct 0.6.0 — SQLite is the default event backend
SQLite is now the default event ledger
agentacct stores its event ledger in SQLite (events.sqlite3) by default instead of the flat events.jsonl file. A fresh install is SQLite-only from its first event; an existing events.jsonl store auto-adopts the log the next time it is opened, keeping the flat file as a backup. Reads and writes no longer re-parse a growing text file on every access — the foundation for a fast local CLI and live view.
Rolling-upgrade safe. Upgrading with daemons still running is safe: while an older, not-yet-restarted process keeps writing to events.jsonl, the new code drains those straggler writes into the log, so events are never split between the two ledgers or lost. Set AGENTACCT_EVENT_LOG_AUTHORITATIVE=0 to opt back into the legacy flat-file mode.
Three commands give explicit control over the flat file: agentacct event verify-log proves the SQLite copy matches a flat file line-for-line, agentacct event drop-flat-ledger --confirm retires the events.jsonl backup once a store has cut over, and agentacct canonical rebuild-store rebuilds the SQLite usage index from the ledger.
Removed: the offline Evidence v2 rebuild subsystem
The owner-gated agentacct evidence rebuild tooling (snapshot / build-candidate / activate / rollback) has been removed — it reconstructed the Evidence v2 store by replaying the v1 ledger from events.jsonl, an assumption the SQLite cutover broke. Evidence v2 itself is unchanged and still self-heals its projection from its own durable spool; agentacct evidence status / list / product are untouched.
Fixed
agentacct mcp doctorreports store writability for a SQLite-backed store (the probe was previously skipped wheneverevents.jsonlwas absent).agentacct canonical rebuild-storereconstructs from the authoritative log, not a staleevents.jsonlbackup, once a store has adopted.agentacct setup instructions/hooks claude-code installno longer crash when their target store does not exist yet.