deepline 0.1.102 → 0.1.103

package/dist/index.d.mts

@@ -978,7 +978,7 @@ interface ClearPlayHistoryResult {
  * Response from starting a play run.
  *
  * Internal/advanced payload returned by low-level play submission primitives.
- * Most callers should prefer `deepline play run`, {@link DeeplineClient.runPlay},
+ * Most callers should prefer `deepline plays run`, {@link DeeplineClient.runPlay},
  * or {@link PlayJob.get}.
  *
  * @example
@@ -1042,7 +1042,7 @@ interface PlayCheckToolGetterHint {
  * Request body for starting a play run via {@link DeeplineClient.startPlayRun}.
  *
  * Internal/advanced request shape for low-level submission primitives.
- * Most callers should prefer `deepline play run`, {@link DeeplineClient.runPlay},
+ * Most callers should prefer `deepline plays run`, {@link DeeplineClient.runPlay},
  * or {@link Deepline.connect}.
  *
  * Either `name` (for live plays) or `artifactStorageKey` (for packaged ad hoc runs) is required.
@@ -1505,7 +1505,7 @@ declare class DeeplineClient {
      * or {@link runPlay}.
      *
      * Supported invocation surfaces intentionally share this same run contract:
-     * `deepline play run`, repo scripts such as `bun run deepline -- play run`,
+     * `deepline plays run`, repo scripts such as `bun run deepline -- plays run`,
      * SDK context calls like `Deepline.connect().play(name).run()`, and direct
      * `POST /api/v2/plays/run` calls all return a workflow/run id. The completed
      * output is always retrievable from `getPlayStatus(runId).result` (or from
@@ -1625,7 +1625,7 @@ declare class DeeplineClient {
      *
      * Unlike {@link registerPlayArtifact}, this does not store the artifact,
      * publish a revision, or start a run. It is the authoritative cloud validation
-     * path used by `deepline play check`.
+     * path used by `deepline plays check`.
      */
     checkPlayArtifact(input: {
         name?: string;
@@ -1750,7 +1750,7 @@ declare class DeeplineClient {
      * Get the current status of a play execution.
      *
      * Internal/advanced primitive. Public callers should usually prefer
-     * {@link runPlay}, {@link PlayJob.get}, or `deepline play run --watch`.
+     * {@link runPlay}, {@link PlayJob.get}, or `deepline plays run --watch`.
      *
      * @param workflowId - Play-run id from {@link startPlayRun}
      * @returns Current status with progress logs and partial results
@@ -3261,7 +3261,7 @@ interface DeeplinePlayRuntimeContext {
  * Provides methods to check status, stream logs, wait for completion,
  * or cancel the execution.
  *
- * This handle is the SDK-context equivalent of `deepline play run --watch` and
+ * This handle is the SDK-context equivalent of `deepline plays run --watch` and
  * `POST /api/v2/plays/run`: every surface returns a run id first, then exposes
  * the completed user output through `PlayJob.get()` or the status endpoint's
  * `result` field. Runtime logs are available from `status().progress.logs` and

package/dist/index.d.ts

@@ -978,7 +978,7 @@ interface ClearPlayHistoryResult {
  * Response from starting a play run.
  *
  * Internal/advanced payload returned by low-level play submission primitives.
- * Most callers should prefer `deepline play run`, {@link DeeplineClient.runPlay},
+ * Most callers should prefer `deepline plays run`, {@link DeeplineClient.runPlay},
  * or {@link PlayJob.get}.
  *
  * @example
@@ -1042,7 +1042,7 @@ interface PlayCheckToolGetterHint {
  * Request body for starting a play run via {@link DeeplineClient.startPlayRun}.
  *
  * Internal/advanced request shape for low-level submission primitives.
- * Most callers should prefer `deepline play run`, {@link DeeplineClient.runPlay},
+ * Most callers should prefer `deepline plays run`, {@link DeeplineClient.runPlay},
  * or {@link Deepline.connect}.
  *
  * Either `name` (for live plays) or `artifactStorageKey` (for packaged ad hoc runs) is required.
@@ -1505,7 +1505,7 @@ declare class DeeplineClient {
      * or {@link runPlay}.
      *
      * Supported invocation surfaces intentionally share this same run contract:
-     * `deepline play run`, repo scripts such as `bun run deepline -- play run`,
+     * `deepline plays run`, repo scripts such as `bun run deepline -- plays run`,
      * SDK context calls like `Deepline.connect().play(name).run()`, and direct
      * `POST /api/v2/plays/run` calls all return a workflow/run id. The completed
      * output is always retrievable from `getPlayStatus(runId).result` (or from
@@ -1625,7 +1625,7 @@ declare class DeeplineClient {
      *
      * Unlike {@link registerPlayArtifact}, this does not store the artifact,
      * publish a revision, or start a run. It is the authoritative cloud validation
-     * path used by `deepline play check`.
+     * path used by `deepline plays check`.
      */
     checkPlayArtifact(input: {
         name?: string;
@@ -1750,7 +1750,7 @@ declare class DeeplineClient {
      * Get the current status of a play execution.
      *
      * Internal/advanced primitive. Public callers should usually prefer
-     * {@link runPlay}, {@link PlayJob.get}, or `deepline play run --watch`.
+     * {@link runPlay}, {@link PlayJob.get}, or `deepline plays run --watch`.
      *
      * @param workflowId - Play-run id from {@link startPlayRun}
      * @returns Current status with progress logs and partial results
@@ -3261,7 +3261,7 @@ interface DeeplinePlayRuntimeContext {
  * Provides methods to check status, stream logs, wait for completion,
  * or cancel the execution.
  *
- * This handle is the SDK-context equivalent of `deepline play run --watch` and
+ * This handle is the SDK-context equivalent of `deepline plays run --watch` and
  * `POST /api/v2/plays/run`: every surface returns a run id first, then exposes
  * the completed user output through `PlayJob.get()` or the status endpoint's
  * `result` field. Runtime logs are available from `status().progress.logs` and

package/dist/index.js

@@ -265,10 +265,11 @@ var SDK_RELEASE = {
   // failed runs, persisted/succeeded/failed row counts, strict local CSV
   // preflight (existence, data rows, quotes, duplicate headers), HTML error
   // scrubbing, and word-boundary watch truncation.
-  version: "0.1.102",
+  // 0.1.103 ships the refined SDK CLI command surface.
+  version: "0.1.103",
   apiContract: "2026-06-dataset-column-cell-stale-hard-cutover",
   supportPolicy: {
-    latest: "0.1.102",
+    latest: "0.1.103",
     minimumSupported: "0.1.53",
     deprecatedBelow: "0.1.53"
   }
@@ -1934,7 +1935,7 @@ var DeeplineClient = class {
    * or {@link runPlay}.
    *
    * Supported invocation surfaces intentionally share this same run contract:
-   * `deepline play run`, repo scripts such as `bun run deepline -- play run`,
+   * `deepline plays run`, repo scripts such as `bun run deepline -- plays run`,
    * SDK context calls like `Deepline.connect().play(name).run()`, and direct
    * `POST /api/v2/plays/run` calls all return a workflow/run id. The completed
    * output is always retrievable from `getPlayStatus(runId).result` (or from
@@ -2103,7 +2104,7 @@ var DeeplineClient = class {
    *
    * Unlike {@link registerPlayArtifact}, this does not store the artifact,
    * publish a revision, or start a run. It is the authoritative cloud validation
-   * path used by `deepline play check`.
+   * path used by `deepline plays check`.
    */
   async checkPlayArtifact(input) {
     return this.http.post("/api/v2/plays/check", input);
@@ -2296,7 +2297,7 @@ var DeeplineClient = class {
    * Get the current status of a play execution.
    *
    * Internal/advanced primitive. Public callers should usually prefer
-   * {@link runPlay}, {@link PlayJob.get}, or `deepline play run --watch`.
+   * {@link runPlay}, {@link PlayJob.get}, or `deepline plays run --watch`.
    *
    * @param workflowId - Play-run id from {@link startPlayRun}
    * @returns Current status with progress logs and partial results

package/dist/index.mjs

@@ -187,10 +187,11 @@ var SDK_RELEASE = {
   // failed runs, persisted/succeeded/failed row counts, strict local CSV
   // preflight (existence, data rows, quotes, duplicate headers), HTML error
   // scrubbing, and word-boundary watch truncation.
-  version: "0.1.102",
+  // 0.1.103 ships the refined SDK CLI command surface.
+  version: "0.1.103",
   apiContract: "2026-06-dataset-column-cell-stale-hard-cutover",
   supportPolicy: {
-    latest: "0.1.102",
+    latest: "0.1.103",
     minimumSupported: "0.1.53",
     deprecatedBelow: "0.1.53"
   }
@@ -1856,7 +1857,7 @@ var DeeplineClient = class {
    * or {@link runPlay}.
    *
    * Supported invocation surfaces intentionally share this same run contract:
-   * `deepline play run`, repo scripts such as `bun run deepline -- play run`,
+   * `deepline plays run`, repo scripts such as `bun run deepline -- plays run`,
    * SDK context calls like `Deepline.connect().play(name).run()`, and direct
    * `POST /api/v2/plays/run` calls all return a workflow/run id. The completed
    * output is always retrievable from `getPlayStatus(runId).result` (or from
@@ -2025,7 +2026,7 @@ var DeeplineClient = class {
    *
    * Unlike {@link registerPlayArtifact}, this does not store the artifact,
    * publish a revision, or start a run. It is the authoritative cloud validation
-   * path used by `deepline play check`.
+   * path used by `deepline plays check`.
    */
   async checkPlayArtifact(input) {
     return this.http.post("/api/v2/plays/check", input);
@@ -2218,7 +2219,7 @@ var DeeplineClient = class {
    * Get the current status of a play execution.
    *
    * Internal/advanced primitive. Public callers should usually prefer
-   * {@link runPlay}, {@link PlayJob.get}, or `deepline play run --watch`.
+   * {@link runPlay}, {@link PlayJob.get}, or `deepline plays run --watch`.
    *
    * @param workflowId - Play-run id from {@link startPlayRun}
    * @returns Current status with progress logs and partial results

package/dist/repo/sdk/src/client.ts

@@ -951,7 +951,7 @@ export class DeeplineClient {
    * or {@link runPlay}.
    *
    * Supported invocation surfaces intentionally share this same run contract:
-   * `deepline play run`, repo scripts such as `bun run deepline -- play run`,
+   * `deepline plays run`, repo scripts such as `bun run deepline -- plays run`,
    * SDK context calls like `Deepline.connect().play(name).run()`, and direct
    * `POST /api/v2/plays/run` calls all return a workflow/run id. The completed
    * output is always retrievable from `getPlayStatus(runId).result` (or from
@@ -1221,7 +1221,7 @@ export class DeeplineClient {
    *
    * Unlike {@link registerPlayArtifact}, this does not store the artifact,
    * publish a revision, or start a run. It is the authoritative cloud validation
-   * path used by `deepline play check`.
+   * path used by `deepline plays check`.
    */
   async checkPlayArtifact(input: {
     name?: string;
@@ -1494,7 +1494,7 @@ export class DeeplineClient {
    * Get the current status of a play execution.
    *
    * Internal/advanced primitive. Public callers should usually prefer
-   * {@link runPlay}, {@link PlayJob.get}, or `deepline play run --watch`.
+   * {@link runPlay}, {@link PlayJob.get}, or `deepline plays run --watch`.
    *
    * @param workflowId - Play-run id from {@link startPlayRun}
    * @returns Current status with progress logs and partial results

package/dist/repo/sdk/src/index.ts

@@ -35,7 +35,7 @@
  * });
  * ```
  *
- * Then run: `deepline play run --file my-play.play.ts --watch`
+ * Then run: `deepline plays run --file my-play.play.ts --watch`
  *
  * ## Architecture
  *

package/dist/repo/sdk/src/play.ts

@@ -38,7 +38,7 @@
  * });
  * ```
  *
- * Then run via CLI: `deepline play run --file my-play.play.ts --watch`
+ * Then run via CLI: `deepline plays run --file my-play.play.ts --watch`
  *
  * ### Programmatic usage
  *
@@ -807,7 +807,7 @@ export interface DeeplinePlayRuntimeContext {
  * Provides methods to check status, stream logs, wait for completion,
  * or cancel the execution.
  *
- * This handle is the SDK-context equivalent of `deepline play run --watch` and
+ * This handle is the SDK-context equivalent of `deepline plays run --watch` and
  * `POST /api/v2/plays/run`: every surface returns a run id first, then exposes
  * the completed user output through `PlayJob.get()` or the status endpoint's
  * `result` field. Runtime logs are available from `status().progress.logs` and

package/dist/repo/sdk/src/release.ts

@@ -58,10 +58,11 @@ export const SDK_RELEASE = {
   // failed runs, persisted/succeeded/failed row counts, strict local CSV
   // preflight (existence, data rows, quotes, duplicate headers), HTML error
   // scrubbing, and word-boundary watch truncation.
-  version: '0.1.102',
+  // 0.1.103 ships the refined SDK CLI command surface.
+  version: '0.1.103',
   apiContract: '2026-06-dataset-column-cell-stale-hard-cutover',
   supportPolicy: {
-    latest: '0.1.102',
+    latest: '0.1.103',
     minimumSupported: '0.1.53',
     deprecatedBelow: '0.1.53',
   },

package/dist/repo/sdk/src/types.ts

@@ -813,7 +813,7 @@ export interface ClearPlayHistoryResult {
  * Response from starting a play run.
  *
  * Internal/advanced payload returned by low-level play submission primitives.
- * Most callers should prefer `deepline play run`, {@link DeeplineClient.runPlay},
+ * Most callers should prefer `deepline plays run`, {@link DeeplineClient.runPlay},
  * or {@link PlayJob.get}.
  *
  * @example
@@ -880,7 +880,7 @@ export interface PlayCheckToolGetterHint {
  * Request body for starting a play run via {@link DeeplineClient.startPlayRun}.
  *
  * Internal/advanced request shape for low-level submission primitives.
- * Most callers should prefer `deepline play run`, {@link DeeplineClient.runPlay},
+ * Most callers should prefer `deepline plays run`, {@link DeeplineClient.runPlay},
  * or {@link Deepline.connect}.
  *
  * Either `name` (for live plays) or `artifactStorageKey` (for packaged ad hoc runs) is required.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "deepline",
-  "version": "0.1.102",
+  "version": "0.1.103",
   "description": "Deepline SDK + CLI — B2B data enrichment powered by durable cloud execution",
   "license": "MIT",
   "repository": {