Use the configured Cloudflare database adapter in sandboxed plugins

[swissky]

Problem

The Cloudflare sandbox plugin bridge still uses D1 directly through env.DB and D1Dialect. On sites configured with Hyperdrive or Durable Objects SQL, sandboxed plugin database operations can fail. If a separate D1 binding exists, the bridge can use a different database from the rest of the site. This is still present on current main.

Use case

A site using Hyperdrive/PostgreSQL or Durable Objects SQL should be able to run sandboxed plugins against the same database as the rest of EmDash. Plugin content, media metadata, taxonomy, user, settings, and plugin-storage operations should work without adding an unrelated D1 database binding.

Current workarounds

There is no reliable adapter-level workaround. Adding a D1 binding may let some bridge calls run, but it does not make them use the configured database and can split plugin data from site data.

Your involvement

• I am requesting this capability.
• I am offering to champion the design in a feature plan or RFC.
• I am offering to implement it after the design is accepted.

[github-actions[bot]]

Design PR #4406 proposes proposals/sandbox-plugin-database-adapters.md for this Idea. Review of the design continues on the pull request.