wip v28

Author: geraldarthurdavis

BITCODE_LIGHTPAPER.md

@@ -0,0 +1,38 @@
+# Bitcode: Lightpaper
+
+Bitcodes, or "*source shares*", are divisible units of measurable intelligence maintained on-chain.
+
+The **Bitcode Protocol** describes the systems that A. deterministically measure any material for its Bitcodes, B. prove, journal, and ledgerize all activity and finalities, and C. practically integrate into external industrial workflows for knowledge asset inflows and distributions and system interfacing.
+
+## Divisibility, Measuring, Minting, Assets
+
+### Semantic Indivisibility
+
+### Synthetic Measurements
+
+### Minting BTD-AssetPacks
+
+## Determinism, Proofs, Audits, Security
+
+### Models, Training, Inference
+
+### Proofs
+
+### Auditibility
+
+### Reliability, Security
+
+## Interfaces, Integrations
+
+### Bitcoin, Taproot
+
+### Cryptographic Wallets
+
+### Version Control Systems
+
+### Website Application
+
+### MCP API
+
+### Chat Applications
+

BITCODE_SPEC_V28.md

@@ -214,6 +214,7 @@ Acceptance criteria:
 - Exchange MVP activity/search/detail route renders without homepage redirects or disabled navigation.
 - signed-in navigation shows BTC and BTD balances as peer wallet facts, without `$BTD` currency-token styling, with a distinct visual separator, and with hover context reserved for recent BTD AssetPacks rather than explanatory product copy.
 - connected-wallet navigation is driven by wallet identity, not only by email/Supabase user state; a locally staged Bitcoin provider connection must replace anonymous `Connect Wallet` chrome with BTC/BTD posture while backend persistence is still pending.
+- Connects visibility is driven by wallet identity or an existing user session; once Profile has staged a Bitcoin wallet, Connects must render GitHub connection controls even when optional email/Supabase session persistence is still pending.
 - top-right BTD hover action shows the connected wallet nickname when available and otherwise shows the middle-truncated Bitcoin address; clicking it opens the `$BTD` wallet auxillary pane rather than treating the balance widget as an Exchange shortcut.
 - Profile owns Bitcoin wallet identity, robust wallet-provider readout, and optional email notification posture; Connects owns GitHub connection and future VCS/provider attachments.
 - V28 verbose QA telemetry may log wallet detection, wallet signing, local/server persistence, user-data merge, nav identity state, and BTD wallet pane entry behind `NEXT_PUBLIC_BITCODE_QA_VERBOSE=true`, `NEXT_PUBLIC_BITCODE_VERBOSE=true`, `?bitcode_verbose=true`, or `localStorage.bitcode.qa.verbose=true`.

BITCODE_SPEC_V28_NOTES.md

@@ -205,6 +205,7 @@ Profile must not render GitHub connection controls; it may point the operator to
 Connects owns GitHub because repository scope is shared by Terminal, Exchange rereads, conversations, and future interfaces.
 The top chrome must use wallet identity as a sufficient signed posture for BTC/BTD balance display even before Supabase/email identity is present.
 The BTD tracker hover/action area now identifies the connected wallet and opens the `$BTD` auxillary pane.
+Connects must use that same wallet identity as a sufficient prerequisite to render GitHub connection controls; optional email/Supabase session state may improve persistence and notifications, but must not hide the second onboarding step after Bitcoin wallet identity is staged.
 Verbose QA telemetry is allowed behind explicit flags so local testnet passes can observe provider detection, Leather/Xverse signing, local wallet persistence, user-data merge, navigation identity, and BTD auxillary entry without making normal production consoles noisy.
 
 These changes remain V28 scope because they are MVP-readiness and trust issues.

BITCODE_SPEC_V28_PARITY_MATRIX.md

@@ -144,7 +144,7 @@ Audit query classes:
 | Canon posture | V27 active / V28 draft in source posture carriers | closed |
 | Routes | unversioned UAPI route scan passes | closed |
 | Commercial app QA | primary route, auth, Auxillaries, Exchange, BTD range, conversations, docs article map, responsive health, URL-addressable filters, consent persistence, and stitched navigation/interaction E2E coverage | closed for expanded automated commercial MVP E2E baseline |
