Reporter-offered workaround (no success result shown): declare the self-bound Durable Object via miniflare options

Finding: In the reporter's account, a cloudflare.config.ts Worker whose Durable Object binding names the Worker itself fails under @cloudflare/vitest-plugin with experimental newConfig, and the reporter offers a miniflare.durableObjects override as a workaround, but the issue shows no success result for it. Source: https://github.com/cloudflare/workers-sdk/issues/16012 (open in the supplied material; maintainer status unknown). Not verified by KFA. Reporter claim: The reporter attributes the failure to convertToWranglerConfig() emitting script_name for a self-reference. This root cause is the reporter's analysis, not maintainer-confirmed. The reporter also describes a second symptom, a cf dev container error for a container attached to a self-bound Durable Object. Bot reproduction (separate claim): An automated triage comment on the same issue (https://github.com/cloudflare/workers-sdk/issues/16012) is LLM-generated. It reports reproducing symptom 1 only. Its archive link is stated to require Cloudflare Access, so the archive was not inspected. The supplied comments report no workaround test and no reproduction of the cf dev container symptom. Workaround as offered by the reporter: override the binding in the plugin's miniflare option: cloudflareTest({ experimental: { newConfig: true }, miniflare: { durableObjects: { MY_DO: { className: "MyDurableObject", useSQLite: true } } } }). The issue shows this code but no test output, and does not state that it resolves the failure. In the reporter's example the class is declared with storage: "sqlite" and the override sets useSQLite: true; no wider rule is stated. Status: This is a reporter-offered workaround only. It is not a confirmed fix or a released fix, and KFA has not tested it. No third-party report of testing it appears in the supplied comments, which may omit middle comments. Whether it applies to the cf dev container symptom is unknown. The report says its reproduction is in a linked PR with an integration test; that PR's content and status were not supplied, and no fix commit or release is supplied.