From dbfa26a778e52926dc14c2b2a4c5682790d2e272 Mon Sep 17 00:00:00 2001
From: AAA <35992542+TNTcraftHIM@users.noreply.github.com>
Date: Fri, 4 Sep 2026 04:00:51 +0800
Subject: [PATCH] fix(client): accept native capability combinations in
 loopback gate

Keep the v5 loopback gate strict on protocol and identity while accepting valid native capability combinations. This fixes false Client-not-found results for capable Windows packages without changing runtime behavior.
---
 scripts/client-loopback-gate.ts | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/scripts/client-loopback-gate.ts b/scripts/client-loopback-gate.ts
index c731eb2..fd3383a 100644
--- a/scripts/client-loopback-gate.ts
+++ b/scripts/client-loopback-gate.ts
@@ -97,10 +97,10 @@ async function browserHandshake(
             const health = await response.json();
             if (health.protocol === ${NATIVE_PROTOCOL} && health.service === "screener-client" &&
                 health.port === port && typeof health.instanceToken === "string" &&
-                health.nativeMedia?.video === false &&
-                health.nativeMedia?.processAudio === false &&
-                health.nativeMedia?.systemAudio === false &&
-                health.nativeMedia?.hardwareH264 === false) {
+                typeof health.nativeMedia?.video === "boolean" &&
+                typeof health.nativeMedia?.processAudio === "boolean" &&
+                typeof health.nativeMedia?.systemAudio === "boolean" &&
+                typeof health.nativeMedia?.hardwareH264 === "boolean") {
               return { port, instanceToken: health.instanceToken };
             }
           } catch {} finally {