feat: suspense-compatible direct API usage

[gudnuf]

Summary

• Adds a configure() function and exports all API functions directly from the package, enabling usage without the React context provider
• This makes the SDK compatible with React Suspense and data-fetching libraries like TanStack Query
• The existing OpenSecretProvider / useOpenSecret pattern still works but is marked as deprecated

Changes

• New src/lib/config.ts: Global configuration singleton (configure, getConfig, isConfigured, resetConfig)
• src/lib/api.ts: Removed client_id parameter from 10 auth functions — they now read it internally from the global config via getConfig()
• src/lib/index.ts: Exports all API functions directly with friendly aliases (signIn, signUp, get, put, del, etc.), plus config, attestation, and AI helper exports
• src/lib/main.tsx: OpenSecretProvider now delegates to configure() internally; removed clientId from all internal API calls
• src/lib/context.ts: Added @deprecated JSDoc to useOpenSecret()
• Test files: All integration tests updated to use centralized test/setup.ts for SDK configuration

Usage

import { configure, signIn, get, put, fetchUser } from "@opensecret/react";

// Configure once at app initialization
configure({ apiUrl: "https://...", clientId: "your-uuid" });

// Use functions directly — works with Suspense, TanStack Query, etc.
await signIn(email, password);
const user = await fetchUser();
const value = await get("key");

Test plan

• TypeScript compiles cleanly (tsc --noEmit and tsc -p tsconfig.build.json)
• Integration tests pass against a live backend
• Verify existing provider-based usage still works (backward compatible)

Based on jbojcic1/OpenSecret-SDK#1, adapted for the latest SDK version.

🤖 Generated with Claude Code