autotel-devtools 23.0.0 → 24.0.0

package/dist/cli.cjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
-const require_http = require('./http-Cqm_MAtc.cjs');
+const require_http = require('./http-CahjEnpE.cjs');
 const require_listen = require('./listen-l09RRHht.cjs');
-const require_grpc = require('./grpc-CSWjMRiB.cjs');
+const require_grpc = require('./grpc-CSW1Evnt.cjs');
 let node_http = require("node:http");
 let node_fs = require("node:fs");
 let node_path = require("node:path");

package/dist/cli.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
-import { a as probePortHolder, g as hostHeaderIsLoopback, l as DevtoolsServer, r as resolveSourceRoot, t as attachDevtoolsRoutes } from "./http-Dbd9TIYU.js";
+import { a as probePortHolder, g as hostHeaderIsLoopback, l as DevtoolsServer, r as resolveSourceRoot, t as attachDevtoolsRoutes } from "./http-z8UbJsqk.js";
 import { t as listenLoopbackDualStack } from "./listen-D-lLgfro.js";
-import { t as startOtlpGrpcReceiver } from "./grpc-CZEDUYCM.js";
+import { t as startOtlpGrpcReceiver } from "./grpc-D1tt8UPi.js";
 import { createServer } from "node:http";
 import { readFileSync } from "node:fs";
 import { dirname, resolve } from "node:path";

package/dist/{error-aggregator-DSwUvgFF.d.cts → error-aggregator-C0at0wzF.d.cts}

