chore: add changeset for remote Hyperdrive bindings in local dev

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: mack-erel

.changeset/hyperdrive-remote-bindings-local-dev.md

@@ -0,0 +1,23 @@
+---
+"miniflare": minor
+"wrangler": minor
+---
+
+Support remote Hyperdrive bindings in local development
+
+Hyperdrive bindings were local-only in `wrangler dev`, so exercising the database behind a deployed Hyperdrive configuration meant running `wrangler dev --remote` or standing up a local copy of the database. Setting `remote: true` on a `hyperdrive` binding now connects local dev to the deployed configuration instead:
+
+```jsonc
+{
+	"hyperdrive": [
+		{
+			"binding": "HYPERDRIVE",
+			"id": "<your-hyperdrive-id>",
+			// connect to the deployed Hyperdrive configuration in `wrangler dev`
+			"remote": true,
+		},
+	],
+}
+```
+
+Miniflare stands up a local TCP bridge and points the binding's designator at it, relaying each connection to the edge Hyperdrive binding over the existing remote bindings proxy, so database clients such as `mysql2` and `pg` work unchanged. The edge session's connection string is fetched once per session so the local binding presents credentials the edge proxy accepts, which also makes `localConnectionString` optional whenever that session can be established. When it cannot — you are logged out, offline, or running with remote bindings turned off — the binding falls back to its `localConnectionString` with a warning, or explains what to fix if there is none. This is opt-in — bindings without `remote: true` keep the existing local-only behaviour and need no configuration changes.