@particle-academy/fancy-flow 0.65.2 → 0.66.0

package/dist/ux.d.cts

@@ -1,7 +1,7 @@
 import { EffectRegistry, DispatchActor } from '@particle-academy/fancy-auto-common';
 export { AutoActivityEvent } from '@particle-academy/fancy-auto-common';
-import { a as NodeCategory, C as ConfigField } from './types-D71SKA5A.cjs';
-import { E as ExecutorRegistry } from './types-JFYjPJAG.cjs';
+import { a as NodeCategory, C as ConfigField } from './types-C2ATTmjN.cjs';
+import { E as ExecutorRegistry } from './types-B-Syk9-M.cjs';
 import 'react';
 import '@xyflow/react';
 import './pause-9iT4tCEV.cjs';

package/dist/ux.d.ts

@@ -1,7 +1,7 @@
 import { EffectRegistry, DispatchActor } from '@particle-academy/fancy-auto-common';
 export { AutoActivityEvent } from '@particle-academy/fancy-auto-common';
-import { a as NodeCategory, C as ConfigField } from './types-Ckhz-YwC.js';
-import { E as ExecutorRegistry } from './types-JFYjPJAG.js';
+import { a as NodeCategory, C as ConfigField } from './types-VunLGqrn.js';
+import { E as ExecutorRegistry } from './types-B-Syk9-M.js';
 import 'react';
 import '@xyflow/react';
 import './pause-9iT4tCEV.js';

package/dist/ux.js

@@ -1,6 +1,6 @@
-import { registerNodeKind } from './chunk-JF6WCRBU.js';
+import { registerNodeKind } from './chunk-HQGOFGAL.js';
 import './chunk-F5RPRB7A.js';
-import './chunk-USL4FMFU.js';
+import './chunk-2QXKDLGT.js';
 import { useMemo } from 'react';
 import { createEffectDispatcher } from '@particle-academy/fancy-auto-common';
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@particle-academy/fancy-flow",
-  "version": "0.65.2",
+  "version": "0.66.0",
   "description": "Workflow editor + runner. Six built-in node kits (trigger / action / decision / output / note / subgraph), tokenized theme, topological execution with per-node status. React-flow bundled; consumers npm install fancy-flow and get nothing extra.",
   "repository": {
     "type": "git",
@@ -134,6 +134,16 @@
         "default": "./dist/llm/prism.cjs"
       }
     },
