bd export currently silently overwrites issues.jsonl even when the database is stale (older than the JSONL file). This causes data loss in multi-agent workflows. Real incident from vc project: - Agent A created 4 discovery epics and exported - Agent B had stale database and exported, removing those epics - Required manual recovery Proposed fix: Check database freshness before export, similar to VC's ValidateDatabaseFreshness(). Require --force to override. Priority P1: Silent data loss in common multi-agent scenario. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
328 KiB
328 KiB