v0.15.1

[0.15.1] - 2026-08-21

This hotfix locks in backward compatibility for SQLite stores created before 0.15.0.

Highlights

• Added regression fixtures based on legacy schema-v1 and schema-v2 stores.
• Verified that opening a legacy store adds messages.deleted_at without deleting or tombstoning existing messages.
• Verified that schema-v1 stores also gain summary_nodes.strategy and advance to schema version 2 automatically.
• Behavioral reads continue to expose legacy message content after migration.

Migration notes

• No manual migration is required.
• Existing databases are upgraded additively on first open; legacy messages remain live.

v0.15.0

[0.15.0] - 2026-08-21

This release expands archive retrieval, deterministic artifact exploration, and storage lifecycle safety.

Highlights

• lcm_grep supports pagination, summary-node scoping, and covering leaf annotations.
• Text artifacts expose deterministic JSON, CSV/TSV, SQL, and code exploration summaries.
• lcm_status and lcm_doctor report hook failures and repair managed resume-note drift.
• Removed messages are preserved as tombstones with explicit [removed] and [pruned: <id>] expansion markers.
• Storage operations use immediate transactions and WAL checkpoints for safer concurrent maintenance.

Issue fixes

• Issue #9: live SQLite corruption is quarantined and the triggering operation retried once; optional plugin hooks fail open so a corrupted store no longer blocks prompt submission.

Migration notes

• Snapshot imports now require an explicit merge or replace mode.
• lcm_expand returns summaries by default; pass includeRaw=true for raw messages.
• The removed interop.contextMode and interop.neverOverrideCompactionPrompt options must be deleted from configuration.

v0.14.2

Full Changelog: v0.14.1...v0.14.2

v0.14.1

Full Changelog: v0.14.0...v0.14.1

v0.14.0

[0.14.0] - 2026-04-13

Added

• New lcm_retrieval_debug MCP tool surfaces the latest automatic-retrieval recall decision per session
• lcm_status now reports storage-size, prunable-event, and FTS-index diagnostic fields
• StoreStats type extended with storage-size, prunable-event, and FTS-index diagnostic fields

Fixed

• readSessionSync, readMessageSync, readMessageSyncV2, and grep scan paths now skip corrupted info_json/part_json rows instead of throwing
• lcm_doctor detects and reports malformed stored rows and orphaned message-fts entries

v0.13.7

Fixed

• skip corrupted stored info_json, part_json, and artifact metadata_json rows during reads so a single bad SQLite row no longer crashes grep, resume, or session loading

Verification

• npm run typecheck
• npm run lint
• npm test

v0.13.6

Bun on Windows now stays in a pre-SQLite safe mode by default to avoid the reported native-crash path. Added an explicit override for users who still need the full archive hooks on Bun for Windows.

v0.13.5

• Restore schema-v2 compatibility for persisted stores after the PR #6 merge.
• Remove the unfinished llm-cli summary configuration surface before shipping it.
• Restore Biome-clean formatting so the full cross-platform CI matrix passes again.

v0.13.4

• Republish the latest malformed-message hardening and Bun Windows capture fixes to npm.
• Keep the Bun-on-Windows lightweight capture regression test portable across non-Windows CI runners.
• Includes the CI formatting fix that landed after PR #5.

v0.13.3

• Publish the latest malformed-message hardening, including grep scan fallback and message.info.time.created guards.
• Include the Bun Windows part-update capture fix.
• Restore CI-clean formatting after the PR #5 merge so publish validation passes.