fix(profile): display-name in QR title, verify NIP-05/lud16, normalize CLINK CTA weight

[dmnyc]

Three small, related polish fixes on the profile surface.

1. Use display name in the profile QR/share modal title

The QR/share modal that opens from the profile page (e.g. daniel's Profile) was reading profile.name (the short handle) instead of the full display name. Now it prefers displayName → display_name → name, so the title reads The Daniel 🖖's Profile for users who have a display name set.

src/routes/user/[slug]/+page.svelte — one-line change.

2. Verify NIP-05 and Lightning Address inputs in the profile editor

The profile editor's NIP-05 and Lightning Address fields previously accepted anything — including malformed addresses like daniel@nodestrich or syntactically-valid-but-wrong ones like daniel@nodestrich.co (which has a real TLD but doesn't map to your pubkey).

Each input now has five states with clear visual indication:

State	Border	Trailing icon	Helper text
Empty	default	—	—
Regex-invalid (e.g. foo@bar)	red	red ⚠	"Use the form name@example.com"
Resolving	default	spinner	—
Verified	green	green ✓	—
Unresolved	amber	amber ⚠	reason from the server

• NIP-05 fetches https://<domain>/.well-known/nostr.json?name=<local> and only goes green if the returned names[local] matches the signed-in pubkey. Otherwise it shows a specific reason (<domain> has no entry for "<local>" / Domain points to a different pubkey than yours / Could not reach <domain> (<status>)).
• Lightning Address fetches https://<domain>/.well-known/lnurlp/<local> and checks the response is a valid LNURL payRequest with a callback.

Fetches are debounced 500 ms and aborted on the next keystroke. The Save button is disabled only on regex-invalid (hard fail); unresolved is a soft warning because some valid lnurlp endpoints don't send CORS headers and would otherwise be unfairly blocked.

src/components/ProfileEditModal.svelte — adds verification handlers, status state, and per-state markup on both inputs.

3. Normalize the CLINK CTA weight on the profile page

<NofferButton variant="cta"> on the profile page was using font-weight: 700 (bold) while the Send Zap and Copy npub buttons it sits next to use Tailwind font-medium (500). The CLINK button visually dominated the row. Moved the heavy weight to the inline pill variant (where it competes with body text and needs the punch) and set the CTA variant to 500 so the row reads as peers.

src/components/clink/NofferButton.svelte.

Test plan

• Open any profile's QR/share modal — title shows the display name with emoji, not the username
• Profile editor → NIP-05: type name@, see red ⚠ + helper text; type a real NIP-05 you own, see green ✓; type one mapped to someone else's domain, see amber ⚠ + "Domain points to a different pubkey than yours"
• Profile editor → Lightning Address: same shape; verifies against /.well-known/lnurlp
• Save button disabled while either field is regex-invalid
• Profile page → CLINK button weight visually matches Send Zap, not bolder