@particle-academy/fancy-flow 0.65.2 → 0.66.1

package/dist/runtime.js

@@ -1,7 +1,7 @@
-export { applyOutputsToNodes, applyStatusesToNodes, createHistory, useFlowHistory, useFlowRun, useFlowState } from './chunk-MBVX4ZRB.js';
-export { runCohort } from './chunk-RIAFHQT5.js';
-export { RunIdentity, escapeSegment, runFlow } from './chunk-JF6WCRBU.js';
-import './chunk-F5RPRB7A.js';
-import './chunk-USL4FMFU.js';
+export { applyOutputsToNodes, applyStatusesToNodes, createHistory, useFlowHistory, useFlowRun, useFlowState } from './chunk-2QTEELJE.js';
+export { runCohort } from './chunk-RE3XNVSB.js';
+import './chunk-OWENS2H5.js';
+export { RunIdentity, escapeSegment, runFlow } from './chunk-27RZJAE2.js';
+import './chunk-2QXKDLGT.js';
 //# sourceMappingURL=runtime.js.map
 //# sourceMappingURL=runtime.js.map

package/dist/schema/index.d.cts

@@ -1,4 +1,4 @@
-import { W as WorkflowInput, P as PortDescriptor, F as FlowGraph } from '../types-JFYjPJAG.cjs';
+import { G as WorkflowInput, P as PortDescriptor, F as FlowGraph } from '../types-B-Syk9-M.cjs';
 import '@xyflow/react';
 
 /** Schema version. Bump on breaking shape changes; add migrations as needed. */
@@ -76,11 +76,24 @@ type WorkflowSchemaNode = {
     inputs?: PortDescriptor[];
     outputs?: PortDescriptor[];
     /**
-     * Visual layout — additive + optional. `parentId`/`extent` carry node grouping
-     * (swimlanes / containers); `width`/`height` carry an explicit (resized) size;
-     * `style` carries inline presentation. A runtime that only walks edges/ports
-     * (e.g. the PHP twin) ignores all of these — they exist purely for the canvas,
-     * so an older reader that doesn't know them simply drops them.
+     * Node grouping and visual layout — additive + optional. `parentId`/`extent`
+     * say which container a node sits in (swimlanes); `width`/`height` carry an
+     * explicit (resized) size; `style` carries inline presentation.
+     *
+     * **`parentId` is NOT decoration, and a runtime that drops it is wrong.** It
+     * decides which terminal a node talks to — a terminal lane owns one session
+     * and membership is this field, deliberately, so there is no second copy of
+     * the grouping in each node's config to drift from what the canvas shows.
+     *
+     * This comment used to say these fields exist "purely for the canvas", so a
+     * runtime that only walks edges and ports could ignore all of them. The
+     * Python twin read that literally and carried none of them: a graph loaded
+     * there and saved back lost every grouping a person had drawn, silently. The
+     * sentence was true when it was written and became false without being
+     * revisited, which is the more common way a comment does harm.
+     *
+     * An older reader that does not know these fields still drops them — that is
+     * forward-compatibility, not permission.
      */
     parentId?: string;
     extent?: "parent" | [[number, number], [number, number]];

package/dist/schema/index.d.ts

@@ -1,4 +1,4 @@
-import { W as WorkflowInput, P as PortDescriptor, F as FlowGraph } from '../types-JFYjPJAG.js';
+import { G as WorkflowInput, P as PortDescriptor, F as FlowGraph } from '../types-B-Syk9-M.js';
 import '@xyflow/react';
 
 /** Schema version. Bump on breaking shape changes; add migrations as needed. */
@@ -76,11 +76,24 @@ type WorkflowSchemaNode = {
     inputs?: PortDescriptor[];
     outputs?: PortDescriptor[];
     /**
-     * Visual layout — additive + optional. `parentId`/`extent` carry node grouping
-     * (swimlanes / containers); `width`/`height` carry an explicit (resized) size;
-     * `style` carries inline presentation. A runtime that only walks edges/ports
-     * (e.g. the PHP twin) ignores all of these — they exist purely for the canvas,
-     * so an older reader that doesn't know them simply drops them.
+     * Node grouping and visual layout — additive + optional. `parentId`/`extent`
+     * say which container a node sits in (swimlanes); `width`/`height` carry an
+     * explicit (resized) size; `style` carries inline presentation.
+     *
+     * **`parentId` is NOT decoration, and a runtime that drops it is wrong.** It
+     * decides which terminal a node talks to — a terminal lane owns one session
+     * and membership is this field, deliberately, so there is no second copy of
+     * the grouping in each node's config to drift from what the canvas shows.
+     *
+     * This comment used to say these fields exist "purely for the canvas", so a
+     * runtime that only walks edges and ports could ignore all of them. The
+     * Python twin read that literally and carried none of them: a graph loaded
+     * there and saved back lost every grouping a person had drawn, silently. The
+     * sentence was true when it was written and became false without being
+     * revisited, which is the more common way a comment does harm.
+     *
+     * An older reader that does not know these fields still drops them — that is
+     * forward-compatibility, not permission.
      */
     parentId?: string;
     extent?: "parent" | [[number, number], [number, number]];