diff --git a/test/browser-apps/README.md b/test/browser-apps/README.md
index 2c758d71..9e9e6a46 100644
--- a/test/browser-apps/README.md
+++ b/test/browser-apps/README.md
@@ -18,6 +18,8 @@ npm run test:browser-apps
 
 `test/browser-apps/interop.test.ts` is the only cross-application scenario. It configures the real WebApp and WebPeer interfaces, transfers a file from WebApp to WebPeer, then starts the built CLI as the final peer and verifies the file through the production CLI. The CLI is a test fixture in this scenario; the PoC test and its support code are not owned by the CLI package.
 
+The interoperability scenario uses legacy path identity on all three peers. WebApp and WebPeer remain outside the NFC support matrix, so the CLI fixture explicitly selects legacy identity instead of inheriting the NFC default for new CLI settings. The scenario still verifies the transferred file through the production CLI.
+
 Run the isolated relay and TURN scenario in Compose with:
 
 ```bash
diff --git a/test/browser-apps/interop.test.ts b/test/browser-apps/interop.test.ts
index e7397016..2c93d922 100644
--- a/test/browser-apps/interop.test.ts
+++ b/test/browser-apps/interop.test.ts
@@ -243,6 +243,8 @@ async function configureCliSettings(
     encrypt: false,
     isConfigured: true,
     passphrase: "",
+    // WebApp and WebPeer retain legacy identity; new CLI settings default to NFC.
+    pathNormalizationVersion: 0,
     remoteType: "ONLY_P2P",
     usePathObfuscation: false,
   });