@anuma/sdk 6.10.0 → 6.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/expo/{chunk-4M56MKBV.mjs → chunk-ZO7S3TBT.mjs} +79 -25
- package/dist/expo/index.cjs +67 -13
- package/dist/expo/index.d.mts +42 -0
- package/dist/expo/index.d.ts +42 -0
- package/dist/expo/index.mjs +1 -1
- package/dist/expo/{recall-WIB7RQQZ.mjs → recall-OALPGL3H.mjs} +1 -1
- package/dist/react/{chunk-EJ65X4GI.mjs → chunk-HNQ2ZEFF.mjs} +79 -25
- package/dist/react/index.cjs +67 -13
- package/dist/react/index.d.mts +42 -0
- package/dist/react/index.d.ts +42 -0
- package/dist/react/index.mjs +1 -1
- package/dist/react/{recall-FWILZSFH.mjs → recall-F5DBVCU2.mjs} +1 -1
- package/dist/server/{chunk-I56324FR.mjs → chunk-BKB6AT7Z.mjs} +79 -25
- package/dist/server/index.cjs +67 -13
- package/dist/server/index.d.mts +42 -0
- package/dist/server/index.d.ts +42 -0
- package/dist/server/index.mjs +1 -1
- package/dist/server/{recall-T7CNXTQ3.mjs → recall-HVIEAH7J.mjs} +1 -1
- package/package.json +1 -1
package/dist/server/index.d.mts
CHANGED
|
@@ -5641,6 +5641,17 @@ interface RecallDiagnostics {
|
|
|
5641
5641
|
* never the cost.
|
|
5642
5642
|
*/
|
|
5643
5643
|
vaultRowsDecrypted?: number;
|
|
5644
|
+
/**
|
|
5645
|
+
* Rows the fact lane had to re-embed through the portal because their stored
|
|
5646
|
+
* vector was unusable — stale `embedding_model`, wrong dimension, or
|
|
5647
|
+
* unparseable. Absent when the fact lane didn't run.
|
|
5648
|
+
*
|
|
5649
|
+
* Expected to be 0 on a healthy vault: rows are embedded at write time and the
|
|
5650
|
+
* re-embed writes the current model back, so a persistently non-zero value
|
|
5651
|
+
* means the writeback is not sticking and every turn is paying for it. On the
|
|
5652
|
+
* LEGACY read path this batch is uncapped, so it can be the whole vault.
|
|
5653
|
+
*/
|
|
5654
|
+
vaultRowsEmbedded?: number;
|
|
5644
5655
|
/** Facts the fact lane returned (post-dedupe, pre-fusion). */
|
|
5645
5656
|
factCount: number;
|
|
5646
5657
|
/** Chunks the chunk lane returned (post-dedupe, pre-fusion). */
|
|
@@ -5653,6 +5664,37 @@ interface RecallDiagnostics {
|
|
|
5653
5664
|
prep: number;
|
|
5654
5665
|
/** Vault fact-lane search (`searchVaultMemoriesWithSize`). */
|
|
5655
5666
|
factLane: number;
|
|
5667
|
+
/**
|
|
5668
|
+
* The cross-encoder's share of {@link factLane} — wall-clock spent inside
|
|
5669
|
+
* `rerankPairs`. Billed even when the CE threw partway through, because a
|
|
5670
|
+
* rerank that burned three seconds and then failed still cost them.
|
|
5671
|
+
*
|
|
5672
|
+
* A SUBSET of `factLane`, not a sibling: read `factLane - rerank` for
|
|
5673
|
+
* everything else the lane did (query embed, vault read, fused ranking).
|
|
5674
|
+
* 0 when the CE did not run; `reranked` is what distinguishes that from a
|
|
5675
|
+
* rerank that cost nothing.
|
|
5676
|
+
*
|
|
5677
|
+
* Exists because #845 spent three rounds arguing about which stage inside
|
|
5678
|
+
* the fact lane dominated — whole-vault read, then admission window, then
|
|
5679
|
+
* the CE — with one aggregate number for all of them. Every hypothesis was
|
|
5680
|
+
* an inference; this makes the question a query.
|
|
5681
|
+
*/
|
|
5682
|
+
rerank: number;
|
|
5683
|
+
/**
|
|
5684
|
+
* The query embed's share of {@link factLane} — one portal round trip.
|
|
5685
|
+
*
|
|
5686
|
+
* Also a SUBSET of `factLane`. Together with `rerank` this makes the lane
|
|
5687
|
+
* decomposable: `factLane - queryEmbed - rerank` is the local work (vault
|
|
5688
|
+
* read, decrypt, BM25/cosine fusion), and each of the three implies a
|
|
5689
|
+
* completely different fix.
|
|
5690
|
+
*
|
|
5691
|
+
* 0 when the lane returned before embedding, which includes every empty
|
|
5692
|
+
* vault — `prepareVaultCandidates` short-circuits first. That is why the
|
|
5693
|
+
* fast `vault_size = 0` population never established a baseline for this
|
|
5694
|
+
* cost, and why the ~850ms floor on the smallest NON-empty vaults had no
|
|
5695
|
+
* attributable owner.
|
|
5696
|
+
*/
|
|
5697
|
+
queryEmbed: number;
|
|
5656
5698
|
/** Chunk-lane search (`searchChunksOp`). */
|
|
5657
5699
|
chunkLane: number;
|
|
5658
5700
|
/** Cross-lane RRF fusion + provenance dedup after both lanes. */
|
package/dist/server/index.d.ts
CHANGED
|
@@ -5641,6 +5641,17 @@ interface RecallDiagnostics {
|
|
|
5641
5641
|
* never the cost.
|
|
5642
5642
|
*/
|
|
5643
5643
|
vaultRowsDecrypted?: number;
|
|
5644
|
+
/**
|
|
5645
|
+
* Rows the fact lane had to re-embed through the portal because their stored
|
|
5646
|
+
* vector was unusable — stale `embedding_model`, wrong dimension, or
|
|
5647
|
+
* unparseable. Absent when the fact lane didn't run.
|
|
5648
|
+
*
|
|
5649
|
+
* Expected to be 0 on a healthy vault: rows are embedded at write time and the
|
|
5650
|
+
* re-embed writes the current model back, so a persistently non-zero value
|
|
5651
|
+
* means the writeback is not sticking and every turn is paying for it. On the
|
|
5652
|
+
* LEGACY read path this batch is uncapped, so it can be the whole vault.
|
|
5653
|
+
*/
|
|
5654
|
+
vaultRowsEmbedded?: number;
|
|
5644
5655
|
/** Facts the fact lane returned (post-dedupe, pre-fusion). */
|
|
5645
5656
|
factCount: number;
|
|
5646
5657
|
/** Chunks the chunk lane returned (post-dedupe, pre-fusion). */
|
|
@@ -5653,6 +5664,37 @@ interface RecallDiagnostics {
|
|
|
5653
5664
|
prep: number;
|
|
5654
5665
|
/** Vault fact-lane search (`searchVaultMemoriesWithSize`). */
|
|
5655
5666
|
factLane: number;
|
|
5667
|
+
/**
|
|
5668
|
+
* The cross-encoder's share of {@link factLane} — wall-clock spent inside
|
|
5669
|
+
* `rerankPairs`. Billed even when the CE threw partway through, because a
|
|
5670
|
+
* rerank that burned three seconds and then failed still cost them.
|
|
5671
|
+
*
|
|
5672
|
+
* A SUBSET of `factLane`, not a sibling: read `factLane - rerank` for
|
|
5673
|
+
* everything else the lane did (query embed, vault read, fused ranking).
|
|
5674
|
+
* 0 when the CE did not run; `reranked` is what distinguishes that from a
|
|
5675
|
+
* rerank that cost nothing.
|
|
5676
|
+
*
|
|
5677
|
+
* Exists because #845 spent three rounds arguing about which stage inside
|
|
5678
|
+
* the fact lane dominated — whole-vault read, then admission window, then
|
|
5679
|
+
* the CE — with one aggregate number for all of them. Every hypothesis was
|
|
5680
|
+
* an inference; this makes the question a query.
|
|
5681
|
+
*/
|
|
5682
|
+
rerank: number;
|
|
5683
|
+
/**
|
|
5684
|
+
* The query embed's share of {@link factLane} — one portal round trip.
|
|
5685
|
+
*
|
|
5686
|
+
* Also a SUBSET of `factLane`. Together with `rerank` this makes the lane
|
|
5687
|
+
* decomposable: `factLane - queryEmbed - rerank` is the local work (vault
|
|
5688
|
+
* read, decrypt, BM25/cosine fusion), and each of the three implies a
|
|
5689
|
+
* completely different fix.
|
|
5690
|
+
*
|
|
5691
|
+
* 0 when the lane returned before embedding, which includes every empty
|
|
5692
|
+
* vault — `prepareVaultCandidates` short-circuits first. That is why the
|
|
5693
|
+
* fast `vault_size = 0` population never established a baseline for this
|
|
5694
|
+
* cost, and why the ~850ms floor on the smallest NON-empty vaults had no
|
|
5695
|
+
* attributable owner.
|
|
5696
|
+
*/
|
|
5697
|
+
queryEmbed: number;
|
|
5656
5698
|
/** Chunk-lane search (`searchChunksOp`). */
|
|
5657
5699
|
chunkLane: number;
|
|
5658
5700
|
/** Cross-lane RRF fusion + provenance dedup after both lanes. */
|
package/dist/server/index.mjs
CHANGED