fix(frontend): keep the public wallet config in the repo, not in deployment secrets

.github/workflows/frontend-dev.yaml

@@ -26,9 +26,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Build Docker image
-        # Unset secrets are not a build failure: wallet config is read lazily inside the guard section,
-        # so the dashboard still renders and the delegate button shows "wallet delegation unavailable".
-        run: docker build --build-arg VITE_DEPLOYMENT_ENV=dev --build-arg VITE_RPC_URL=${{ secrets.VITE_RPC_URL }} --build-arg VITE_WAGMI_ID=${{ secrets.VITE_WAGMI_ID }} -f frontend/Dockerfile -t ${{ env.DOCKER_TAGS }} .
+        run: docker build --build-arg VITE_DEPLOYMENT_ENV=dev -f frontend/Dockerfile -t ${{ env.DOCKER_TAGS }} .
 
   deploy:
     name: Deploy Frontend to DEV
@@ -56,12 +54,8 @@ jobs:
           push: true
           tags: ${{ env.DOCKER_TAGS }}
           platforms: linux/arm64
-          # Unset secrets are not a build failure: wallet config is read lazily inside the guard section,
-          # so the dashboard still renders and the delegate button shows "wallet delegation unavailable".
           build-args: |
             VITE_DEPLOYMENT_ENV=dev
-            VITE_RPC_URL=${{ secrets.VITE_RPC_URL }}
-            VITE_WAGMI_ID=${{ secrets.VITE_WAGMI_ID }}
 
       - name: Install cloudflared
         run: |

.github/workflows/frontend-prd.yaml

@@ -26,9 +26,7 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Build Docker image
-        # Unset secrets are not a build failure: wallet config is read lazily inside the guard section,
-        # so the dashboard still renders and the delegate button shows "wallet delegation unavailable".
-        run: docker build --build-arg VITE_DEPLOYMENT_ENV=prd --build-arg VITE_RPC_URL=${{ secrets.VITE_RPC_URL }} --build-arg VITE_WAGMI_ID=${{ secrets.VITE_WAGMI_ID }} -f frontend/Dockerfile -t ${{ env.DOCKER_TAGS }} .
+        run: docker build --build-arg VITE_DEPLOYMENT_ENV=prd -f frontend/Dockerfile -t ${{ env.DOCKER_TAGS }} .
 
   deploy:
     name: Deploy Frontend to PRD
@@ -56,12 +54,8 @@ jobs:
           push: true
           tags: ${{ env.DOCKER_TAGS }}
           platforms: linux/arm64
-          # Unset secrets are not a build failure: wallet config is read lazily inside the guard section,
-          # so the dashboard still renders and the delegate button shows "wallet delegation unavailable".
           build-args: |
             VITE_DEPLOYMENT_ENV=prd
-            VITE_RPC_URL=${{ secrets.VITE_RPC_URL }}
-            VITE_WAGMI_ID=${{ secrets.VITE_WAGMI_ID }}
 
       - name: Install cloudflared
         run: |

frontend/.env.example

@@ -2,13 +2,18 @@ VITE_API_BASE_URL=http://localhost:3001
 # or for remote backend
 # VITE_API_BASE_URL=https://dev.monitoring.juicedollar.com/api
 
-# Wallet / Guard Delegation section (required for the Delegate button). Read fail-loud in
-# src/lib/wagmi.ts — a missing value throws inside the lazy WalletProvider boundary (no silent
-# fallback), so the rest of the read-only dashboard keeps running. Only the Delegate button uses
-# these; the read path (signer / voting-power % / gas / helpers) comes from the backend /guard
-# endpoint and works without them.
+# Wallet config for the Guard Delegation section. Both values are PUBLIC — they are baked into the
+# browser bundle and visible to anyone who opens the dashboard — so they are NOT deployment secrets:
+# the shipped defaults live in frontend/Dockerfile and can be overridden per build with --build-arg.
+# Set them here only for the local dev server, or to point at a different endpoint or project.
+#
+# They are read fail-loud in src/lib/wagmi.ts, but the failure stays contained: a missing value throws
+# inside the lazy WalletProvider boundary, so the read-only dashboard keeps working and only the
+# Delegate button shows "wallet delegation unavailable". The status half (signer, voting power,
+# qualification, helper count, gas) comes from the backend /guard endpoint and needs neither value.
 
-# Citrea RPC URL for the wagmi http() transport (browser-visible — use a public/rate-limited endpoint).
-VITE_RPC_URL=https://your-citrea-rpc-provider.com
-# WalletConnect / Web3Modal project id (reuse the dapp's id).
-VITE_WAGMI_ID=your-walletconnect-project-id
+# Citrea RPC URL for the wagmi http() transport. The public endpoint the backend uses also answers
+# browser requests, so it works here as-is.
+VITE_RPC_URL=https://rpc.citreascan.com
+# WalletConnect project id — identifies the dapp to the relay, public by design.
+VITE_WAGMI_ID=b49c3a590c4407316a6fd6eae6531e90

frontend/Dockerfile

@@ -12,9 +12,20 @@ ARG VITE_API_BASE_URL=/api
 ENV VITE_API_BASE_URL=$VITE_API_BASE_URL
 ARG VITE_DEPLOYMENT_ENV
 ENV VITE_DEPLOYMENT_ENV=$VITE_DEPLOYMENT_ENV
-ARG VITE_RPC_URL
+# Wallet config for the guard delegation section. Both values are PUBLIC by nature — they are baked
+# into the browser bundle and visible to anyone who opens the dashboard — so they belong here as
+# defaults rather than in deployment secrets, the same way VITE_API_BASE_URL does above. Override per
+# build with --build-arg if a deployment needs a different endpoint or project.
+# The Citrea RPC is the same public endpoint the backend uses and answers browser requests
+# (access-control-allow-origin: *). The WalletConnect project id identifies the dapp to the relay.
+#
+# COUPLING: the delegate action builds its chain from the chain id the BACKEND reports at /guard, while
+# this RPC URL is fixed here. Repointing the backend at another network (BLOCKCHAIN_ID / RPC_URL) without
+# overriding VITE_RPC_URL in the same breath leaves the wallet transport talking to Citrea while the
+# declared chain id says otherwise — transactions can look unconfirmed in the UI. Change both together.
+ARG VITE_RPC_URL=https://rpc.citreascan.com
 ENV VITE_RPC_URL=$VITE_RPC_URL
-ARG VITE_WAGMI_ID
+ARG VITE_WAGMI_ID=b49c3a590c4407316a6fd6eae6531e90
 ENV VITE_WAGMI_ID=$VITE_WAGMI_ID
 RUN npm run build