-| Auxillaries shell | contained tabs-left active experience without orbital layout collision, no visible auxillary Save buttons, stable first-open pane scroll, top-right overlay controls, no notification-footer Auxillaries launcher, wallet-first Profile order, GitHub-second source-provider order, optional-email-third posture, consistent mock/non-mock pane order, and BTD pane activity/table readability | pending manual reconfirmation after May 9 source fixes |
+| Auxillaries shell | contained tabs-left active experience without orbital layout collision, no visible auxillary Save buttons, stable first-open pane scroll, top-right overlay controls, no notification-footer Auxillaries launcher, wallet-first Profile order, GitHub-second source-provider order, Connects rendering from wallet identity before optional email/Supabase persistence, optional-email-third posture, consistent mock/non-mock pane order, and BTD pane activity/table readability | pending manual reconfirmation after May 9 source fixes |
 | Exchange MVP | activity/search/detail/range-acquisition route readiness | closed for master-detail MVP |
 | Terminal master-detail correction | Terminal must present itself as a Give/Need operator surface with recent/scoped activity results while Exchange owns the searchable master-detail activity table and selected detail | closed pending next manual QA confirmation |
 | Terminal clickable affordance | Known no-op or ambiguous click targets must be fixed, and clickable controls must be visually distinguishable from static badges/chips | partial; digest detail buttons and static overview badges corrected, broader manual pass remains |

BITCODE_V28_QA.md

@@ -330,6 +330,7 @@ Automated verification after this implementation pass:
 - `pnpm -C uapi run build`: pass after the May 9 QA fixes; the prior clean-clone Vercel module-resolution failure remains fixed locally.
 - Playwright non-mock browser smoke after the May 9 patch: `Connect Wallet` opens the contained Auxillaries shell, selector order is `Connects`, `Interfaces`, `Profile`, `$BTD`, old-ring count is `0`, Google prerequisite copy is absent, MetaMask and GitHub are present, no visible Save/Continue buttons remain, Profile first-open scroll advances, and no console/page errors occur.
 - May 9 live Leather QA: wallet connection persisted, but follow-up findings required V28 fixes for wallet-authenticated nav chrome, Profile/Connects ownership, robust connected-wallet readout, Sign Out button styling, BTD tracker wallet identity action, and verbose console telemetry. Source now treats local Bitcoin wallet identity as sufficient chrome identity while backend persistence catches up; Profile owns wallet/profile/email only; Connects owns GitHub; the BTD tracker opens the `$BTD` auxillary pane; and verbose QA logs are gated behind `NEXT_PUBLIC_BITCODE_QA_VERBOSE=true`, `NEXT_PUBLIC_BITCODE_VERBOSE=true`, `?bitcode_verbose=true`, or `localStorage.bitcode.qa.verbose=true`.
+- May 9 follow-up QA found Connects still showing the old signed-in blocker after the Bitcoin wallet was correctly connected. V28 fixes Connects to render GitHub controls from wallet identity or email session, so Profile wallet completion can progress directly into repository connection without waiting on optional email/Supabase persistence.
 - `pnpm -C uapi exec tsc --noEmit --pretty false`: pass after the formal protocol package split.
 - `pnpm -C uapi run test:e2e:commercial-mvp`: 50 passed after Conversations streaming, Conversations exit, and Terminal transaction-search stabilization.
 - `npm --prefix protocol-demonstration run test:integration`: 58 passed after standalone demonstration/package-boundary cleanup.

uapi/app/auxillaries/components/AuxillariesConnectsPane.tsx

@@ -8,6 +8,7 @@ import { VCSIntegrationPanel } from '@/components/base/bitcode/vcs/VCSIntegratio
 import { getRepositoryInventorySourceLabel } from '@/app/terminal/terminal-repository-context';
 import { deriveBitcodeTransactionReadiness } from '@/app/terminal/bitcode-transaction-readiness';
 import { useUserData } from '@/hooks/useUserData';
+import { bitcodeQaTelemetry } from '../../../lib/bitcode-qa-telemetry';
 
 import AuxillariesConnectsPaneHeader from '@/app/auxillaries/components/headers/AuxillariesConnectsPaneHeader';
 
