diff --git a/src/plugins/runtime-registry-boundary.test.ts b/src/plugins/runtime-registry-boundary.test.ts
index 1553401a831..e13a53b9746 100644
--- a/src/plugins/runtime-registry-boundary.test.ts
+++ b/src/plugins/runtime-registry-boundary.test.ts
@@ -6,6 +6,7 @@ import { describe, expect, it } from "vitest";
 const repoRoot = resolve(dirname(fileURLToPath(import.meta.url)), "../..");
 const allowedRuntimeResolverRefs = new Set([
   "src/commands/doctor.e2e-harness.ts",
+  "src/infra/outbound/channel-bootstrap.runtime.ts",
   "src/plugins/capability-provider-runtime.ts",
   "src/plugins/loader.ts",
 ]);
diff --git a/src/plugins/setup-registry.test.ts b/src/plugins/setup-registry.test.ts
index c052f0b1f76..28a48e16fd7 100644
--- a/src/plugins/setup-registry.test.ts
+++ b/src/plugins/setup-registry.test.ts
@@ -8,10 +8,10 @@ import {
   resetRegistryJitiMocks,
 } from "./test-helpers/registry-jiti-mocks.js";
 
-// plugin-module-loader-cache prefers native require() for compiled .js before falling
-// back to jiti. These tests scripts plugin-loading behaviour through the
-// source-transform mock — disable the native-require fast path so the mocked source transformer
-// stays authoritative for the test fixture files on disk.
+// plugin-module-loader-cache prefers native require() for compiled .js before
+// falling back to jiti. These tests script plugin-loading behavior through the
+// source-transform mock, so force the fallback path and keep the fixture
+// transformer authoritative.
 vi.mock("./native-module-require.js", () => ({
   isJavaScriptModulePath: (_modulePath: string) => false,
   tryNativeRequireJavaScriptModule: (_modulePath: string) => ({ ok: false }),
@@ -210,7 +210,7 @@ describe("setup-registry module loader", () => {
     );
     expect(mocks.createJiti.mock.calls[0]?.[1]).toEqual(
       expect.objectContaining({
-        tryNative: false,
+        tryNative: true,
       }),
     );
   });