Testing and launch
Local verification
Build the SDK before running browser tests. The suite exercises consent, denial, login return, the real SDK button, connection revocation, separate caps, the fourth-session tail and checkout recovery. APIs and Stripe are mocked: passing these tests does not prove live provider or Stripe behavior.
Partner acceptance
Use a registered pilot app to verify Connect → consent → callback → refresh persistence → Kimi completion → usage. Connect two apps to one account and verify shared counters. Revoke one app and confirm it loses access while the other keeps access. Reject wrong callback state and never capture credentials in logs.
Outstanding production gates
Live Stripe prices and webhook delivery, PostgreSQL concurrency, EU provider verification, lifecycle delivery, reconciliation recovery, Archiveye integration and package publication still require completion. These docs describe a pilot contract, not a completed production launch.
pnpm --dir packages --filter @pura-ai/sdk build
pnpm --dir e2e exec playwright test --config pura-llm/oauth-connect.playwright.config.ts
PYTHONPATH=pura-llm/backend pura-llm/backend/.venv/bin/python -m pytest pura-llm/backend/tests -q