@@ -41,12 +42,38 @@ export default function AuxillariesConnectsPane({
     refresh,
   } = useUserData();
 
+  const hasConnectsIdentity = Boolean(user || hasWalletConnection);
+
+  useEffect(() => {
+    onCompletionStatusChange?.(Boolean(hasConnectsIdentity && hasValidGitHubConnection));
+  }, [hasConnectsIdentity, hasValidGitHubConnection, onCompletionStatusChange]);
+
   useEffect(() => {
-    onCompletionStatusChange?.(Boolean(user && hasValidGitHubConnection));
-  }, [hasValidGitHubConnection, onCompletionStatusChange, user]);
+    bitcodeQaTelemetry('info', 'auxillaries.connects', 'readiness', {
+      hasEmailSession: Boolean(user),
+      hasWalletConnection,
+      hasConnectsIdentity,
+      hasGitHubConnection,
+      hasValidGitHubConnection,
+      walletBindingStatus,
+      walletProvider: walletConnectionStatus?.provider ?? null,
+      repositoryProvider: repositoryConnectionStatus?.provider ?? null,
+      repositoryValid: repositoryConnectionStatus?.valid ?? null,
+    });
+  }, [
+    hasConnectsIdentity,
+    hasGitHubConnection,
+    hasValidGitHubConnection,
+    hasWalletConnection,
+    repositoryConnectionStatus?.provider,
+    repositoryConnectionStatus?.valid,
+    user,
+    walletBindingStatus,
+    walletConnectionStatus?.provider,
+  ]);
 
   const transactionReadiness = deriveBitcodeTransactionReadiness({
-    signedIn: Boolean(user),
+    signedIn: hasConnectsIdentity,
     hasRepositoryProvider: hasGitHubConnection,
     hasValidRepositoryProvider: hasValidGitHubConnection,
     hasWalletBinding: hasWalletConnection,
@@ -59,12 +86,14 @@ export default function AuxillariesConnectsPane({
       <div className="orbital-step-content connects-step">
         <AuxillariesConnectsPaneHeader isOnboardingComplete={isOnboardingComplete} />
 
-        {!user ? (
+        {!hasConnectsIdentity ? (
           <div className="space-y-4 rounded-[24px] border border-white/10 bg-black/20 p-5 text-white/80">
             <div className="space-y-2">
-              <h3 className="text-lg font-semibold text-white">Sign in to open Connects</h3>
+              <h3 className="text-lg font-semibold text-white">Connect Bitcoin wallet first</h3>
               <p className="text-sm leading-7 text-white/68">
-                Sign in first, then attach GitHub so need measurement, asset-pack synthesis, and settlement follow-through can operate against a live repository source.
+                Connect a Bitcoin-capable wallet in Profile, then attach GitHub here so need
+                measurement, asset-pack synthesis, and settlement follow-through can operate
+                against a live repository source.
               </p>
             </div>
 

uapi/jest.config.cjs

@@ -107,6 +107,7 @@ module.exports = {
     '<rootDir>/tests/featureFlagsMockMode.test.ts',
     '<rootDir>/tests/bitcoinWalletClient.test.ts',
     '<rootDir>/tests/auxillariesWorkspacePanels.test.tsx',
+    '<rootDir>/tests/auxillariesConnectsPane.test.tsx',
     '<rootDir>/tests/btdTrackerLoading.test.tsx',
     '<rootDir>/tests/notificationsWidget.test.tsx',
     '<rootDir>/tests/orbitalsBTDPane.test.tsx',

uapi/tests/auxillariesConnectsPane.test.tsx

@@ -168,6 +168,58 @@ describe('AuxillariesConnectsPane', () => {
     expect(screen.getByText(/write admission will fail closed until the live provider connection is restored/i)).toBeInTheDocument();
   });
 
+  it('renders GitHub connection controls from wallet identity before optional email session exists', () => {
+    mockUseAuth.mockReturnValue({
+      user: null,
+      loading: false,
+    } as any);
+
+    mockUseUserData.mockReturnValue({
+      data: {
+        profile: {
+          wallet_address: 'tb1qleatheroperator',
+          wallet_provider: 'leather',
+        },
+      },
+      hasGitHubConnection: false,
+      hasValidGitHubConnection: false,
+      hasWalletConnection: true,
+      hasStoredVerifiedWalletConnection: false,
+      hasVerifiedWalletConnection: false,
+      walletBindingStatus: 'pending',
+      walletConnectionStatus: {
+        connected: true,
+        provider: 'leather',
+        valid: true,
+        address: 'tb1qleatheroperator',
+        verificationState: 'pending',
+      },
+      repositoryConnectionStatus: null,
+      repositories: [],
+      repositoryInventorySource: null,
+      organizations: [],
+      btdBalance: 0,
+      isLoading: false,
+      error: null,
+      refresh: jest.fn(),
+      isOnboardingComplete: false,
+      onboardedSteps: ['profile'],
+    } as any);
+
+    render(
+      <AuxillariesConnectsPane
+        onSave={jest.fn()}
+        loading={false}
+        isOnboardingComplete={false}
+      />,
+    );
+
+    expect(screen.getByText('Connect GitHub for source-bearing input')).toBeInTheDocument();
+    expect(screen.getByTestId('mock-vcs-integration-panel')).toBeInTheDocument();
+    expect(screen.queryByText(/Sign in to open Connects/i)).not.toBeInTheDocument();
+    expect(screen.queryByText(/Connect Bitcoin wallet first/i)).not.toBeInTheDocument();
+  });
+
   it('treats a saved verified wallet signer without a live wallet-provider session as reconnect-required settlement posture', () => {
     mockUseUserData.mockReturnValue({
       data: {