V48 Gate 1: Update Track 1 rollup for reconnect auth_source; family authoring moves to its own gate

The signed-in Leather reconnect rewrites the wallet connection auth_source
from bitcoin_wallet_oauth_identity to bitcoin_wallet_provider, so the
rollup's wallet join now accepts both and surfaces payment_address,
proof_kind, and auth_source. Notes clarify the full V48 draft family opens
in a dedicated authoring gate; Gate 1 closes as the identity/auth QA gate.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: geraldarthurdavis

BITCODE_SPEC_V48_NOTES.md

@@ -13,7 +13,7 @@
 - Scope: V48 starts as the interactive local experiential QA target over promoted V47 commercial website testnet launch canon.
 - QA findings ledger: `BITCODE_V48_QA.md` (the running record of accepted V48 findings and repairs)
 - Gate 1 (in progress): identity and authentication interactive QA on branch `v48/gate-1-identity-auth-interactive-qa`
-- Full draft family (`BITCODE_SPEC_V48.md`, `BITCODE_SPEC_V48_DELTA.md`, `BITCODE_SPEC_V48_PARITY_MATRIX.md`) opens at Gate 1 closure, per the V47 Gate 1 precedent
+- Full draft family (`BITCODE_SPEC_V48.md`, `BITCODE_SPEC_V48_DELTA.md`, `BITCODE_SPEC_V48_PARITY_MATRIX.md`) opens in a dedicated specification-authoring gate once the interactive QA tracks have accumulated the specification intent; Gate 1 closed as the identity/authentication QA-and-repairs gate
 
 ## Notes-only draft rule
 

supabase/queries/v48_qa_05_track1_readiness_rollup.sql

@@ -2,8 +2,13 @@
 -- Purpose: one-row Track 1 identity summary — session, identity, profile,
 -- wallet binding, GitHub installation, repository count.
 -- Run: anytime; the quick "where does Track 1 stand" check.
--- Expect (Track 1 complete): session_minted true, wallet binding populated,
--- github_installation_id present, repository_count > 0.
+-- Expect (Track 1 complete): session_minted true, wallet binding populated
+-- (payment_address fills after the signed-in reconnect; proof_kind is
+-- provider_session for identity-derived binds and bitcoin_message_signature
+-- after reconnect), github_installation_id present, repository_count > 0.
+-- Note: the wallet connection's auth_source is bitcoin_wallet_oauth_identity
+-- for identity-derived binds and bitcoin_wallet_provider after the signed-in
+-- panel reconnect — the join accepts both.
 
 WITH qa_user AS (
   SELECT id
@@ -18,8 +23,11 @@ SELECT
   i.identity_data ->> 'sub' AS bitcoin_subject,
   p.username,
   p.settings #>> '{bitcodeProfile,walletBinding,address}' AS wallet_address,
+  p.settings #>> '{bitcodeProfile,walletBinding,paymentAddress}' AS payment_address,
+  p.settings #>> '{bitcodeProfile,walletBinding,proofKind}' AS wallet_proof_kind,
   p.settings #>> '{bitcodeProfile,walletBinding,status}' AS wallet_status,
   wallet.provider AS wallet_connection_provider,
+  wallet.connection_data ->> 'auth_source' AS wallet_auth_source,
   wallet.is_active AS wallet_active,
   github.connection_data ->> 'installation_id' AS github_installation_id,
   github.connection_data ->> 'account_login' AS github_account,
@@ -32,7 +40,7 @@ LEFT JOIN public.user_profiles p
   ON p.id = u.id
 LEFT JOIN public.user_connections wallet
   ON wallet.user_id = u.id
- AND wallet.connection_data ->> 'auth_source' = 'bitcoin_wallet_oauth_identity'
+ AND wallet.connection_data ->> 'auth_source' IN ('bitcoin_wallet_oauth_identity', 'bitcoin_wallet_provider')
 LEFT JOIN public.user_connections github
   ON github.user_id = u.id AND github.provider = 'github'
 WHERE u.id IN (SELECT id FROM qa_user);