Live-checking the import route on the node showed both of its refusals
arriving as "Operation failed. Check server logs for details."
That is not merely opaque here, it is unsafe. The two messages are the
feature's safety rails: "That is not a valid BIP-39 recovery phrase —
check for typos" is the only help someone gets when a pasted phrase has
a bad word, and "This wallet already has a backup phrase… reveal and
write down the current phrase first, then confirm to replace it" is the
warning that stops an operator orphaning the words their balance was
minted under. Masked, the first is unactionable and the second is
invisible — the confirmation checkbox would be the only clue that
anything was at stake.
Same for "no backup phrase yet, nothing to restore from" and the NUT-09
message naming a mint that cannot restore at all.
Caught only because the refusal paths were exercised against the live
node rather than trusted from the unit tests, which see the real message
and never meet the sanitizer.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
