@astrasyncai/verification-gateway 4.4.0 → 4.5.1

package/dist/gateway/gateway.mjs

@@ -3672,7 +3672,7 @@ function getTrustLevel(score) {
 }
 
 // src/version.ts
-var SDK_VERSION = "4.4.0";
+var SDK_VERSION = "4.5.1";
 
 // src/http.ts
 var SDK_USER_AGENT = `astrasync-sdk/${SDK_VERSION}`;
@@ -4129,12 +4129,15 @@ async function verify(config, request, options) {
   const verificationContext = apiResponse.verificationContext;
   const accessLevel = apiResponse.access?.accessLevel ?? "standard";
   const result = {
-    // Round-18 G4: backend allowed access. Identity is verified (we resolved
-    // the caller to an agent) and policy passed all gates. Read idVerified
-    // from verificationContext for symmetry with the deny branch; default true
-    // on success path since `access.allowed === true` implies identity was
-    // resolvable (anonymous-allow paths flow through createGuidanceResponse).
-    identityVerified: apiResponse.verificationContext?.idVerified !== false,
+    // 4.5.0 (probe F1): read idVerified from verificationContext with the
+    // SAME absent⇒false default as the deny branch. The previous `!== false`
+    // default manufactured `identityVerified: true` for anonymous
+    // allow_full/allow_partial/audit responses (which allow access but omit
+    // verificationContext entirely) — the "anonymous caller labelled
+    // verified" defect. Every authenticated success response has carried
+    // `verificationContext.idVerified: true` since v2.2.4, so a truth claim
+    // this load-bearing must never be defaulted on.
+    identityVerified: apiResponse.verificationContext?.idVerified === true,
     policyAllowed: true,
     accessLevel,
     agent,