From ac36ba4e0f44fed8444894ea87a2645faeb260c3 Mon Sep 17 00:00:00 2001
From: Anthony Ettinger <anthony@chovy.com>
Date: Sun, 5 Jul 2026 13:46:47 +0000
Subject: [PATCH 1/2] store: list CoinPay Wallet extension (coinpay-wallet)

Adds the registry listing for the CoinPay non-custodial MV3 wallet
(Phase 1). Bundle hosted as a GitHub release asset; sha256 pinned.

Publish path #2 (registry PR) per apps/extensions/registry/README.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .../registry/coinpay-wallet/listing.json           | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 apps/extensions/registry/coinpay-wallet/listing.json

diff --git a/apps/extensions/registry/coinpay-wallet/listing.json b/apps/extensions/registry/coinpay-wallet/listing.json
new file mode 100644
index 0000000..7d6c078
--- /dev/null
+++ b/apps/extensions/registry/coinpay-wallet/listing.json
@@ -0,0 +1,14 @@
+{
+  "slug": "coinpay-wallet",
+  "name": "CoinPay Wallet",
+  "summary": "Non-custodial multi-chain wallet with one-click x402 payments.",
+  "description": "CoinPay Wallet is a non-custodial, cross-browser (MV3) wallet for the CoinPay multi-chain platform.\n\n- Create or import a BIP-39 wallet; the seed is encrypted at rest (WebCrypto AES-256-GCM + PBKDF2) and never leaves your device.\n- Derives addresses for BTC, BCH, ETH, POL and SOL (with USDC on ETH/POL/SOL), matching the CoinPay web wallet.\n- Backup-confirmation gate before the wallet is usable; configurable idle auto-lock.\n\nThis Phase 1 release ships wallet lifecycle + receive/address views. Send and one-click x402 (HTTP 402) payment approval land in subsequent updates. Source: https://github.com/profullstack/coinpayportal/tree/master/packages/extension",
+  "homepage_url": "https://coinpayportal.com",
+  "version": "0.0.1",
+  "manifest_version": 3,
+  "permissions": ["storage", "alarms", "https://coinpayportal.com/*"],
+  "bundle_url": "https://github.com/profullstack/coinpayportal/releases/download/extension-v0.0.1/coinpay-wallet.zip",
+  "crx_url": null,
+  "bundle_sha256": "d9442a103f5d75888c946b8ca9b7dc1acf309c8533b098e65d1e7673031cf233",
+  "published_at": "2026-07-05T00:00:00.000Z"
+}

From 353030f509122972fe0655a44dec71b018c3ecb6 Mon Sep 17 00:00:00 2001
From: Anthony Ettinger <anthony@chovy.com>
Date: Sun, 5 Jul 2026 13:48:36 +0000
Subject: [PATCH 2/2] ci: fix extension-scan merge-base failure on shallow
 clones

The scan job fetched the base branch with --depth=1 and used a three-dot
git diff, which fails with 'no merge base' because the shallow base and PR
head share no common ancestor. Use fetch-depth: 0 so the diff resolves.
Affected every registry-PR listing.
---
 .github/workflows/extension-scan.yml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/extension-scan.yml b/.github/workflows/extension-scan.yml
index 81e31f7..e9da316 100644
--- a/.github/workflows/extension-scan.yml
+++ b/.github/workflows/extension-scan.yml
@@ -19,12 +19,17 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+        with:
+          # Full history so the three-dot diff below has a merge base with the
+          # base branch (a shallow --depth=1 fetch leaves them with no common
+          # ancestor: "fatal: origin/<base>...HEAD: no merge base").
+          fetch-depth: 0
 
       - name: Find changed listings
         id: changed
         run: |
-          git fetch origin "${{ github.base_ref }}" --depth=1
-          files=$(git diff --name-only "origin/${{ github.base_ref }}"...HEAD -- 'apps/extensions/registry/**/listing.json')
+          git fetch origin "${{ github.base_ref }}"
+          files=$(git diff --name-only "origin/${{ github.base_ref }}...HEAD" -- 'apps/extensions/registry/**/listing.json')
           echo "files<<EOF" >> "$GITHUB_OUTPUT"
           echo "$files" >> "$GITHUB_OUTPUT"
           echo "EOF" >> "$GITHUB_OUTPUT"