5 Commits

Include renames

Author	SHA1	Message	Date
archipelago	3347b8b8b9	fix(ui): https app launches and the nostr bridge follow the frame's real origin ... Three launcher/bridge defects combined to make HTTPS dashboards look broken while HTTP ones worked: 1. portAuth() looked the launch port up under the name the user clicks ('mempool-web', 'lnd', 'bitcoin-knots'…), but the signed catalog declares those ports under the manifest id that owns them (archy-mempool-web, lnd-ui, bitcoin-ui). The lookup missed, portIsGateFronted answered false, and an HTTPS dashboard handed app frames http:// URLs — blocked as mixed content: mempool and IndeeHub 'did not connect', bitcoin knots/core opened http:// in a new tab. Resolution now follows launch aliases, then a port-wide catalog scan that only answers when every declarer of that port agrees (a port any app publishes as plain HTTP is never upgraded to https). 2. The signed-catalog cache was only warmed by the Store/Discover views, so a user who went straight to My Apps launched apps with an empty cache. Warmed at dashboard mount now — fetchAppCatalog() already memoizes with a 1h TTL. 3. The NIP-07 bridge compared event.origin for strict equality with the recorded (http) app URL and replied to the recorded URL as the postMessage targetOrigin — both break the moment a frame is scheme- upgraded (cached HSTS did exactly that): every nostr request was silently dropped and replies to the stale origin threw. The bridge now matches host+port (scheme deliberately ignored) and always replies to event.origin — the frame's real origin. Unit tests cover alias resolution (incl. bitcoin-knots→8334→https), the conservative port-scan, and scheme-agnostic sender matching.	2026-09-01 10:29:05 -04:00
archipelago	192e045426	feat(ui): SSH-over-mesh card, store-listing filter, icon treatment ... Settings gains the SSH-over-mesh card (danger-zone confirmation for the any-peer scope, sshd preflights, fipssh copy hint). The signed-catalog merge filters components via the shared serviceNames module; Discover grids get the standard icon container; install no longer yanks the user to My Apps; v1.8.8 release notes.	2026-09-01 02:41:55 -04:00
archipelago	46cb0bfd37	fix(ui): gate-fronted https launches + signed-catalog App Store ... directAppUrl(), the legacy open() path, and resolveRuntimeLaunchUrl() now upgrade to https only for ports the app gate fronts — decided from the signed catalog's embedded manifest ports (auth gated/open), so plain-HTTP publishes (legacy installs, auth:none API ports like Cuprate's RPC) keep http instead of failing outright. fetchAppCatalog() merges the daemon-verified signed catalog into the App Store listing (signed entries appear immediately; community copy supplies featured and curated metadata), and Marketplace.vue uses the same dynamic fetcher as Discover so the grid sees signed-new apps too.	2026-08-31 18:41:00 -04:00
Dorian	d259f3cbb9	fix(web): companion-gate the store banner + manual intro trigger (#61 residual) ... Only the auto-popup was companion-gated — inside the companion WebView users still saw the 'install the companion' banner in the App Store and could pop the intro overlay through it. Gates all three paths on isCompanionApp(): CompanionBanner self-hides, openCompanionIntro() is a no-op, and the manual-open watcher in CompanionIntroOverlay refuses to open (the overlay's raw window check also moves to the canonical helper so there is exactly one detection). No APK change.	2026-08-31 12:56:32 +01:00
Archipelago	b67e1527a2	Archipelago — open-source initial import	2026-08-12 10:55:50 +00:00