@camstack/types 1.2.442 → 1.2.444

package/dist/capabilities/pipeline-step-input.d.ts

@@ -0,0 +1,33 @@
+/**
+ * The pipeline step-input shape and the run-result bridge, in a module that
+ * imports nothing but zod and types.
+ *
+ * WHY A SEPARATE FILE (addon footprint, D28): both were declared in
+ * `pipeline-executor.cap.ts`, whose import evaluates the whole executor schema
+ * graph. An addon that only needs these two (the benchmark's `runPipelineTest`
+ * action) paid ~130 MB of heap at load. `pipeline-executor.cap.ts` re-exports
+ * them, so every existing import keeps working; addon server code takes them
+ * from `@camstack/types/addon`.
+ */
+import { z } from 'zod';
+import type { FrameResult } from '../types/detection.js';
+export type PipelineStepInputOutput = {
+    readonly addonId: string;
+    readonly modelId?: string;
+    readonly enabled: boolean;
+    readonly children?: readonly PipelineStepInputOutput[];
+    readonly settings?: Readonly<Record<string, unknown>>;
+    /**
+     * Step-tree device jump (same-node, phase 1). Operator manual override
+     * carried from the per-(node,device) BASE
+     * (`inferenceDevices[node][deviceKey].steps[step].jumpDeviceKey`): run THIS
+     * enrichment step (and its inherited children) on a DIFFERENT enabled device
+     * of the SAME node — `<backend>:<device>` (e.g. `openvino:npu`). Absent ⇒ the
+     * runner AUTO-jumps only when the effective device's format cannot run the
+     * step's model, else the step inherits the effective device. Same-node only.
+     */
+    readonly jumpDeviceKey?: string;
+};
+export declare const PipelineStepInputSchema: z.ZodType<PipelineStepInputOutput>;
+/** Typed bridge to the recursive `FrameResult` graph; validation is structural. */
+export declare const PipelineRunResultBridge: z.ZodCustom<FrameResult, FrameResult>;