Normalise score/_score in SearchMatch for Spice v1/v2 compatibility

- Both score and _score are required (non-optional) on SearchMatch
- If only score is present (v1), _score is filled from it
- If only _score is present (v2), score is filled from it
- score is marked @deprecated in favour of _score

Author: ewgenius

src/client-common.ts

@@ -1386,6 +1386,15 @@ export class SpiceClient {
     }
 
     const result = await response.json();
+    if (result.results) {
+      for (const match of result.results) {
+        if (match._score === undefined && match.score !== undefined) {
+          match._score = match.score;
+        } else if (match.score === undefined && match._score !== undefined) {
+          match.score = match._score;
+        }
+      }
+    }
     return result as SearchResponse;
   }
 

src/interfaces.ts

@@ -133,13 +133,20 @@ export interface SearchMatch {
    */
   dataset: string;
   /**
-   * The similarity of the match to the query (Spice v1)
+   * The similarity of the match to the query.
+   *
+   * @deprecated Use `_score` instead. This field is from Spice v1 and is kept for
+   * backward compatibility. When the server returns only `_score` (v2), this field
+   * is automatically filled from `_score`.
    */
-  score?: number;
+  score: number;
   /**
-   * The similarity of the match to the query (Spice v2)
+   * The similarity of the match to the query.
+   *
+   * This is the canonical score field used by Spice v2. When the server returns
+   * only `score` (v1), this field is automatically filled from `score`.
    */
-  _score?: number;
+  _score: number;
   /**
    * The matches for this result
    */