@atlanai/sdk 0.2.1 → 0.2.2

package/dist/raw/eval/models/EvalPageDatasetRecordArtifactView.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/EvalPageDatasetRecordArtifactView.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/EvalPageExperimentArtifactView.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/EvalPageExperimentArtifactView.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/EvalPageExperimentResultArtifactView.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/EvalPageExperimentResultArtifactView.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/EvalPageScorerArtifactView.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/EvalPageScorerArtifactView.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/EvalPatchDataset412Response.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/EvalPatchDataset412Response.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/EvalRecordSource.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/EvalRecordSource.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/EvalScorerArtifactView.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
  *
@@ -19,6 +19,12 @@ import type { RegistryRelationshipsView } from './RegistryRelationshipsView';
  * @interface EvalScorerArtifactView
  */
 export interface EvalScorerArtifactView {
+    /**
+     * Value of the `app` field.
+     * @type {string}
+     * @memberof EvalScorerArtifactView
+     */
+    app?: string;
     /**
      * Value of the `artifact_status` field.
      * @type {string}
@@ -61,12 +67,6 @@ export interface EvalScorerArtifactView {
      * @memberof EvalScorerArtifactView
      */
     displayName?: string;
-    /**
-     * Value of the `extension` field.
-     * @type {string}
-     * @memberof EvalScorerArtifactView
-     */
-    extension?: string;
     /**
      * Kind-prefixed Crockford-base32 handle (`<kind>_<base32>`).
      * @type {string}
@@ -105,19 +105,28 @@ export interface EvalScorerArtifactView {
      * The Control-Plane OIDC client id this artifact authenticates as
      * (`x-gateway-identity` kinds); absent for every other kind.
      *
-     * **Derived, not stored.** The registry resolves it from the artifact's
-     * `service_principals` row rather than keeping a second copy on the artifact,
-     * so it appears on the create response and on the single-artifact read — the
-     * two paths that make that lookup — and **not** on list, search, or a `PATCH`
-     * response, none of which do a per-row identity read. It is the public half of
-     * the credential pair and is not secret.
+     * **Derived, not stored, and present on the create response only.** The
+     * registry would resolve it from the artifact's `service_principals` row
+     * rather than keep a second copy on the artifact — but only the create path
+     * does that lookup, because it has just provisioned the identity. Every read
+     * shape (single read, list, search, `PATCH`) is built by one constructor that
+     * sets this `None`, so it is absent from all four.
+     *
+     * This block used to name the single-artifact read as a second populated path.
+     * It was never one. Adding it means deciding whether list and search pay a
+     * per-row identity read too; the lookup a future implementation would call is
+     * `registry_server::identity::artifact_principal`. It is the public half of the
+     * credential pair and is not secret.
      * @type {string}
      * @memberof EvalScorerArtifactView
      */
     oidcClientId?: string;
     /**
      * Canonical owner: the `users.user_id` this artifact belongs to, FK-backed.
-     * Absent when unset (legacy rows / system-plane creates).
+     *
+     * Defaulted to the creating principal, so this is normally set. Absent for a row created
+     * before that default landed, for a system-plane write, and for a principal with no directory
+     * row — a service account or a seed has nothing to own anything with.
      * @type {string}
      * @memberof EvalScorerArtifactView
      */
@@ -225,13 +234,16 @@ export interface EvalScorerArtifactView {
      */
     updatedBy: string;
     /**
-     * Optional human version selector (semver); absent when unset.
+     * The free-form label the write set, verbatim. Absent when none was sent, and *not* the name
+     * the version shipped under — that is the release's own `version_label`.
      * @type {string}
      * @memberof EvalScorerArtifactView
      */
     versionLabel?: string;
     /**
-     * Monotonic version coordinate within the artifact line.
+     * This version's position in its line — the write index, 1-based and dense over versions
+     * *written*. Distinct from a release's `version_ordinal`, which counts versions **shipped**;
+     * the two agree under the default `auto` release policy and diverge under `manual`.
      * @type {number}
      * @memberof EvalScorerArtifactView
      */

package/dist/raw/eval/models/EvalScorerArtifactView.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
  *
@@ -62,6 +62,7 @@ function EvalScorerArtifactViewFromJSONTyped(json, ignoreDiscriminator) {
         return json;
     }
     return {
+        'app': json['app'] == null ? undefined : json['app'],
         'artifactStatus': json['artifact_status'],
         'commitTs': json['commit_ts'],
         'contentHashHex': json['content_hash_hex'] == null ? undefined : json['content_hash_hex'],
@@ -69,7 +70,6 @@ function EvalScorerArtifactViewFromJSONTyped(json, ignoreDiscriminator) {
         'createdBy': json['created_by'],
         'description': json['description'] == null ? undefined : json['description'],
         'displayName': json['display_name'] == null ? undefined : json['display_name'],
-        'extension': json['extension'] == null ? undefined : json['extension'],
         'id': json['id'],
         'identity': json['identity'] == null ? undefined : (0, GatewayArtifactIdentityRevealView_1.GatewayArtifactIdentityRevealViewFromJSON)(json['identity']),
         'isLatest': json['is_latest'],
@@ -111,6 +111,7 @@ function EvalScorerArtifactViewToJSONTyped(value, ignoreDiscriminator = false) {
         return value;
     }
     return {
+        'app': value['app'],
         'artifact_status': value['artifactStatus'],
         'commit_ts': value['commitTs'],
         'content_hash_hex': value['contentHashHex'],
@@ -118,7 +119,6 @@ function EvalScorerArtifactViewToJSONTyped(value, ignoreDiscriminator = false) {
         'created_by': value['createdBy'],
         'description': value['description'],
         'display_name': value['displayName'],
-        'extension': value['extension'],
         'id': value['id'],
         'identity': (0, GatewayArtifactIdentityRevealView_1.GatewayArtifactIdentityRevealViewToJSON)(value['identity']),
         'is_latest': value['isLatest'],

package/dist/raw/eval/models/EvalScorerCreate.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/EvalScorerCreate.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/EvalScorerKind.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/EvalScorerKind.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/EvalScorerMeta.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/EvalScorerMeta.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/EvalScorerPatch.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/EvalScorerPatch.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/EvalScorerScope.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/EvalScorerScope.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/EvalSubjectKind.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/EvalSubjectKind.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/GatewayArtifactBase.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
  *
@@ -16,6 +16,12 @@ import type { GatewayArtifactIdentityRevealView } from './GatewayArtifactIdentit
  * @interface GatewayArtifactBase
  */
 export interface GatewayArtifactBase {
+    /**
+     * Value of the `app` field.
+     * @type {string}
+     * @memberof GatewayArtifactBase
+     */
+    app?: string;
     /**
      * Value of the `artifact_status` field.
      * @type {string}
@@ -58,12 +64,6 @@ export interface GatewayArtifactBase {
      * @memberof GatewayArtifactBase
      */
     displayName?: string;
-    /**
-     * Value of the `extension` field.
-     * @type {string}
-     * @memberof GatewayArtifactBase
-     */
-    extension?: string;
     /**
      * Kind-prefixed Crockford-base32 handle (`<kind>_<base32>`).
      * @type {string}
@@ -102,19 +102,28 @@ export interface GatewayArtifactBase {
      * The Control-Plane OIDC client id this artifact authenticates as
      * (`x-gateway-identity` kinds); absent for every other kind.
      *
-     * **Derived, not stored.** The registry resolves it from the artifact's
-     * `service_principals` row rather than keeping a second copy on the artifact,
-     * so it appears on the create response and on the single-artifact read — the
-     * two paths that make that lookup — and **not** on list, search, or a `PATCH`
-     * response, none of which do a per-row identity read. It is the public half of
-     * the credential pair and is not secret.
+     * **Derived, not stored, and present on the create response only.** The
+     * registry would resolve it from the artifact's `service_principals` row
+     * rather than keep a second copy on the artifact — but only the create path
+     * does that lookup, because it has just provisioned the identity. Every read
+     * shape (single read, list, search, `PATCH`) is built by one constructor that
+     * sets this `None`, so it is absent from all four.
+     *
+     * This block used to name the single-artifact read as a second populated path.
+     * It was never one. Adding it means deciding whether list and search pay a
+     * per-row identity read too; the lookup a future implementation would call is
+     * `registry_server::identity::artifact_principal`. It is the public half of the
+     * credential pair and is not secret.
      * @type {string}
      * @memberof GatewayArtifactBase
      */
     oidcClientId?: string | null;
     /**
      * Canonical owner: the `users.user_id` this artifact belongs to, FK-backed.
-     * Absent when unset (legacy rows / system-plane creates).
+     *
+     * Defaulted to the creating principal, so this is normally set. Absent for a row created
+     * before that default landed, for a system-plane write, and for a principal with no directory
+     * row — a service account or a seed has nothing to own anything with.
      * @type {string}
      * @memberof GatewayArtifactBase
      */
@@ -222,13 +231,16 @@ export interface GatewayArtifactBase {
      */
     updatedBy: string;
     /**
-     * Optional human version selector (semver); absent when unset.
+     * The free-form label the write set, verbatim. Absent when none was sent, and *not* the name
+     * the version shipped under — that is the release's own `version_label`.
      * @type {string}
      * @memberof GatewayArtifactBase
      */
     versionLabel?: string | null;
     /**
-     * Monotonic version coordinate within the artifact line.
+     * This version's position in its line — the write index, 1-based and dense over versions
+     * *written*. Distinct from a release's `version_ordinal`, which counts versions **shipped**;
+     * the two agree under the default `auto` release policy and diverge under `manual`.
      * @type {number}
      * @memberof GatewayArtifactBase
      */

package/dist/raw/eval/models/GatewayArtifactBase.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
  *
@@ -59,6 +59,7 @@ function GatewayArtifactBaseFromJSONTyped(json, ignoreDiscriminator) {
         return json;
     }
     return {
+        'app': json['app'] == null ? undefined : json['app'],
         'artifactStatus': json['artifact_status'],
         'commitTs': json['commit_ts'],
         'contentHashHex': json['content_hash_hex'] === undefined ? undefined : json['content_hash_hex'] === null ? null : json['content_hash_hex'],
@@ -66,7 +67,6 @@ function GatewayArtifactBaseFromJSONTyped(json, ignoreDiscriminator) {
         'createdBy': json['created_by'],
         'description': json['description'] === undefined ? undefined : json['description'] === null ? null : json['description'],
         'displayName': json['display_name'] == null ? undefined : json['display_name'],
-        'extension': json['extension'] == null ? undefined : json['extension'],
         'id': json['id'],
         'identity': json['identity'] === undefined ? undefined : json['identity'] === null ? null : (0, GatewayArtifactIdentityRevealView_1.GatewayArtifactIdentityRevealViewFromJSON)(json['identity']),
         'isLatest': json['is_latest'],
@@ -102,6 +102,7 @@ function GatewayArtifactBaseToJSONTyped(value, ignoreDiscriminator = false) {
         return value;
     }
     return {
+        'app': value['app'],
         'artifact_status': value['artifactStatus'],
         'commit_ts': value['commitTs'],
         'content_hash_hex': value['contentHashHex'],
@@ -109,7 +110,6 @@ function GatewayArtifactBaseToJSONTyped(value, ignoreDiscriminator = false) {
         'created_by': value['createdBy'],
         'description': value['description'],
         'display_name': value['displayName'],
-        'extension': value['extension'],
         'id': value['id'],
         'identity': (0, GatewayArtifactIdentityRevealView_1.GatewayArtifactIdentityRevealViewToJSON)(value['identity']),
         'is_latest': value['isLatest'],

package/dist/raw/eval/models/GatewayArtifactIdentityRevealView.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/GatewayArtifactIdentityRevealView.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/GatewayPageMeta.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/GatewayPageMeta.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/GatewaySourceEnvelope.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/GatewaySourceEnvelope.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
  *