Pay an npub: ark > lightning > on-chain, and fix the orphaned LN seams

Picking a search result (or pasting an npub) now resolves every way the
person can be paid and takes the best: their kind-10037 ark advert; an
ark= instruction in BIP-353 via their coinos name (registrar /pubkey
returns the URI directly) or their nip05 name's own DNS record (a bare
domain is the BIP-353 "_" user); then Lightning from profile lud16/
lud06 through the zap flow; then a BIP-353 on-chain address as last
resort. Search results no longer put the nip05 identifier in the fill
value — that's how fiatjaf.com ended up as a dead recipient.

Along the way: the zaps feature's canLnPay/startLnPay seams had no
provider since the swaps feature retired, so the whole Lightning-zap
path was unreachable. Ark provides both now (the ASP pays invoices
natively), which also revives zapping any LN-only npub.

Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Wvj4aoeMZwA7VUGdJP9Swi

1 files changed, 1 insertions, 1 deletions

diff --git a/src/i18n.js b/src/i18n.js
index 8ca63cc..09c9b07 100644
--- a/src/i18n.js
+++ b/src/i18n.js
@@ -445,7 +445,7 @@ const STR = {
     arkExitNoBalance: 'Nothing in Spending to move.',
     arkZapTitle: 'Send a zap',
     arkZapLookup: 'Looking them up…',
-    arkZapNoArk: 'This nostr user can’t receive instant payments yet.',
+    arkZapNoArk: 'No way to pay this account was found — no Ark address, Lightning address, or payment record.',
     arkZapHint: 'Instant and free, with a zap receipt on nostr.',
     arkZapCommentPh: 'Comment (optional)',
     arkZapBtn: 'Zap',