/**
 * SDK-MEASURED metric pinning (mmnto-ai/totem#2738 falsification round, F7).
 *
 * The rest of the relevance suite pins the MAP; it cannot tell you whether the
 * map matches what LanceDB actually returns. The `dot` entry in particular was
 * derived from the SDK's DOC COMMENT ("if the vectors are normalized … dot
 * distance is equivalent to the cosine distance") and never measured — a doc
 * comment is a claim, not a measurement, and it is silent about what happens
 * off the unit sphere. This file is the falsifier that gap wanted: it builds a
 * throwaway LanceDB table with hand-chosen vectors, queries it under each of
 * the SDK's three metrics, and asserts the RETURNED `_distance` before feeding
 * each measured value through the map.
 *
 * If a future SDK bump changes a distance convention — l2 stops being squared,
 * dot flips sign, the default stops being l2 — this file goes red at the exact
 * number that moved, instead of every relevance in the system quietly
 * re-scaling behind a green suite.
 */
export {};
//# sourceMappingURL=relevance.sdk.test.d.ts.map