The existing ZFC checks only compared issue counts, missing the case where counts match but content differs (e.g., status=open vs status=closed). Added Case 3 (bd-f2f) hash-based staleness detection: - Before export, check if JSONL content hash differs from stored hash - If hash mismatch detected, import JSONL first to get remote changes - Then proceed with export to write merged state This prevents the corruption scenario where: 1. Stale DB has old status values (e.g., status=closed) 2. Remote JSONL has correct values (e.g., status=open) 3. Export would overwrite correct JSONL with stale DB values 4. Git 3-way merge would propagate the corruption 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
51 KiB
51 KiB