2 Commits

Include renames

Author	SHA1	Message	Date
archipelagoandClaude Opus 5	fa26c5fc56	fix(wallet): gate lightning on node STATE, gate send too, add a shared CopyButton ... Three defects from testing the previous commit on archi-dev-box: 1. The gate keyed on `id in packages`, which is not "installed and usable" — package-data carries an entry for a Lightning app that is known but not running. On a box with no lnd container at all the gate passed and the raw error came through as "Operation failed. Check server logs for details." Now keyed on PackageState.Running. 2. Because installed-but-stopped is a real and different situation, the modal has two modes: absent offers the install choices, stopped says the node isn't running and offers "Open My Apps". Neither dead-ends in an error. 3. Lightning SEND let you walk all the way to confirm-send with no node. The gate now runs in review(), before the confirm step — failing at submit after a review screen is the defect, not a smaller version of it. Also adds CopyButton, the start of one consistent copy affordance: icon + label, an emerald tick held 1.6s, a fixed box so the width never jumps, and a document.execCommand fallback so copy still works over plain http on a LAN IP (navigator.clipboard rejects on insecure origins, which is how a lot of nodes are reached). Converted the wallet's own copies — the lightning invoice the user reported, plus the on-chain/Ark addresses and the payment hash/txid. 20 of 25 copy sites across 15 other files still use ad-hoc markup; converting them is mechanical but was not attempted here rather than half-done. Verified: 5 gate tests; npm run build clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-02 07:36:25 -04:00
archipelagoandClaude Opus 5	5718179e2f	feat(wallet): offer to install a Lightning node instead of failing an invoice ... Creating a Lightning invoice with no Lightning implementation installed failed at the RPC layer — lnd.createinvoice returned connection-refused and the Receive screen rendered it as a red error. That reads as the wallet being broken when the node simply has no Lightning node installed yet. useLightningRequired() gates the three invoice paths (wallet Receive, the Web5 send/receive sheet, and the app launcher's paywall — both arms there, since paying an invoice needs a node as much as minting one). With none installed it raises a modal offering to install one and the caller bails without surfacing an error at all. The modal lists the choice rather than assuming LND: LND installs today, Core Lightning is listed greyed as "Coming soon" so the platform doesn't read as LND-only. When CLN ships it is two lines — flip `available` and add the id to LIGHTNING_NODE_APP_IDS. Detection is install state, NOT reachability, deliberately: an installed node that is merely stopped or still starting is a different problem ("start it") and must not be answered with "install a Lightning node". Also fixes the credentials modal, which painted its own rgba(8,10,18,.98) navy card instead of the house glass-card — it read as blue against every other modal. It existed twice (Apps.vue and apps/AppIconGrid.vue); both now use BaseModal, so they also inherit Esc/focus handling, body scroll lock and the standard pinned-header/footer scroll contract they were missing. Dead panel CSS removed from both. Verified: 4 new tests; full suite 103 files / 826 tests green; npm run build clean with the new strings present in the built bundle. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-02 07:23:37 -04:00