@particle-academy/fancy-flow 0.38.0 → 0.40.0

package/dist/index.d.cts

@@ -347,47 +347,23 @@ declare function paletteDropHandlers(onDrop: (kindName: string, evt: React.DragE
     onDrop: (e: React.DragEvent) => void;
 };
 
-type NodeConfigPanelProps = {
-    /** Currently-selected node — pass null to render the empty state. */
-    node: FlowNode | null;
-    /** Called when the user edits the node label, description, or config. */
-    onChange: (next: FlowNode) => void;
-    /**
-     * Called when the user deletes the node from the panel. When provided, the
-     * panel renders a "Delete node" button while a node is selected — so the
-     * delete affordance lives WITH the panel (a dev composing their own editor
-     * gets it for free), rather than in a host toolbar it has to re-implement.
-     */
-    onDelete?: (node: FlowNode) => void;
-    /** Label for the delete button. Default "Delete node". */
-    deleteLabel?: string;
-    /** Optional header content (e.g. close button). */
-    header?: ReactNode;
-    /** Optional credential picker hook — host renders the picker. */
-    renderCredentialField?: (props: {
-        credentialType: string;
-        value: unknown;
-        onChange: (next: unknown) => void;
-    }) => ReactNode;
-    /**
-     * Optional document editor hook — host renders the editor for `document`
-     * fields. Lets rich authored content live in node config without fancy-flow
-     * taking on a document model.
-     */
-    renderDocumentField?: (props: {
-        documentType?: string;
-        value: unknown;
-        onChange: (next: unknown) => void;
-    }) => ReactNode;
-    className?: string;
-    style?: React.CSSProperties;
+/** What a host renderer is handed. */
+type ConfigFieldRenderContext = {
+    field: ConfigField;
+    value: unknown;
+    onChange: (next: unknown) => void;
+    /** The id the panel's `<label>` points at. Put it on your control. */
+    id?: string;
 };
 /**
- * NodeConfigPanel — schema-driven form for the selected node. Defers to
- * `kind.renderPanel` if the kind opts out of the auto-form.
+ * Render one field. Return `null` to fall back to the package's own rendering,
+ * so a host can claim a type conditionally instead of reimplementing every case.
+ *
+ * Named `...Fn` because `ConfigFieldRenderer` is already the component this
+ * module exports; two things with one name in a public API is a paper cut a
+ * consumer pays for, not us.
  */
-declare function NodeConfigPanel({ node, onChange, onDelete, deleteLabel, header, renderCredentialField, renderDocumentField, className, style, }: NodeConfigPanelProps): react.JSX.Element;
-
+type ConfigFieldRenderFn = (ctx: ConfigFieldRenderContext) => ReactNode;
 type ConfigFieldRendererProps = {
     field: ConfigField;
     value: unknown;
@@ -420,6 +396,22 @@ type ConfigFieldRendererProps = {
         value: unknown;
         onChange: (next: unknown) => void;
     }) => ReactNode;
+    /**
+     * Host renderers keyed by field `type`.
+     *
+     * The generic form of `renderDocumentField` / `renderCredentialField`: those
+     * cover two types the package deliberately does not interpret, this covers
+     * any type at all — including one the package has never heard of.
+     *
+     * Without it, a richer field had to be rendered OUTSIDE the panel, so that
+     * node's config stopped living where every other field does. An unknown type
+     * also fell through to `default:` and rendered nothing, so the schema said the
+     * field existed and the panel showed empty space.
+     *
+     * Consulted BEFORE the built-in switch, so a host can also replace a built-in
+     * (react-fancy inputs, say) through the same seam rather than a second one.
+     */
+    fieldRenderers?: Record<string, ConfigFieldRenderFn>;
 };
 /**
  * ConfigFieldRenderer — dispatches to the right input element per field type.
@@ -432,7 +424,50 @@ type ConfigFieldRendererProps = {
  * Each control carries the caller's `id` and a `data-ff-field` handle keyed by
  * the field, so a label can point at it and an agent can find it by name.
  */
-declare function ConfigFieldRenderer({ field, value, onChange, id, renderCredentialField, renderDocumentField, }: ConfigFieldRendererProps): react.JSX.Element | null;
+declare function ConfigFieldRenderer({ field, value, onChange, id, renderCredentialField, renderDocumentField, fieldRenderers, }: ConfigFieldRendererProps): react.JSX.Element | null;
+
+type NodeConfigPanelProps = {
+    /** Currently-selected node — pass null to render the empty state. */
+    node: FlowNode | null;
+    /** Called when the user edits the node label, description, or config. */
+    onChange: (next: FlowNode) => void;
+    /**
+     * Called when the user deletes the node from the panel. When provided, the
+     * panel renders a "Delete node" button while a node is selected — so the
+     * delete affordance lives WITH the panel (a dev composing their own editor
+     * gets it for free), rather than in a host toolbar it has to re-implement.
+     */
+    onDelete?: (node: FlowNode) => void;
+    /** Label for the delete button. Default "Delete node". */
+    deleteLabel?: string;
+    /** Optional header content (e.g. close button). */
+    header?: ReactNode;
+    /** Optional credential picker hook — host renders the picker. */
+    renderCredentialField?: (props: {
+        credentialType: string;
+        value: unknown;
+        onChange: (next: unknown) => void;
+    }) => ReactNode;
+    /**
+     * Optional document editor hook — host renders the editor for `document`
+     * fields. Lets rich authored content live in node config without fancy-flow
+     * taking on a document model.
+     */
+    /** Host renderers keyed by field `type`. See {@link ConfigFieldRenderer}. */
+    fieldRenderers?: Record<string, ConfigFieldRenderFn>;
+    renderDocumentField?: (props: {
+        documentType?: string;
+        value: unknown;
+        onChange: (next: unknown) => void;
+    }) => ReactNode;
+    className?: string;
+    style?: React.CSSProperties;
+};
+/**
+ * NodeConfigPanel — schema-driven form for the selected node. Defers to
+ * `kind.renderPanel` if the kind opts out of the auto-form.
+ */
+declare function NodeConfigPanel({ node, onChange, onDelete, deleteLabel, header, renderCredentialField, renderDocumentField, fieldRenderers, className, style, }: NodeConfigPanelProps): react.JSX.Element;
 
 /** Entry-point node — outputs only, no inputs. */
 declare function TriggerNodeInner(props: NodeProps<FlowNode>): react.JSX.Element;
@@ -580,4 +615,72 @@ type FlowRunFeedProps = {
  */
 declare function FlowRunFeed({ entries, showHeader, title, running, className, style }: FlowRunFeedProps): react.JSX.Element;
 
-export { ActionNode, type AlignEdge, AutoLayoutOptions, ConfigField, ConfigFieldRenderer, type ConfigFieldRendererProps, ConnectionValidatorOptions, DecisionNode, ExecutorRegistry, FlowCanvas, type FlowCanvasProps, FlowEditor, type FlowEditorAction, type FlowEditorApi, type FlowEditorBuiltins, type FlowEditorProps, type FlowEditorSlots, FlowGraph, FlowNode, type FlowNodeRenderProps, FlowRunControls, type FlowRunControlsProps, FlowRunFeed, FlowRunFeedEntry, type FlowRunFeedProps, LaneNode, NodeCategory, NodeConfigPanel, type NodeConfigPanelProps, NodeKindDefinition, NodePalette, type NodePaletteProps, NodePort, type NodePortProps, type NodePortSide, type NodePortType, NodeRunStatus, NodeShell, type NodeShellProps, NoteNode, OutputNode, SubgraphNode, TriggerNode, WorkflowMetadata, WorkflowSchema, alignNodes, cloneSubgraph, defaultNodeTypes, defineNode, distributeNodes, paletteDropHandlers, reconnectEdge, useFlowEditor, useFlowEditorOptional };
+/**
+ * The fancy-flow Live Contract — the run / job stream shape.
+ *
+ * Pure data, with `LiveContract` imported as a TYPE, so this adds no dependency.
+ * `FancyFlow\Laravel\LiveContract` declares the identical list and both sides
+ * assert parity.
+ *
+ * ## What makes this shape different
+ *
+ * A run emits far more than it stores. `NodeStatusChanged` and `NodeOutput`
+ * fire per node, many times a second on a wide graph — and a node's log line is
+ * not a cache entry, it is a **stream**. So the contract covers the run's
+ * DURABLE state (does this run exist, has it finished, is it waiting on a
+ * person) and deliberately leaves per-node chatter to `useFancyStream`, the
+ * same split the whiteboard makes between its document and its cursors.
+ *
+ * Get that wrong and a 40-node run invalidates the run list forty times while
+ * it executes, each one a re-fetch that tells the UI nothing it did not already
+ * learn from the stream.
+ *
+ * ## `awaiting` is the one that matters
+ *
+ * A run parking on a human step is the event a host most needs to react to —
+ * it is when a form has to appear in front of somebody. It gets its own event
+ * rather than folding into `updated`, so a host can subscribe to just that.
+ *
+ * ## Broadcast status, stated plainly
+ *
+ * `fancy-flow-php` currently dispatches these as **in-process Laravel events**;
+ * none of them implement `ShouldBroadcast` yet. This contract is therefore the
+ * agreed vocabulary rather than a description of traffic already on the wire: a
+ * host that wants live runs today re-broadcasts these under these names. Making
+ * the PHP events broadcast natively is a separate change, because it turns on
+ * websocket traffic for every consumer.
+ */
+declare const flowLive: {
+    readonly namespace: "flow";
+    readonly events: readonly [{
+        readonly event: "flow.run.created";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+    }, {
+        readonly event: "flow.run.updated";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+    }, {
+        readonly event: "flow.run.completed";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+    }, {
+        readonly event: "flow.run.awaiting";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+        readonly note: "A run parking on a human step — the moment a form has to appear in front of somebody. Its own event so a host can subscribe to just that, rather than filtering every update.";
+    }, {
+        readonly event: "flow.run.failed";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+        readonly note: "Not one of the standard verbs: a failed run is a terminal state a host renders differently from a completed one, so collapsing the two would lose the distinction.";
+    }];
+};
+/**
+ * Per-run keys, for a host showing a single run rather than the list.
+ *
+ * The contract declares prefixes because it is static data and a run id is not
+ * known until runtime. TanStack matches by prefix, so `["flow", "runs"]` still
+ * invalidates `["flow", "runs", runId]`.
+ */
+declare const flowKeys: {
+    readonly runs: () => readonly ["flow", "runs"];
+    readonly run: (runId: string) => readonly ["flow", "runs", string];
+};
+
+export { ActionNode, type AlignEdge, AutoLayoutOptions, ConfigField, type ConfigFieldRenderContext, type ConfigFieldRenderFn, ConfigFieldRenderer, type ConfigFieldRendererProps, ConnectionValidatorOptions, DecisionNode, ExecutorRegistry, FlowCanvas, type FlowCanvasProps, FlowEditor, type FlowEditorAction, type FlowEditorApi, type FlowEditorBuiltins, type FlowEditorProps, type FlowEditorSlots, FlowGraph, FlowNode, type FlowNodeRenderProps, FlowRunControls, type FlowRunControlsProps, FlowRunFeed, FlowRunFeedEntry, type FlowRunFeedProps, LaneNode, NodeCategory, NodeConfigPanel, type NodeConfigPanelProps, NodeKindDefinition, NodePalette, type NodePaletteProps, NodePort, type NodePortProps, type NodePortSide, type NodePortType, NodeRunStatus, NodeShell, type NodeShellProps, NoteNode, OutputNode, SubgraphNode, TriggerNode, WorkflowMetadata, WorkflowSchema, alignNodes, cloneSubgraph, defaultNodeTypes, defineNode, distributeNodes, flowKeys, flowLive, paletteDropHandlers, reconnectEdge, useFlowEditor, useFlowEditorOptional };

package/dist/index.d.ts

@@ -347,47 +347,23 @@ declare function paletteDropHandlers(onDrop: (kindName: string, evt: React.DragE
     onDrop: (e: React.DragEvent) => void;
 };
 
-type NodeConfigPanelProps = {
-    /** Currently-selected node — pass null to render the empty state. */
-    node: FlowNode | null;
-    /** Called when the user edits the node label, description, or config. */
-    onChange: (next: FlowNode) => void;
-    /**
-     * Called when the user deletes the node from the panel. When provided, the
-     * panel renders a "Delete node" button while a node is selected — so the
-     * delete affordance lives WITH the panel (a dev composing their own editor
-     * gets it for free), rather than in a host toolbar it has to re-implement.
-     */
-    onDelete?: (node: FlowNode) => void;
-    /** Label for the delete button. Default "Delete node". */
-    deleteLabel?: string;
-    /** Optional header content (e.g. close button). */
-    header?: ReactNode;
-    /** Optional credential picker hook — host renders the picker. */
-    renderCredentialField?: (props: {
-        credentialType: string;
-        value: unknown;
-        onChange: (next: unknown) => void;
-    }) => ReactNode;
-    /**
-     * Optional document editor hook — host renders the editor for `document`
-     * fields. Lets rich authored content live in node config without fancy-flow
-     * taking on a document model.
-     */
-    renderDocumentField?: (props: {
-        documentType?: string;
-        value: unknown;
-        onChange: (next: unknown) => void;
-    }) => ReactNode;
-    className?: string;
-    style?: React.CSSProperties;
+/** What a host renderer is handed. */
+type ConfigFieldRenderContext = {
+    field: ConfigField;
+    value: unknown;
+    onChange: (next: unknown) => void;
+    /** The id the panel's `<label>` points at. Put it on your control. */
+    id?: string;
 };
 /**
- * NodeConfigPanel — schema-driven form for the selected node. Defers to
- * `kind.renderPanel` if the kind opts out of the auto-form.
+ * Render one field. Return `null` to fall back to the package's own rendering,
+ * so a host can claim a type conditionally instead of reimplementing every case.
+ *
+ * Named `...Fn` because `ConfigFieldRenderer` is already the component this
+ * module exports; two things with one name in a public API is a paper cut a
+ * consumer pays for, not us.
  */
-declare function NodeConfigPanel({ node, onChange, onDelete, deleteLabel, header, renderCredentialField, renderDocumentField, className, style, }: NodeConfigPanelProps): react.JSX.Element;
-
+type ConfigFieldRenderFn = (ctx: ConfigFieldRenderContext) => ReactNode;
 type ConfigFieldRendererProps = {
     field: ConfigField;
     value: unknown;
@@ -420,6 +396,22 @@ type ConfigFieldRendererProps = {
         value: unknown;
         onChange: (next: unknown) => void;
     }) => ReactNode;
+    /**
+     * Host renderers keyed by field `type`.
+     *
+     * The generic form of `renderDocumentField` / `renderCredentialField`: those
+     * cover two types the package deliberately does not interpret, this covers
+     * any type at all — including one the package has never heard of.
+     *
+     * Without it, a richer field had to be rendered OUTSIDE the panel, so that
+     * node's config stopped living where every other field does. An unknown type
+     * also fell through to `default:` and rendered nothing, so the schema said the
+     * field existed and the panel showed empty space.
+     *
+     * Consulted BEFORE the built-in switch, so a host can also replace a built-in
+     * (react-fancy inputs, say) through the same seam rather than a second one.
+     */
+    fieldRenderers?: Record<string, ConfigFieldRenderFn>;
 };
 /**
  * ConfigFieldRenderer — dispatches to the right input element per field type.
@@ -432,7 +424,50 @@ type ConfigFieldRendererProps = {
  * Each control carries the caller's `id` and a `data-ff-field` handle keyed by
  * the field, so a label can point at it and an agent can find it by name.
  */
-declare function ConfigFieldRenderer({ field, value, onChange, id, renderCredentialField, renderDocumentField, }: ConfigFieldRendererProps): react.JSX.Element | null;
+declare function ConfigFieldRenderer({ field, value, onChange, id, renderCredentialField, renderDocumentField, fieldRenderers, }: ConfigFieldRendererProps): react.JSX.Element | null;
+
+type NodeConfigPanelProps = {
+    /** Currently-selected node — pass null to render the empty state. */
+    node: FlowNode | null;
+    /** Called when the user edits the node label, description, or config. */
+    onChange: (next: FlowNode) => void;
+    /**
+     * Called when the user deletes the node from the panel. When provided, the
+     * panel renders a "Delete node" button while a node is selected — so the
+     * delete affordance lives WITH the panel (a dev composing their own editor
+     * gets it for free), rather than in a host toolbar it has to re-implement.
+     */
+    onDelete?: (node: FlowNode) => void;
+    /** Label for the delete button. Default "Delete node". */
+    deleteLabel?: string;
+    /** Optional header content (e.g. close button). */
+    header?: ReactNode;
+    /** Optional credential picker hook — host renders the picker. */
+    renderCredentialField?: (props: {
+        credentialType: string;
+        value: unknown;
+        onChange: (next: unknown) => void;
+    }) => ReactNode;
+    /**
+     * Optional document editor hook — host renders the editor for `document`
+     * fields. Lets rich authored content live in node config without fancy-flow
+     * taking on a document model.
+     */
+    /** Host renderers keyed by field `type`. See {@link ConfigFieldRenderer}. */
+    fieldRenderers?: Record<string, ConfigFieldRenderFn>;
+    renderDocumentField?: (props: {
+        documentType?: string;
+        value: unknown;
+        onChange: (next: unknown) => void;
+    }) => ReactNode;
+    className?: string;
+    style?: React.CSSProperties;
+};
+/**
+ * NodeConfigPanel — schema-driven form for the selected node. Defers to
+ * `kind.renderPanel` if the kind opts out of the auto-form.
+ */
+declare function NodeConfigPanel({ node, onChange, onDelete, deleteLabel, header, renderCredentialField, renderDocumentField, fieldRenderers, className, style, }: NodeConfigPanelProps): react.JSX.Element;
 
 /** Entry-point node — outputs only, no inputs. */
 declare function TriggerNodeInner(props: NodeProps<FlowNode>): react.JSX.Element;
@@ -580,4 +615,72 @@ type FlowRunFeedProps = {
  */
 declare function FlowRunFeed({ entries, showHeader, title, running, className, style }: FlowRunFeedProps): react.JSX.Element;
 
-export { ActionNode, type AlignEdge, AutoLayoutOptions, ConfigField, ConfigFieldRenderer, type ConfigFieldRendererProps, ConnectionValidatorOptions, DecisionNode, ExecutorRegistry, FlowCanvas, type FlowCanvasProps, FlowEditor, type FlowEditorAction, type FlowEditorApi, type FlowEditorBuiltins, type FlowEditorProps, type FlowEditorSlots, FlowGraph, FlowNode, type FlowNodeRenderProps, FlowRunControls, type FlowRunControlsProps, FlowRunFeed, FlowRunFeedEntry, type FlowRunFeedProps, LaneNode, NodeCategory, NodeConfigPanel, type NodeConfigPanelProps, NodeKindDefinition, NodePalette, type NodePaletteProps, NodePort, type NodePortProps, type NodePortSide, type NodePortType, NodeRunStatus, NodeShell, type NodeShellProps, NoteNode, OutputNode, SubgraphNode, TriggerNode, WorkflowMetadata, WorkflowSchema, alignNodes, cloneSubgraph, defaultNodeTypes, defineNode, distributeNodes, paletteDropHandlers, reconnectEdge, useFlowEditor, useFlowEditorOptional };
+/**
+ * The fancy-flow Live Contract — the run / job stream shape.
+ *
+ * Pure data, with `LiveContract` imported as a TYPE, so this adds no dependency.
+ * `FancyFlow\Laravel\LiveContract` declares the identical list and both sides
+ * assert parity.
+ *
+ * ## What makes this shape different
+ *
+ * A run emits far more than it stores. `NodeStatusChanged` and `NodeOutput`
+ * fire per node, many times a second on a wide graph — and a node's log line is
+ * not a cache entry, it is a **stream**. So the contract covers the run's
+ * DURABLE state (does this run exist, has it finished, is it waiting on a
+ * person) and deliberately leaves per-node chatter to `useFancyStream`, the
+ * same split the whiteboard makes between its document and its cursors.
+ *
+ * Get that wrong and a 40-node run invalidates the run list forty times while
+ * it executes, each one a re-fetch that tells the UI nothing it did not already
+ * learn from the stream.
+ *
+ * ## `awaiting` is the one that matters
+ *
+ * A run parking on a human step is the event a host most needs to react to —
+ * it is when a form has to appear in front of somebody. It gets its own event
+ * rather than folding into `updated`, so a host can subscribe to just that.
+ *
+ * ## Broadcast status, stated plainly
+ *
+ * `fancy-flow-php` currently dispatches these as **in-process Laravel events**;
+ * none of them implement `ShouldBroadcast` yet. This contract is therefore the
+ * agreed vocabulary rather than a description of traffic already on the wire: a
+ * host that wants live runs today re-broadcasts these under these names. Making
+ * the PHP events broadcast natively is a separate change, because it turns on
+ * websocket traffic for every consumer.
+ */
+declare const flowLive: {
+    readonly namespace: "flow";
+    readonly events: readonly [{
+        readonly event: "flow.run.created";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+    }, {
+        readonly event: "flow.run.updated";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+    }, {
+        readonly event: "flow.run.completed";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+    }, {
+        readonly event: "flow.run.awaiting";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+        readonly note: "A run parking on a human step — the moment a form has to appear in front of somebody. Its own event so a host can subscribe to just that, rather than filtering every update.";
+    }, {
+        readonly event: "flow.run.failed";
+        readonly keys: readonly [readonly ["flow", "runs"]];
+        readonly note: "Not one of the standard verbs: a failed run is a terminal state a host renders differently from a completed one, so collapsing the two would lose the distinction.";
+    }];
+};
+/**
+ * Per-run keys, for a host showing a single run rather than the list.
+ *
+ * The contract declares prefixes because it is static data and a run id is not
+ * known until runtime. TanStack matches by prefix, so `["flow", "runs"]` still
+ * invalidates `["flow", "runs", runId]`.
+ */
+declare const flowKeys: {
+    readonly runs: () => readonly ["flow", "runs"];
+    readonly run: (runId: string) => readonly ["flow", "runs", string];
+};
+
+export { ActionNode, type AlignEdge, AutoLayoutOptions, ConfigField, type ConfigFieldRenderContext, type ConfigFieldRenderFn, ConfigFieldRenderer, type ConfigFieldRendererProps, ConnectionValidatorOptions, DecisionNode, ExecutorRegistry, FlowCanvas, type FlowCanvasProps, FlowEditor, type FlowEditorAction, type FlowEditorApi, type FlowEditorBuiltins, type FlowEditorProps, type FlowEditorSlots, FlowGraph, FlowNode, type FlowNodeRenderProps, FlowRunControls, type FlowRunControlsProps, FlowRunFeed, FlowRunFeedEntry, type FlowRunFeedProps, LaneNode, NodeCategory, NodeConfigPanel, type NodeConfigPanelProps, NodeKindDefinition, NodePalette, type NodePaletteProps, NodePort, type NodePortProps, type NodePortSide, type NodePortType, NodeRunStatus, NodeShell, type NodeShellProps, NoteNode, OutputNode, SubgraphNode, TriggerNode, WorkflowMetadata, WorkflowSchema, alignNodes, cloneSubgraph, defaultNodeTypes, defineNode, distributeNodes, flowKeys, flowLive, paletteDropHandlers, reconnectEdge, useFlowEditor, useFlowEditorOptional };

package/dist/index.js

@@ -115,9 +115,15 @@ function ConfigFieldRenderer({
   onChange,
   id,
   renderCredentialField,
-  renderDocumentField
+  renderDocumentField,
+  fieldRenderers
 }) {
   const handle = { id, "data-ff-field": field.key };
+  const custom = fieldRenderers?.[field.type];
+  if (custom) {
+    const rendered = custom({ field, value, onChange, id });
+    if (rendered !== null && rendered !== void 0) return /* @__PURE__ */ jsx(Fragment, { children: rendered });
+  }
   switch (field.type) {
     case "text": {
       if (field.choices?.length) {
@@ -225,7 +231,8 @@ function ConfigFieldRenderer({
           value,
           onChange,
           renderCredentialField,
-          renderDocumentField
+          renderDocumentField,
+          fieldRenderers
         }
       );
     case "keyvalue":
@@ -278,7 +285,8 @@ function RepeaterField({
   value,
   onChange,
   renderCredentialField,
-  renderDocumentField
+  renderDocumentField,
+  fieldRenderers
 }) {
   const rows = Array.isArray(value) ? value : [];
   const max = field.maxItems ?? Infinity;
@@ -360,7 +368,8 @@ function RepeaterField({
             value: row[sub.key],
             onChange: (cell) => setCell(i, sub.key, cell),
             renderCredentialField,
-            renderDocumentField
+            renderDocumentField,
+            fieldRenderers
           }
         )
       ] }, sub.key))
@@ -492,6 +501,7 @@ function NodeConfigPanel({
   header,
   renderCredentialField,
   renderDocumentField,
+  fieldRenderers,
   className,
   style
 }) {
@@ -596,7 +606,8 @@ function NodeConfigPanel({
             value: config[field.key],
             onChange: (v) => setConfigValue(field.key, v),
             renderCredentialField,
-            renderDocumentField: documentField
+            renderDocumentField: documentField,
+            fieldRenderers
           }
         )
       ] }, field.key))
@@ -1506,9 +1517,33 @@ function NodePort({ side, type, id, style, title, className }) {
   );
 }
 
+// src/live.ts
+var flowLive = {
+  namespace: "flow",
+  events: [
+    { event: "flow.run.created", keys: [["flow", "runs"]] },
+    { event: "flow.run.updated", keys: [["flow", "runs"]] },
+    { event: "flow.run.completed", keys: [["flow", "runs"]] },
+    {
+      event: "flow.run.awaiting",
+      keys: [["flow", "runs"]],
+      note: "A run parking on a human step \u2014 the moment a form has to appear in front of somebody. Its own event so a host can subscribe to just that, rather than filtering every update."
+    },
+    {
+      event: "flow.run.failed",
+      keys: [["flow", "runs"]],
+      note: "Not one of the standard verbs: a failed run is a terminal state a host renders differently from a completed one, so collapsing the two would lose the distinction."
+    }
+  ]
+};
+var flowKeys = {
+  runs: () => ["flow", "runs"],
+  run: (runId) => ["flow", "runs", runId]
+};
+
 // src/index.ts
 registerBuiltinKinds();
 
-export { ConfigFieldRenderer, FlowEditor, FlowRunControls, FlowRunFeed, NodeConfigPanel, NodePalette, NodePort, defineNode, paletteDropHandlers };
+export { ConfigFieldRenderer, FlowEditor, FlowRunControls, FlowRunFeed, NodeConfigPanel, NodePalette, NodePort, defineNode, flowKeys, flowLive, paletteDropHandlers };
 //# sourceMappingURL=index.js.map
 //# sourceMappingURL=index.js.map