@aiqa/sdk 2.0.0 → 2.0.1

package/README.md

@@ -165,7 +165,7 @@ while you wait.
 
 `addFact()` does not throw on verification failure — an unmatched
 fact resolves with `is_valid_answer: false` and (where the backend
-provides it) `verification_status: "unmatched"` or `"contradicted"`.
+provides it) `verification_status: "unmatched"`.
 Reject paths are reserved for transport / protocol errors.
 
 **Parameters:**
@@ -212,8 +212,7 @@ const result = await sdk.addFact({
 });
 
 if (result.is_valid_answer) {
-  // verification_status will be "matched" (or "contradicted" if the
-  // customer explicitly contradicted the expected answer).
+  // verification_status will be "matched".
   console.log("matched:", result.ai_answer);
 } else {
   // verification_status will be "unmatched". matched_components /
@@ -366,13 +365,13 @@ processing
                           (same, but for a held unmatched verdict)
                           │
                           ▼
-                    matched | unmatched | contradicted   ← terminal
+                    matched | unmatched   ← terminal
 ```
 
 Rules for consumers:
 
 - **`addFact()` resolves only on a terminal state** (`matched`,
-  `unmatched`, `contradicted`). Render progress from the
+  `unmatched`). Render progress from the
   `FACT_VERIFIED` event, render the final verdict from the Promise
   result.
 - **Treat unknown `verification_status` strings as `processing`.**
@@ -453,8 +452,8 @@ interface AddFactResult {
   answer_match_score?: number;
 
   /**
-   * Top-level state at terminal resolution. Always one of `matched`,
-   * `unmatched`, or `contradicted` because the `addFact()` Promise only
+   * Top-level state at terminal resolution. Always one of `matched`
+   * or `unmatched` because the `addFact()` Promise only
    * resolves on terminals. Optional during the rollout window for
    * backwards compatibility with older backends.
    */
@@ -484,8 +483,7 @@ type VerificationStatus =
   | "pending_confirmation_matched"
   | "pending_confirmation_unmatched"
   | "matched"
-  | "unmatched"
-  | "contradicted";
+  | "unmatched";
 ```
 
 The enum is additive: consumers that `switch` on this value MUST

package/dist/browser/browser.d.ts

@@ -100,16 +100,15 @@ type QuestionStatus = "searching" | "asked" | "not_asked";
  *  - `pending_confirmation_matched`   backend has a matching answer but is
  *                                     holding a settling window for mid-answer
  *                                     clarifications (e.g. spellings, "I mean…");
- *                                     resolves to `matched`/`unmatched`/`contradicted`
+ *                                     resolves to `matched`/`unmatched`
  *  - `pending_confirmation_unmatched` same as above but the held verdict is
  *                                     `unmatched`; UI can show "we heard X but it
  *                                     doesn't match, waiting to confirm" instead
  *                                     of a hard red verdict
  *  - `matched`                        terminal: answer matched expected
  *  - `unmatched`                      terminal: budget exhausted with no match
- *  - `contradicted`                   terminal (future): customer contradicted expected
  */
-type VerificationStatus = "processing" | "awaiting_question" | "awaiting_answer" | "partial" | "pending_confirmation_matched" | "pending_confirmation_unmatched" | "matched" | "unmatched" | "contradicted";
+type VerificationStatus = "processing" | "awaiting_question" | "awaiting_answer" | "partial" | "pending_confirmation_matched" | "pending_confirmation_unmatched" | "matched" | "unmatched";
 type ApplicationFact = ApplicationFactInput & {
     ai_answer?: any;
     question_status: QuestionStatus;
@@ -143,8 +142,8 @@ interface AddFactResult {
     answer_match_score?: number;
     metadata?: Record<string, string>;
     /**
-     * Top-level state at terminal resolution. Always one of `matched`,
-     * `unmatched`, or `contradicted` because the `addFact()` Promise only
+     * Top-level state at terminal resolution. Always one of `matched`
+     * or `unmatched` because the `addFact()` Promise only
      * resolves on terminals. Optional during the rollout window for
      * backwards compatibility with older backends.
      */
@@ -164,7 +163,7 @@ interface AddFactResult {
  * Fires on EVERY state transition the verification queue produces —
  * non-terminal (`partial`, `awaiting_question`, `awaiting_answer`,
  * `pending_confirmation_matched`, `pending_confirmation_unmatched`,
- * `processing`) AND terminal (`matched`, `unmatched`, `contradicted`).
+ * `processing`) AND terminal (`matched`, `unmatched`).
  *
  * Subscribe with:
  *   sdk.on("FACT_VERIFIED", (payload: FactVerifiedPayload) => {...});

package/dist/browser/browser.js

@@ -3397,7 +3397,7 @@ var compareVersions = (left, right) => {
 // package.json
 var package_default = {
   name: "@aiqa/sdk",
-  version: "2.0.0-develop.2",
+  version: "2.1.0-develop.1",
   main: "dist/node/node.js",
   module: "dist/node/node.js",
   types: "dist/node/node.d.ts",
@@ -3613,7 +3613,14 @@ var AiQaSdk = class {
     const url2 = new URL(this.url);
     const socketOptions = {
       reconnectionDelayMax: 1e4,
-      path: url2.pathname
+      path: url2.pathname,
+      // WebSocket only, skipping engine.io's default HTTP long-polling phase.
+      // Some embedders sit behind proxies/security gateways that duplicate the
+      // polling GETs across a fleet; the concurrent polls violate engine.io's
+      // one-inflight-poll-per-session rule and tear the session down, so every
+      // poll then returns "Session ID unknown" (HTTP 400) and the client never
+      // authenticates. A single WebSocket has no repeated requests to duplicate.
+      transports: ["websocket"]
     };
     this.socket = lookup2(url2.origin, socketOptions);
     this.socket.on("connect", () => {