Credentials page cannot authorize agent wallet without NEXT_PUBLIC_PRIVY_SIGNER_ID

[nboufeld]

Problem

On /app/credentials, clicking the agent wallet authorization flow can fail immediately with:

Missing NEXT_PUBLIC_PRIVY_SIGNER_ID env var.

This happens client-side before useSigners().addSigners(...) or POST /api/agent-delegation can run.

Code paths

• frontend/app/app/credentials/AgentDelegationCard.tsx reads process.env.NEXT_PUBLIC_PRIVY_SIGNER_ID into SIGNER_ID and returns that error when it is missing.
• addSigners needs that signer ID to attach the Privy server-side signer/quorum to the user's Solana wallet.
• The MCP submission path also checks profiles.wallet_pubkey and profiles.github_handle before accepting submissions.

Impact

Developers can appear connected in the web UI but still cannot delegate the wallet for MCP agent submissions. As a result, submissions.create remains blocked for accounts whose MCP profile has no wallet pubkey / linked GitHub handle.

Expected

Production/frontend deployments should include NEXT_PUBLIC_PRIVY_SIGNER_ID matching the signer configured in Privy, and the deployment should be rebuilt so the public env var is present in the client bundle.

It would also help to ensure the profile row gets populated with wallet_pubkey and github_handle during onboarding or delegation, since MCP auth reads those fields from profiles.