@atlanai/sdk 0.2.1 → 0.2.3

package/dist/raw/eval/models/GatewayTraceStatsOrderDirection.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsPanelQuery.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsPanelQuery.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsRequest.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsRequest.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsRequestType.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsRequestType.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsScalarResult.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsScalarResult.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsSeries.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsSeries.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsSeriesPoint.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsSeriesPoint.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsTableColumn.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsTableColumn.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsTableColumnType.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsTableColumnType.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsTableRow.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsTableRow.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsWindow.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/GatewayTraceStatsWindow.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/ProblemDetails.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/ProblemDetails.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/RegistryEdgeTarget.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/RegistryEdgeTarget.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/RegistryRelationshipEdge.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/RegistryRelationshipEdge.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/RegistryRelationshipsView.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/RegistryRelationshipsView.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/SpanListEnvelope.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/SpanListEnvelope.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/SpanViewDto.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *
@@ -109,6 +109,31 @@ export interface SpanViewDto {
      * @memberof SpanViewDto
      */
     provider?: string | null;
+    /**
+     * Promoted Eval score dimensions. Present together on `score` spans and
+     * omitted from every other span type.
+     * @type {string}
+     * @memberof SpanViewDto
+     */
+    scoreName?: string | null;
+    /**
+     * Value of the `score_value` field.
+     * @type {number}
+     * @memberof SpanViewDto
+     */
+    scoreValue?: number | null;
+    /**
+     * Stable identifier of the related scorer resource.
+     * @type {string}
+     * @memberof SpanViewDto
+     */
+    scorerId?: string | null;
+    /**
+     * Value of the `scorer_version` field.
+     * @type {number}
+     * @memberof SpanViewDto
+     */
+    scorerVersion?: number | null;
     /**
      * Value of the `service_name` field.
      * @type {string}

package/dist/raw/eval/models/SpanViewDto.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *
@@ -64,6 +64,10 @@ function SpanViewDtoFromJSONTyped(json, ignoreDiscriminator) {
         'output': json['output'] === undefined ? undefined : json['output'] === null ? null : json['output'],
         'parentSpanId': json['parent_span_id'] === undefined ? undefined : json['parent_span_id'] === null ? null : json['parent_span_id'],
         'provider': json['provider'] === undefined ? undefined : json['provider'] === null ? null : json['provider'],
+        'scoreName': json['score_name'] === undefined ? undefined : json['score_name'] === null ? null : json['score_name'],
+        'scoreValue': json['score_value'] === undefined ? undefined : json['score_value'] === null ? null : json['score_value'],
+        'scorerId': json['scorer_id'] === undefined ? undefined : json['scorer_id'] === null ? null : json['scorer_id'],
+        'scorerVersion': json['scorer_version'] === undefined ? undefined : json['scorer_version'] === null ? null : json['scorer_version'],
         'serviceName': json['service_name'] === undefined ? undefined : json['service_name'] === null ? null : json['service_name'],
         'skillName': json['skill_name'] === undefined ? undefined : json['skill_name'] === null ? null : json['skill_name'],
         'skillVersion': json['skill_version'] === undefined ? undefined : json['skill_version'] === null ? null : json['skill_version'],
@@ -101,6 +105,10 @@ function SpanViewDtoToJSONTyped(value, ignoreDiscriminator = false) {
         'output': value['output'],
         'parent_span_id': value['parentSpanId'],
         'provider': value['provider'],
+        'score_name': value['scoreName'],
+        'score_value': value['scoreValue'],
+        'scorer_id': value['scorerId'],
+        'scorer_version': value['scorerVersion'],
         'service_name': value['serviceName'],
         'skill_name': value['skillName'],
         'skill_version': value['skillVersion'],

package/dist/raw/eval/models/TraceDetailView.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *
@@ -142,6 +142,15 @@ export interface TraceDetailView {
      * @memberof TraceDetailView
      */
     workspaceId?: string;
+    /**
+     * The content plane's verdict: `none` | `present` | `deleted` (tombstoned —
+     * "content removed", a different fact from "no content") | `error` (the
+     * plane could not answer; the structural detail is still complete).
+     * Absent from deployments that predate the plane — additive.
+     * @type {string}
+     * @memberof TraceDetailView
+     */
+    contentState?: string | null;
     /**
      *
      * @type {any}

package/dist/raw/eval/models/TraceDetailView.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *
@@ -67,6 +67,7 @@ function TraceDetailViewFromJSONTyped(json, ignoreDiscriminator) {
         'traceStatus': (0, TraceStatus_1.TraceStatusFromJSON)(json['trace_status']),
         'userId': json['user_id'] == null ? undefined : json['user_id'],
         'workspaceId': json['workspace_id'] == null ? undefined : json['workspace_id'],
+        'contentState': json['content_state'] === undefined ? undefined : json['content_state'] === null ? null : json['content_state'],
         'input': json['input'] === undefined ? undefined : json['input'] === null ? null : json['input'],
         'links': (0, TraceLinks_1.TraceLinksFromJSON)(json['links']),
         'output': json['output'] === undefined ? undefined : json['output'] === null ? null : json['output'],
@@ -100,6 +101,7 @@ function TraceDetailViewToJSONTyped(value, ignoreDiscriminator = false) {
         'trace_status': (0, TraceStatus_1.TraceStatusToJSON)(value['traceStatus']),
         'user_id': value['userId'],
         'workspace_id': value['workspaceId'],
+        'content_state': value['contentState'],
         'input': value['input'],
         'links': (0, TraceLinks_1.TraceLinksToJSON)(value['links']),
         'output': value['output'],

package/dist/raw/eval/models/TraceLinks.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceLinks.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceListEnvelope.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceListEnvelope.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceParentView.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceParentView.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceStatus.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceStatus.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *

package/dist/raw/eval/models/TraceSummaryStats.d.ts

@@ -1,6 +1,6 @@
 /**
  * Evaluation catalog
- * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. A verdict is a score span in the run\'s trace; `POST /experiments/{id}/summarize` rolls a run\'s score spans into its durable `summary`. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
+ * The evaluation loop as registry artifacts: curated `dataset`s of examples pinned from production sessions and traces, `experiment` run snapshots with create-only per-case `experiment_result`s, and versioned `scorer` definitions. Finalizing an experiment derives its durable score `summary` from the uploaded result rows. The gateway executes and scores nothing — external harnesses, CI, and judges run the evals, emit score spans, and upload results here.
  *
  * The version of the OpenAPI document: 0.1.0
  *