Adapter verification
Adapter verification status and live setup
Section titled “Adapter verification status and live setup”Recorded 2026-10-17. Mock/type checks and compatible services do not establish connectivity to the hosted provider.
| Adapter | Level | Checked | Unverified | Settings and prerequisites |
|---|---|---|---|---|
| createAISDKChatAdapter / createOpenAICompatibleChatAdapter | 単体・streaming fixtures/unit/stream fixtures | メッセージ変換・streaming・cancel/error・packed consumer。 / Message conversion/streaming/cancel/errors and packed consumers. | モデルproviderへの課金API・実トークン認証・品質。 / Paid provider API, actual credentials and model quality. | Adapters accept api (URL), headers and optional fetch; OpenAI-compatible mode also requires model. Configure the application BFF/provider credentials and an authorized test model/budget. No live model runner. |
Reproduction
# public/ root; Docker + Node >=24 + Bun 1.4.0bun install --frozen-lockfile --ignore-scriptsbun run test:adapters:localbun run test:containerstest:adapters:local runs D1/Better Auth plus Supabase, Mongo, Convex and content composition. test:containers also runs the existing MinIO/PostgreSQL suites. Both are required when running TOOLS_TEST_CONTAINERS=1 bun run verify.
Logs live in the owning package or root .verification/logs/. Unique Compose projects and ephemeral loopback ports isolate each run; finally blocks remove fixtures, containers and data. External settings above describe application configuration, not environment variables that make the local runner contact cloud accounts. External tests require dedicated non-production resources and authorization; record evidence, tested versions and remaining gaps.
References: Miniflare D1, PostgREST, Convex self-hosting, Better Auth SQLite.