Improve signer setup segment readability on Passport QR flow

[Copilot]

The signer setup UI had low-contrast segmented options (Singlesig/Multisig) on the Passport QR setup screen, making the inactive option hard to read in light mode. This reduced scannability at a critical mode-selection step.

• Scope

  • Updated the shared segmented control used by signer setup flows to ensure inactive primary labels render with explicit themed contrast.
  • Kept interaction behavior, selection state, animation, and derivation-mode logic unchanged.

• UI implementation

  • File: src/components/SegmentController.tsx
  • Change: apply an explicit theme color to the unselected main label while preserving the existing selected override.

<Text
  style={[styles.label, selectedIndex === index && { color: Colors.headerWhite }]}
  color={`${colorMode}.secondaryText`}
>
  {option.label}
</Text>

• OpenSpec artifacts
  • Added and archived a focused spec change for segmented-option readability:
    • signer-setup-segment-visibility

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• blackie.c3-soft.com
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/bitcoin-keeper/bitcoin-keeper/node_modules/jest-worker/build/workers/processChild.js es/.bin/sh node /bit�� e git k/bitcoin-keeper-Wl,-soname=secp256k1.node ssues-on-multiplsh l/config run-script/lib/npatch-package e (dns block)
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/bitcoin-keeper/bitcoin-keeper/node_modules/jest-worker/build/workers/processChild.js it-clone6vYirX/nmkdir -p "Release/obj.target/" "./Release/.deps/Release/obj.target/" /bin/sh 1/x6�� ln -f "Release/-I git in/as ssues-on-multiplsh commit.gpgsign ode_modules/.binpatch-package e m/_c�� e git k/bitcoin-keeper/bitcoin-keeper/-I nOnly l/config son l/openssl/include (dns block)
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/bitcoin-keeper/bitcoin-keeper/node_modules/jest-worker/build/workers/processChild.js node_modules/.biRelease/obj.target/ node-gyp-build-t./Release/.deps/Release/obj.target/ (dns block)
• invalid.host
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/bitcoin-keeper/bitcoin-keeper/node_modules/jest-worker/build/workers/processChild.js node_modules/.biRelease/obj.target/ node-gyp-build-t./Release/.deps/Release/obj.target/ (dns block)
• mempool.space
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/bitcoin-keeper/bitcoin-keeper/node_modules/jest-worker/build/workers/processChild.js es/.bin/sh node /bit�� e git k/bitcoin-keeper-Wl,-soname=secp256k1.node ssues-on-multiplsh l/config run-script/lib/npatch-package e (dns block)
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/bitcoin-keeper/bitcoin-keeper/node_modules/jest-worker/build/workers/processChild.js it-clone6vYirX/nmkdir -p "Release/obj.target/" "./Release/.deps/Release/obj.target/" /bin/sh 1/x6�� ln -f "Release/-I git in/as ssues-on-multiplsh commit.gpgsign ode_modules/.binpatch-package e m/_c�� e git k/bitcoin-keeper/bitcoin-keeper/-I nOnly l/config son l/openssl/include (dns block)
• static.realm.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/bitcoin-keeper/bitcoin-keeper/node_modules/.bin/prebuild-install --runtime napi er.o�� ')); (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)