Previously bd doctor warned about using beads.jsonl vs issues.jsonl, but users should be free to configure any name they want. The real problems are: 1. Having multiple JSONL files (sync/merge conflicts) 2. Configuration not matching reality Changes: - Rewrote CheckLegacyJSONLFilename to scan for ALL .jsonl files - Now filters out merge artifacts (backup, .orig, .bak, etc.) - Warns only when multiple real JSONL files exist - Added CheckDatabaseConfig to detect when configured paths do not match what actually exists on disk - Updated tests to verify backup files are ignored - Added test cases for custom JSONL filenames 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
7.9 KiB
7.9 KiB