+    "./terminal/fancy-term-host": {
+      "import": {
+        "types": "./dist/terminal/fancy-term-host.d.ts",
+        "default": "./dist/terminal/fancy-term-host.js"
+      },
+      "require": {
+        "types": "./dist/terminal/fancy-term-host.d.cts",
+        "default": "./dist/terminal/fancy-term-host.cjs"
+      }
+    },
     "./fields/react-fancy": {
       "import": {
         "types": "./dist/fields/react-fancy.d.ts",

package/dist/capabilities-BYa5p5jw.d.cts

@@ -1,112 +0,0 @@
-import { F as FlowGraph } from './types-JFYjPJAG.cjs';
-
-/**
- * Host capabilities — the services core nodes need but must never depend on.
- *
- * A node that imports a provider SDK forces every consumer to install it: a
- * workflow app that never calls a model should not inherit an LLM dependency.
- * So core declares the CONTRACT and the host supplies the implementation, the
- * same arrangement `renderDocumentField` already uses for documents.
- *
- * That keeps opinionated nodes in core without their opinions: `llm_branch`
- * ships the routing semantics, port derivation and config UI, while whichever
- * client the host registers — Prism, an OpenAI SDK, a local model, a fake in a
- * test — decides how the question actually gets asked.
- *
- * Registration is deliberately explicit and typed per capability rather than a
- * stringly-keyed bag, so a missing one is a clear error at the seam instead of
- * an undefined somewhere downstream.
- */
-type LlmRoute = {
-    port: string;
-    description?: string;
-};
-type LlmRouteRequest = {
-    /** Optional framing for the decision. */
-    system?: string;
-    /** What the model is deciding about. */
-    prompt: string;
-    /** The ports it must choose between. */
-    routes: LlmRoute[];
-    provider?: string;
-    model?: string;
-    /** Host-resolved credential reference, never a raw key. */
-    credential?: string;
-};
-type LlmRouteChoice = {
-    /** Must be one of the requested route ports. */
-    port: string;
-    /** Why — carried down the chosen port so a run is explainable afterwards. */
-    reason?: string;
-};
-/**
- * The only thing core asks of an LLM: given routes, pick one.
- *
- * Deliberately not a general chat interface. A narrow contract is one a host
- * can satisfy in a few lines over any SDK, and it keeps the choice
- * machine-checkable — an implementation should constrain the model to the
- * declared ports (structured output / enum) rather than parsing prose.
- */
-type LlmClient = {
-    chooseRoute: (request: LlmRouteRequest) => Promise<LlmRouteChoice> | LlmRouteChoice;
-};
-/** Install the host's LLM client. Returns an unregister function. */
-declare function registerLlmClient(client: LlmClient): () => void;
-declare function getLlmClient(): LlmClient | null;
-/**
- * Why a workflow reference could not be resolved.
- *
- * `missing` and `version-mismatch` are deliberately distinct. Collapsing them
- * into a bare null makes "no such workflow" indistinguishable from "that
- * workflow exists, but it is not the one you pinned" — and the second wants an
- * error naming both versions, because it is the interesting failure.
- */
-type WorkflowResolutionFailure = {
-    reason: "missing" | "version-mismatch";
-    /** The version the host actually holds, when it holds one. */
-    available?: number;
-    message?: string;
-};
-type WorkflowResolution = FlowGraph | WorkflowResolutionFailure | null;
-/**
- * Resolve a workflow reference to a runnable graph.
- *
- * `subflow` names another workflow rather than embedding it, so the host owns
- * where workflows live — a database, a file, an API.
- *
- * ## Why `version` is here
- *
- * A workflow another workflow depends on is an INTERFACE, and interfaces need
- * pins. Without a version, a parent goes on calling `invoice-triage`, someone
- * edits that child, and the parent now runs different logic having reported
- * success the whole time — correct-looking, no error, wrong behaviour. The same
- * failure family as the 0.9.0 routing divergence.
- *
- * The parameter lives on the resolver rather than being encoded into the ref
- * string (`invoice-triage@3`) because a stringly-typed protocol is one every
- * host invents differently — the "three vocabularies for one node" problem.
- *
- * Raised by the MOIC Suite consumer, whose `workflow_ref` pins versions and
- * fails loudly on mismatch. Their point: a host COULD NOT implement pinning
- * before this, because the node had no way to ask and the resolver no way to
- * receive.
- *
- * Returning `null` still means "no such workflow". Return a
- * {@link WorkflowResolutionFailure} to distinguish a version mismatch.
- */
-type WorkflowResolver = (ref: string, version?: number) => Promise<WorkflowResolution> | WorkflowResolution;
-/** Narrow a resolver's return value to an explicit failure. */
-declare function isResolutionFailure(value: WorkflowResolution): value is WorkflowResolutionFailure;
-/** Install the host's workflow resolver. Returns an unregister function. */
-declare function registerWorkflowResolver(resolver: WorkflowResolver): () => void;
-declare function getWorkflowResolver(): WorkflowResolver | null;
-type CapabilityId = "llm" | "workflow_resolver" | "document";
-/**
- * Which capabilities are currently satisfied.
- *
- * Exists so a host (or the CLI, or an agent over MCP) can answer "what does
- * this graph need that I haven't wired?" BEFORE a run fails halfway through.
- */
-declare function capabilityStatus(): Record<CapabilityId, boolean>;
-
-export { type CapabilityId as C, type LlmClient as L, type WorkflowResolver as W, type LlmRouteRequest as a, type LlmRoute as b, type LlmRouteChoice as c, type WorkflowResolution as d, type WorkflowResolutionFailure as e, capabilityStatus as f, getLlmClient as g, getWorkflowResolver as h, isResolutionFailure as i, registerWorkflowResolver as j, registerLlmClient as r };

package/dist/capabilities-COOXRiNL.d.ts

@@ -1,112 +0,0 @@
-import { F as FlowGraph } from './types-JFYjPJAG.js';
-
-/**
- * Host capabilities — the services core nodes need but must never depend on.
- *
- * A node that imports a provider SDK forces every consumer to install it: a
- * workflow app that never calls a model should not inherit an LLM dependency.
- * So core declares the CONTRACT and the host supplies the implementation, the
- * same arrangement `renderDocumentField` already uses for documents.
- *
- * That keeps opinionated nodes in core without their opinions: `llm_branch`
- * ships the routing semantics, port derivation and config UI, while whichever
- * client the host registers — Prism, an OpenAI SDK, a local model, a fake in a
- * test — decides how the question actually gets asked.
- *
- * Registration is deliberately explicit and typed per capability rather than a
- * stringly-keyed bag, so a missing one is a clear error at the seam instead of
- * an undefined somewhere downstream.
- */
-type LlmRoute = {
-    port: string;
-    description?: string;
-};
-type LlmRouteRequest = {
-    /** Optional framing for the decision. */
-    system?: string;
-    /** What the model is deciding about. */
-    prompt: string;
-    /** The ports it must choose between. */
-    routes: LlmRoute[];
-    provider?: string;
-    model?: string;
-    /** Host-resolved credential reference, never a raw key. */
-    credential?: string;
-};
-type LlmRouteChoice = {
-    /** Must be one of the requested route ports. */
-    port: string;
-    /** Why — carried down the chosen port so a run is explainable afterwards. */
-    reason?: string;
-};
-/**
- * The only thing core asks of an LLM: given routes, pick one.
- *
- * Deliberately not a general chat interface. A narrow contract is one a host
- * can satisfy in a few lines over any SDK, and it keeps the choice
- * machine-checkable — an implementation should constrain the model to the
- * declared ports (structured output / enum) rather than parsing prose.
- */
-type LlmClient = {
-    chooseRoute: (request: LlmRouteRequest) => Promise<LlmRouteChoice> | LlmRouteChoice;
-};
-/** Install the host's LLM client. Returns an unregister function. */
-declare function registerLlmClient(client: LlmClient): () => void;
-declare function getLlmClient(): LlmClient | null;
-/**
- * Why a workflow reference could not be resolved.
- *
- * `missing` and `version-mismatch` are deliberately distinct. Collapsing them
- * into a bare null makes "no such workflow" indistinguishable from "that
- * workflow exists, but it is not the one you pinned" — and the second wants an
- * error naming both versions, because it is the interesting failure.
- */
-type WorkflowResolutionFailure = {
-    reason: "missing" | "version-mismatch";
-    /** The version the host actually holds, when it holds one. */
-    available?: number;
-    message?: string;
-};
-type WorkflowResolution = FlowGraph | WorkflowResolutionFailure | null;
-/**
- * Resolve a workflow reference to a runnable graph.
- *
- * `subflow` names another workflow rather than embedding it, so the host owns
- * where workflows live — a database, a file, an API.
- *
- * ## Why `version` is here
- *
- * A workflow another workflow depends on is an INTERFACE, and interfaces need
- * pins. Without a version, a parent goes on calling `invoice-triage`, someone
- * edits that child, and the parent now runs different logic having reported
- * success the whole time — correct-looking, no error, wrong behaviour. The same
- * failure family as the 0.9.0 routing divergence.
- *
- * The parameter lives on the resolver rather than being encoded into the ref
- * string (`invoice-triage@3`) because a stringly-typed protocol is one every
- * host invents differently — the "three vocabularies for one node" problem.
- *
- * Raised by the MOIC Suite consumer, whose `workflow_ref` pins versions and
- * fails loudly on mismatch. Their point: a host COULD NOT implement pinning
- * before this, because the node had no way to ask and the resolver no way to
- * receive.
- *
- * Returning `null` still means "no such workflow". Return a
- * {@link WorkflowResolutionFailure} to distinguish a version mismatch.
- */
-type WorkflowResolver = (ref: string, version?: number) => Promise<WorkflowResolution> | WorkflowResolution;
-/** Narrow a resolver's return value to an explicit failure. */
-declare function isResolutionFailure(value: WorkflowResolution): value is WorkflowResolutionFailure;
-/** Install the host's workflow resolver. Returns an unregister function. */
-declare function registerWorkflowResolver(resolver: WorkflowResolver): () => void;
-declare function getWorkflowResolver(): WorkflowResolver | null;
-type CapabilityId = "llm" | "workflow_resolver" | "document";
-/**
- * Which capabilities are currently satisfied.
- *
- * Exists so a host (or the CLI, or an agent over MCP) can answer "what does
- * this graph need that I haven't wired?" BEFORE a run fails halfway through.
- */
-declare function capabilityStatus(): Record<CapabilityId, boolean>;
-
-export { type CapabilityId as C, type LlmClient as L, type WorkflowResolver as W, type LlmRouteRequest as a, type LlmRoute as b, type LlmRouteChoice as c, type WorkflowResolution as d, type WorkflowResolutionFailure as e, capabilityStatus as f, getLlmClient as g, getWorkflowResolver as h, isResolutionFailure as i, registerWorkflowResolver as j, registerLlmClient as r };