Commits on May 2, 2026 v0.41.1: ref-mode merge UX fixes Three fixes triaged out of the v0.40 ignored-spec backlog. Each spec was either passing under the v0.40 implementation already or asserting old structural-merge wording; this release closes the gap between v0.40+ behavior and the acceptance suite. Fixed ----- - `merge_progress_summary` now also reads `.morph/MERGE_REF.json` (the v0.40 ref-mode breadcrumb) and pulls unmerged paths from `git ls-files --unmerged`, so `morph status` mid-conflict reports "You have unmerged paths" + the morph merge --continue/--abort hint banner instead of "nothing to commit". Legacy MERGE_HEAD is still honored for any in-flight pre-v0.40 merge. - `morph merge --abort` outside a merge errors (exit 1, stderr `no merge in progress`) instead of no-op'ing. Matches `git merge --abort`'s `fatal: There is no merge to abort` (exit 128).…