The import command was only updating jsonl_content_hash, not jsonl_file_hash. After sync imports JSONL but skips re-export (because DB matches JSONL), the jsonl_file_hash remained stale, causing validateJSONLIntegrity() to emit spurious "JSONL file hash mismatch" warnings on subsequent operations. Now import also calls SetJSONLFileHash with the same hash value, keeping both hashes in sync and eliminating the false warnings. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>