Service‑binding permission enforcement in Wrangler dev --local mode

Determine whether the Wrangler dev server applies the same service‑binding permission checks that exist in the production Cloudflare Workers runtime when the --local flag is used.

The documentation shows that wrangler dev reads bindings from wrangler.toml and offers flags to override or disable remote resources, but it does not specify whether production‑level access‑control checks for service bindings are reproduced locally. This uncertainty makes it unclear if a worker that would be rejected in production could still succeed during local testing.

• Does the dev server enforce service‑binding auth policies when --local is set?
• If the checks are omitted, what configuration or flag can be used to make the local environment mirror production permission boundaries?