Files
amethyst/commonsUI
Claude c3cecf1e9f fix(qr): correct the bunker message, and pin what the scanner sheet has to explain
While looking into routing more scanned payloads I found the reverse: the
scanner's explanation sheet told users to add a bunker:// address "from the
NIP-46 signer screen", which cannot accept one. Amethyst *publishes* bunker
addresses — it is the remote signer — and the signer screen pairs nostrconnect://
offers only; remote-signer login exists on Desktop and even there it generates a
nostrconnect:// rather than consuming a bunker URI. Split the string so bunker
and nostrconnect each say something true.

The investigation also showed raw nostr+walletconnect:// URIs already route,
via the fallback at the end of uriToRoute rather than the dlnwc?value= branch
above it. Both behaviours are now pinned by tests, because what uriToRoute
returns null for is exactly what that sheet has to explain.

Also set LANG/LC_ALL to C.UTF-8 for agent sessions. Without a UTF-8 locale
sun.jnu.encoding is ASCII, and `./gradlew test` fails while *writing its HTML
report* — after every test has passed — because eleven test names across four
modules contain an em dash. It cost a full 12-minute run this session and would
cost one in every future session.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0134jvyriixNTHST4WRbbqbX
2026-09-15 19:23:22 +00:00
..