@@ -1,4 +1,4 @@
-import { n as ErrorGroup, o as TraceData, r as ErrorOccurrence } from "./types-B0tjwFqj.cjs";
+import { n as ErrorGroup, o as TraceData, r as ErrorOccurrence } from "./types-C-ORUrT2.cjs";
 //#region src/server/error-aggregator.d.ts
 /** How many errors the aggregator is holding, and what they are. */
 interface ErrorStats {

package/dist/{error-aggregator-B52JI8jL.d.ts → error-aggregator-C25_JiVI.d.ts}

@@ -1,4 +1,4 @@
-import { n as ErrorGroup, o as TraceData, r as ErrorOccurrence } from "./types-DM8y4A9Z.js";
+import { n as ErrorGroup, o as TraceData, r as ErrorOccurrence } from "./types-BhbHVeiy.js";
 //#region src/server/error-aggregator.d.ts
 /** How many errors the aggregator is holding, and what they are. */
 interface ErrorStats {

package/dist/{exporter-C4uKgo7l.d.cts → exporter-AkgWRDpc.d.cts}

@@ -1,6 +1,6 @@
 import { c as QueryError, r as SignalSchema } from "./compile-JDFHUCo5.cjs";
-import { n as SpanAttributes } from "./types-DHDvZnnn.cjs";
-import { i as LogData, n as ErrorGroup, o as TraceData, t as DevtoolsData } from "./types-B0tjwFqj.cjs";
+import { i as WebMcpInventory, n as SpanAttributes } from "./types-B86Qkqg5.cjs";
+import { i as LogData, n as ErrorGroup, o as TraceData, t as DevtoolsData } from "./types-C-ORUrT2.cjs";
 import { AgentRawEvent, OtelMetricRecord } from "autotel-agents";
 import { Server } from "node:http";
 import { ReadableSpan, SpanExporter } from "@opentelemetry/sdk-trace-base";
@@ -278,6 +278,31 @@ declare class DevtoolsStore {
   };
   /** Query fields currently present, for editor completion. */
   listQueryFields(signal: 'traces' | 'logs', limit?: number): string[];
+  /**
+   * Values of one attribute paired with another on the same entity.
+   *
+   * `searchAttributes` matches on value text, which cannot answer "what arms
+   * does this experiment have". Pairing two keys across the same span can, and
+   * that is what turns a pair of cohorts into something the viewer offers
+   * rather than something the reader has to type.
+   *
+   * Rows arrive grouped by `key`, each group's values commonest first, so a
+   * caller can build the groups in one pass and take the two commonest as a
+   * default pair.
+   *
+   * The join runs over `attribute_occurrences`, not the `attribute_values`
+   * dictionary: occurrences are deleted with their span, so retention prunes
+   * them, and they carry the entity a value was seen on, so an arm is only
+   * offered for the experiment it actually ran under. The dictionary can do
+   * neither — it counts values for the lifetime of the database and forgets
+   * which span each came from, which would offer arms belonging to a different
+   * experiment and experiments whose spans are long gone.
+   */
+  pairedAttributeValues(signal: 'traces' | 'logs', key: string, pairedKey: string, limit?: number): Array<{
+    value: unknown;
+    paired: unknown;
+    count: number;
+  }>;
   searchAttributes(signal: 'traces' | 'logs', value: string, limit?: number): Array<{
     key: string;
     value: unknown;
@@ -479,9 +504,37 @@ declare class DevtoolsServer {
     errors: ErrorGroup[];
     errors_parse?: QueryError[];
   };
+  /**
+   * Fold WebMCP lifecycle history through the window end into the tool surface
+   * an agent is offered, while counting executions only inside the window.
+   *
+   * Drains every page rather than folding the first one: an inventory built
+   * from a page of results does not fail, it *under-reports* — "2 tools dropped
+   * annotations" when the answer is 6 — and gets more wrong the more traffic
+   * there is, which is backwards for an observability answer.
+   *
+   * The span-name filter is composed here rather than accepted from the client:
+   * this endpoint answers one question, and a caller-supplied predicate could
+   * only narrow it into a wrong answer.
+   */
+  queryWebMcp(args: {
+    window?: {
+      start: number;
+      end: number;
+    };
+    limit?: number;
+  }): {
+    webmcp: WebMcpInventory;
+    errors_parse?: QueryError[];
+  };
   /** Run a log query against the durable store. */
   queryLogs(args: QueryLogsArgs): QueryLogsResult;
   listQueryFields(signal: 'traces' | 'logs'): string[];
+  pairedAttributeValues(signal: 'traces' | 'logs', key: string, pairedKey: string, limit?: number): {
+    value: unknown;
+    paired: unknown;
+    count: number;
+  }[];
   searchAttributes(signal: 'traces' | 'logs', value: string, limit?: number): {
     key: string;
     value: unknown;

package/dist/{exporter-BrEcnzoT.d.ts → exporter-yo7lLDIs.d.ts}

@@ -1,6 +1,6 @@
 import { c as QueryError, r as SignalSchema } from "./compile-JDFHUCo5.js";
-import { n as SpanAttributes } from "./types-DHDvZnnn.js";
-import { i as LogData, n as ErrorGroup, o as TraceData, t as DevtoolsData } from "./types-DM8y4A9Z.js";
+import { i as WebMcpInventory, n as SpanAttributes } from "./types-B86Qkqg5.js";
+import { i as LogData, n as ErrorGroup, o as TraceData, t as DevtoolsData } from "./types-BhbHVeiy.js";
 import { Server } from "node:http";
 import { AgentRawEvent, OtelMetricRecord } from "autotel-agents";
 import { ExportResult } from "@opentelemetry/core";
@@ -278,6 +278,31 @@ declare class DevtoolsStore {
   };
   /** Query fields currently present, for editor completion. */
   listQueryFields(signal: 'traces' | 'logs', limit?: number): string[];
+  /**
+   * Values of one attribute paired with another on the same entity.
+   *
+   * `searchAttributes` matches on value text, which cannot answer "what arms
+   * does this experiment have". Pairing two keys across the same span can, and
+   * that is what turns a pair of cohorts into something the viewer offers
+   * rather than something the reader has to type.
+   *
+   * Rows arrive grouped by `key`, each group's values commonest first, so a
+   * caller can build the groups in one pass and take the two commonest as a
+   * default pair.
+   *
+   * The join runs over `attribute_occurrences`, not the `attribute_values`
+   * dictionary: occurrences are deleted with their span, so retention prunes
+   * them, and they carry the entity a value was seen on, so an arm is only
+   * offered for the experiment it actually ran under. The dictionary can do
+   * neither — it counts values for the lifetime of the database and forgets
+   * which span each came from, which would offer arms belonging to a different
+   * experiment and experiments whose spans are long gone.
+   */
+  pairedAttributeValues(signal: 'traces' | 'logs', key: string, pairedKey: string, limit?: number): Array<{
+    value: unknown;
+    paired: unknown;
+    count: number;
+  }>;
   searchAttributes(signal: 'traces' | 'logs', value: string, limit?: number): Array<{
     key: string;
     value: unknown;
@@ -479,9 +504,37 @@ declare class DevtoolsServer {
     errors: ErrorGroup[];
     errors_parse?: QueryError[];
   };
+  /**
+   * Fold WebMCP lifecycle history through the window end into the tool surface
+   * an agent is offered, while counting executions only inside the window.
+   *
+   * Drains every page rather than folding the first one: an inventory built
+   * from a page of results does not fail, it *under-reports* — "2 tools dropped
+   * annotations" when the answer is 6 — and gets more wrong the more traffic
+   * there is, which is backwards for an observability answer.
+   *
+   * The span-name filter is composed here rather than accepted from the client:
+   * this endpoint answers one question, and a caller-supplied predicate could
+   * only narrow it into a wrong answer.
+   */
+  queryWebMcp(args: {
+    window?: {
+      start: number;
+      end: number;
+    };
+    limit?: number;
+  }): {
+    webmcp: WebMcpInventory;
+    errors_parse?: QueryError[];
+  };
   /** Run a log query against the durable store. */
   queryLogs(args: QueryLogsArgs): QueryLogsResult;
   listQueryFields(signal: 'traces' | 'logs'): string[];
+  pairedAttributeValues(signal: 'traces' | 'logs', key: string, pairedKey: string, limit?: number): {
+    value: unknown;
+    paired: unknown;
+    count: number;
+  }[];
   searchAttributes(signal: 'traces' | 'logs', value: string, limit?: number): {
     key: string;
     value: unknown;