Summary
find_conflicts surfaces conflicts but resolution is currently manual. We need a first-class workflow that lets users resolve conflicts directly from the CLI (and optionally from the web UI).
Proposed Changes
CLI
# List unresolved conflicts
ele conflicts list
# Choose one side
ele resolve-conflict <id> --choose source=claude
ele resolve-conflict <id> --choose source=obsidian
# Interactive merge (opens $EDITOR with both versions + merge markers)
ele resolve-conflict <id> --interactive
# Auto-resolve by strategy
ele resolve-conflict --all --strategy=newest
ele resolve-conflict --all --strategy=longest
Web UI
- Add a Conflicts tab/badge in the dashboard showing unresolved count
- Side-by-side diff view for each conflict pair
- One-click "Keep this / Keep that / Merge" buttons
- Option to write a merged version inline
Acceptance Criteria
Related
Builds on existing find_conflicts logic.
Summary
find_conflictssurfaces conflicts but resolution is currently manual. We need a first-class workflow that lets users resolve conflicts directly from the CLI (and optionally from the web UI).Proposed Changes
CLI
Web UI
Acceptance Criteria
ele conflicts listshows all pending conflicts with IDsele resolve-conflict <id> --choose source=<name>resolves and marks as doneele resolve-conflict <id> --interactiveopens a merge editorfind_conflictsno longer surfaces themRelated
Builds on existing
find_conflictslogic.