Move Extensions domain access behind the API

[admdly]

Summary

• remove the site-owned Extensions D1 binding, migrations, and direct SQL adapters
• route account, developer, submission, claim, transfer, moderation, and catalogue access through the generated API client
• synchronize OIDC identity with the API before issuing the local session
• regenerate the v2 client from the API PR contract, including documented active-account errors and the owner-list query without developer_id

This PR is intended to merge with FOSSBilling/api#186, which owns the consolidated Extensions schema and endpoints.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	extensions	ae9a9d3	Commit Preview URL Branch Preview URL	Aug 05 2026, 03:56 PM

[cubic-dev-ai]

All reported issues were addressed across 33 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 16 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 6 files (changes from recent commits).

<sub>Requires human review: This PR re-architects data access from direct D1 to an external API, changes identity sync and authorization, and removes database migrations—a human should review the operational and data-handling tradeoffs.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 4 files (changes from recent commits).

<sub>Requires human review: Replaces local D1 database with API call, altering operational tradeoffs (latency, availability), changes auth/authorization verification, and removes the database layer entirely — a hard-to-reverse architectural decision needing human review.

Re-trigger cubic</sub>