ZacharyZhang-NYandClaude Opus 5.5
6d1373fe16
A failed read of what Git is doing shows as a danger alert in Git's words. git am's Skip and Abort had no operation name in either catalog and panicked; both catalogs now hold it. Tests cover the unread stop and both buttons through their confirm to Git. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 lines
752 B
Markdown
4 lines
752 B
Markdown
FAIL
|
|
|
|
apps/ely-tree/src/moves.rs:211 — Abort and Skip both request `tree.opname.am` for the new `Op::Am`, but neither language catalog defines that key. Open a repository where `git am --3way` stopped on a conflict, then press Abort or Skip: both handlers panic with `no message "tree.opname.am" in en-US` (also `zh-CN`) before opening their confirmation, breaking operation recovery. Native Windows and WSL probes reproduce all four action/locale combinations; logs: `.work/G-02-r1/windows-probe-actions.log` and `.work/G-02-r1/linux-probe-actions.log`. Add the operation name to both catalogs and cover both actions through their confirmation and Git command paths; the existing am regression only checks detection and misses these broken buttons.
|