@carlonicora/nextjs-jsonapi 5.2.0 → 5.3.0

package/dist/email-automations/index.d.mts

@@ -0,0 +1,303 @@
+import * as React from 'react';
+import { ReactNode } from 'react';
+import { a as EmailAutomationInterface, c as EmailAutomationStepInterface, b as EmailAutomationStepInput, f as EmailAutomationTriggerInterface, g as EmailAutomationFields, e as EmailAutomationEnrollmentInterface, h as EmailAutomationEnrollmentFields } from '../email-automation-enrollment.fields-BZvF14qx.mjs';
+import { Node, Edge, NodeProps, EdgeProps } from '@xyflow/react';
+import { U as UseTableStructureHook } from '../types-70acd-8C.mjs';
+import '../ApiDataInterface-BcZeXy5X.mjs';
+import '@tanstack/react-table';
+import '../types-Bq_UA8Lg.mjs';
+import 'lucide-react';
+import '../ApiRequestDataTypeInterface-CYEcRUrh.mjs';
+import '../useDataListRetriever-WEXL4bqB.mjs';
+
+/**
+ * Page container for the administrative email-automation list.
+ *
+ * Client component by necessity: `module={Modules.EmailAutomation}` is a
+ * registry entry carrying an icon component and methods, which a Server
+ * Component cannot pass across the boundary. Routes mount this container
+ * instead — the same shape as every other list page.
+ *
+ * No `forceHeader`: ContentListTable draws its own header row with the title
+ * and the create action, exactly as the company and user list pages do.
+ */
+declare function EmailAutomationsListContainer(): React.JSX.Element;
+
+type EmailAutomationContainerProps = {
+    automationId: string;
+};
+declare function EmailAutomationContainer({ automationId }: EmailAutomationContainerProps): React.JSX.Element;
+
+type EmailAutomationsListProps = {
+    /**
+     * Pass this whenever the list is the page's own content inside a
+     * `RoundPageContainer fullWidth`. Without it ContentListTable wraps itself in
+     * `rounded-md border`, drawing a second bordered card inside the page's
+     * rounded shell.
+     */
+    fullWidth?: boolean;
+};
+declare function EmailAutomationsList({ fullWidth }?: EmailAutomationsListProps): React.JSX.Element;
+
+/**
+ * Read-only list of the people in this automation (owner decision 6: no row
+ * actions). Rendered inside a tab, so it keeps its own bordered card (no
+ * `fullWidth`), as PricesList does inside ProductContainer.
+ */
+declare function EmailAutomationRecipientsList(): React.JSX.Element;
+
+type EmailAutomationEditorProps = {
+    automation?: EmailAutomationInterface;
+    propagateChanges?: (automation: EmailAutomationInterface) => void;
+    onSuccess?: () => void | Promise<void>;
+    trigger?: ReactNode;
+    forceShow?: boolean;
+    onClose?: () => void;
+    dialogOpen?: boolean;
+    onDialogOpenChange?: (open: boolean) => void;
+};
+declare function EmailAutomationEditor(props: EmailAutomationEditorProps): React.JSX.Element;
+
+type EmailStepEditorProps = {
+    step?: EmailAutomationStepInterface;
+    automationId: string;
+    /** Canvas position for a step created from the editor. */
+    initialPosition?: {
+        x: number;
+        y: number;
+    };
+    /** The head step's delay counts from entering the automation, not from a previous email. */
+    isHead?: boolean;
+    trigger?: ReactNode;
+    forceShow?: boolean;
+    onClose?: () => void;
+    dialogOpen?: boolean;
+    onDialogOpenChange?: (open: boolean) => void;
+    onSuccess?: () => void | Promise<void>;
+};
+declare function EmailStepEditor(props: EmailStepEditorProps): React.JSX.Element;
+
+/**
+ * Inline on/off for the automation page header, so pausing never needs the
+ * editor sheet. Off holds every enrolment in place (spec § "Sending" 3).
+ */
+declare function EmailAutomationActiveSwitch(): React.JSX.Element | null;
+
+declare function EmailAutomationCanvasTab(): React.JSX.Element;
+
+declare function EmailAutomationCanvas(): React.JSX.Element;
+
+/**
+ * Mounts EmailStepEditor (the EditorSheet the step uses everywhere) on top of
+ * the canvas, driven by `selectedStepId` from EmailAutomationContext. Copy of
+ * the app's ScenarioCanvasInspector with one branch.
+ *
+ *  - We control open state via `forceShow + dialogOpen + onDialogOpenChange`.
+ *  - On `onSuccess` we reload the canvas.
+ *  - The step comes from the context's `steps` (already loaded for the
+ *    canvas), so there is no per-step fetch.
+ */
+declare function EmailAutomationCanvasInspector(): React.JSX.Element | null;
+/**
+ * Build an `onDialogOpenChange` callback that ignores the editor's
+ * initial `open=false` notification. `useEditorDialog` (the hook
+ * inside every EditorSheet) initialises `open` to `false`, then in
+ * an effect sets it to `dialogOpen` (true). The "open=false" effect
+ * fires synchronously on mount and would otherwise wipe our canvas
+ * selection before the editor ever paints.
+ */
+declare function useUserClosedGuard(onClose: () => void): (open: boolean) => void;
+
+declare const TRIGGER_NODE_ID = "trigger";
+declare const TRIGGER_SOURCE_HANDLE = "trigger-source";
+declare const STEP_NODE_PREFIX = "step:";
+declare const STEP_SOURCE_HANDLE_PREFIX = "step-source-";
+declare const STEP_TARGET_HANDLE_PREFIX = "step-target-";
+declare const TRIGGER_NODE_WIDTH = 200;
+declare const TRIGGER_NODE_HEIGHT = 56;
+declare const STEP_NODE_WIDTH = 200;
+declare const STEP_NODE_HEIGHT = 72;
+/**
+ * The fields the canvas reads from a step. `EmailAutomationStepInterface`
+ * satisfies it structurally; the narrow shape keeps this function pure and
+ * testable with plain objects.
+ */
+type CanvasStep = {
+    id: string;
+    subject: string;
+    delayHours: number;
+    positionX?: number;
+    positionY?: number;
+    sentCount: number;
+    next?: {
+        id: string;
+    };
+};
+type TriggerNodeData = {
+    label: string;
+};
+type EmailStepNodeData = {
+    stepId: string;
+    subject: string;
+    sentCount: number;
+    orphan: boolean;
+    manuallyPositioned: boolean;
+};
+type DelayEdgeData = {
+    targetStepId: string;
+    delayHours: number;
+};
+type CanvasGraph = {
+    nodes: Node[];
+    edges: Edge[];
+    orphanIds: string[];
+};
+/**
+ * The head is the oldest step with no incoming NEXT, exactly as the API picks
+ * it (`findHead`). `steps` arrive ordered by createdAt ASC from
+ * `findByAutomation`, so the first step nobody points at is the head.
+ */
+declare function findHeadStepId(steps: CanvasStep[]): string | null;
+/**
+ * Turns the automation's steps into React Flow nodes and edges: the trigger
+ * node, one node per step, a trigger→head edge, and one edge per NEXT link.
+ * Steps not reachable from the head (walking next→next) are orphans: they
+ * never send and render dashed.
+ */
+declare function buildCanvasGraph(steps: CanvasStep[], triggerLabel: string): CanvasGraph;
+
+type TriggerNodeType = Node<{
+    data: TriggerNodeData;
+}>;
+/**
+ * The fixed head of the chain (SecretTargetNode recipe). Source handle only:
+ * people enter here. Plain element, no Base UI inside the node; the click that
+ * opens EmailAutomationEditor is handled by the canvas (`onNodeClick`).
+ */
+declare function TriggerNode({ data }: NodeProps<TriggerNodeType>): React.JSX.Element;
+
+type EmailStepNodeType = Node<{
+    data: EmailStepNodeData;
+}>;
+/**
+ * 200px card (SceneNode recipe): subject bold, "sent N" muted. An orphan (not
+ * reachable from the trigger, so it never sends) is the dashed, faded variant
+ * with a caption. Plain elements only: Base UI menus/popovers do not work
+ * inside React Flow nodes; clicks and context menus are handled by the canvas.
+ */
+declare function EmailStepNode({ data }: NodeProps<EmailStepNodeType>): React.JSX.Element;
+
+type DelayEdgeType = Edge<DelayEdgeData>;
+/**
+ * ClueEdge recipe: a bezier with a label chip at its midpoint. The chip shows
+ * the target step's delay and opens that step's editor. It is a plain
+ * <button>: Base UI popovers do not work inside the React Flow canvas.
+ */
+declare function DelayEdge({ id, sourceX, sourceY, targetX, targetY, sourcePosition, targetPosition, label, data, }: EdgeProps<DelayEdgeType>): React.JSX.Element;
+
+type UnsubscribeScope = "automation" | "all";
+interface Props {
+    token: string;
+    scope: UnsubscribeScope;
+}
+declare function EmailUnsubscribe({ token, scope }: Props): React.JSX.Element;
+
+/** A new step: the provider always sets `automationId` and, when absent, a fresh `id`. */
+type EmailAutomationStepCreateInput = Omit<EmailAutomationStepInput, "id" | "automationId"> & {
+    id?: string;
+    automationId?: string;
+};
+/** A step update: the provider always sets `automationId`. */
+type EmailAutomationStepUpdateInput = Omit<EmailAutomationStepInput, "automationId"> & {
+    automationId?: string;
+};
+interface EmailAutomationContextType {
+    automation: EmailAutomationInterface | undefined;
+    steps: EmailAutomationStepInterface[];
+    reload: () => Promise<void>;
+    selectedStepId: string | null;
+    select: (id: string | null) => void;
+    createStep: (input: EmailAutomationStepCreateInput) => Promise<EmailAutomationStepInterface>;
+    updateStep: (input: EmailAutomationStepUpdateInput) => Promise<EmailAutomationStepInterface>;
+    deleteStep: (id: string) => Promise<void>;
+    setNext: (stepId: string, nextStepId: string | null) => Promise<void>;
+    updatePosition: (stepId: string, x: number, y: number) => Promise<void>;
+    tidy: () => Promise<void>;
+    triggers: EmailAutomationTriggerInterface[];
+}
+type EmailAutomationProviderProps = {
+    automationId: string;
+    children: ReactNode;
+};
+declare const EmailAutomationProvider: ({ automationId, children }: EmailAutomationProviderProps) => React.JSX.Element;
+declare const useEmailAutomation: () => EmailAutomationContextType;
+
+declare function CanvasToolbar({ onTidy }: {
+    onTidy: () => void | Promise<void>;
+}): React.JSX.Element;
+
+declare function EmptyCanvas({ children }: {
+    children: ReactNode;
+}): React.JSX.Element;
+
+type LayoutNode = {
+    id: string;
+    /** node body dimensions in canvas px — used by dagre to allocate space */
+    width: number;
+    height: number;
+    /** if true, dagre leaves position alone and uses these (x, y) verbatim */
+    manuallyPositioned: boolean;
+    x?: number;
+    y?: number;
+};
+type LayoutEdge = {
+    source: string;
+    target: string;
+};
+type LayoutResult = Record<string, {
+    x: number;
+    y: number;
+}>;
+/**
+ * Deterministic LR layout. Pinned nodes keep their (x, y). Unpinned nodes
+ * are laid out by dagre and returned in the result map.
+ */
+declare function autoLayout(nodes: LayoutNode[], edges: LayoutEdge[]): LayoutResult;
+
+declare const LONG_PRESS_MS = 500;
+declare const LONG_PRESS_MOVE_TOLERANCE_PX = 10;
+/**
+ * Touch long-press detector for canvas nodes. A finger held still for
+ * LONG_PRESS_MS on a node fires `onLongPress` with the press point; any move
+ * beyond the tolerance (a pan or a node drag), a lift or a cancel aborts it.
+ * After a fired press, `consumeClick()` returns true once, so the caller can
+ * swallow the click that the finger lift produces.
+ */
+declare function createLongPressTracker(params: {
+    onLongPress: (press: {
+        target: string;
+        clientX: number;
+        clientY: number;
+    }) => void;
+    delayMs?: number;
+    moveTolerancePx?: number;
+    setTimer?: (fn: () => void, ms: number) => unknown;
+    clearTimer?: (handle: unknown) => void;
+}): {
+    down(target: string, clientX: number, clientY: number): void;
+    move(clientX: number, clientY: number): void;
+    up: () => void;
+    cancel: () => void;
+    consumeClick(): boolean;
+};
+
+/**
+ * `context.triggerLabels` maps a trigger key to the label the API declares for
+ * it (EmailAutomationsList loads them). A key the app no longer declares falls
+ * back to the raw key, so a stale automation stays readable.
+ */
+declare const useEmailAutomationTableStructure: UseTableStructureHook<EmailAutomationInterface, EmailAutomationFields>;
+
+declare const useEmailAutomationEnrollmentTableStructure: UseTableStructureHook<EmailAutomationEnrollmentInterface, EmailAutomationEnrollmentFields>;
+
+export { type CanvasGraph, type CanvasStep, CanvasToolbar, DelayEdge, type DelayEdgeData, EmailAutomationActiveSwitch, EmailAutomationCanvas, EmailAutomationCanvasInspector, EmailAutomationCanvasTab, EmailAutomationContainer, type EmailAutomationContainerProps, type EmailAutomationContextType, EmailAutomationEditor, type EmailAutomationEditorProps, EmailAutomationProvider, type EmailAutomationProviderProps, EmailAutomationRecipientsList, type EmailAutomationStepCreateInput, type EmailAutomationStepUpdateInput, EmailAutomationsList, EmailAutomationsListContainer, EmailStepEditor, type EmailStepEditorProps, EmailStepNode, type EmailStepNodeData, EmailUnsubscribe, EmptyCanvas, LONG_PRESS_MOVE_TOLERANCE_PX, LONG_PRESS_MS, type LayoutEdge, type LayoutNode, type LayoutResult, STEP_NODE_HEIGHT, STEP_NODE_PREFIX, STEP_NODE_WIDTH, STEP_SOURCE_HANDLE_PREFIX, STEP_TARGET_HANDLE_PREFIX, TRIGGER_NODE_HEIGHT, TRIGGER_NODE_ID, TRIGGER_NODE_WIDTH, TRIGGER_SOURCE_HANDLE, TriggerNode, type TriggerNodeData, autoLayout, buildCanvasGraph, createLongPressTracker, findHeadStepId, useEmailAutomation, useEmailAutomationEnrollmentTableStructure, useEmailAutomationTableStructure, useUserClosedGuard };

package/dist/email-automations/index.d.ts

@@ -0,0 +1,303 @@
+import * as React from 'react';
+import { ReactNode } from 'react';
+import { a as EmailAutomationInterface, c as EmailAutomationStepInterface, b as EmailAutomationStepInput, f as EmailAutomationTriggerInterface, g as EmailAutomationFields, e as EmailAutomationEnrollmentInterface, h as EmailAutomationEnrollmentFields } from '../email-automation-enrollment.fields-Cp3VMzFq.js';
+import { Node, Edge, NodeProps, EdgeProps } from '@xyflow/react';
+import { U as UseTableStructureHook } from '../types-l8SFleXi.js';
+import '../ApiDataInterface-BcZeXy5X.js';
+import '@tanstack/react-table';
+import '../types-bsm8Fp55.js';
+import 'lucide-react';
+import '../ApiRequestDataTypeInterface-CYEcRUrh.js';
+import '../useDataListRetriever-WEXL4bqB.js';
+
+/**
+ * Page container for the administrative email-automation list.
+ *
+ * Client component by necessity: `module={Modules.EmailAutomation}` is a
+ * registry entry carrying an icon component and methods, which a Server
+ * Component cannot pass across the boundary. Routes mount this container
+ * instead — the same shape as every other list page.
+ *
+ * No `forceHeader`: ContentListTable draws its own header row with the title
+ * and the create action, exactly as the company and user list pages do.
+ */
+declare function EmailAutomationsListContainer(): React.JSX.Element;
+
+type EmailAutomationContainerProps = {
+    automationId: string;
+};
+declare function EmailAutomationContainer({ automationId }: EmailAutomationContainerProps): React.JSX.Element;
+
+type EmailAutomationsListProps = {
+    /**
+     * Pass this whenever the list is the page's own content inside a
+     * `RoundPageContainer fullWidth`. Without it ContentListTable wraps itself in
+     * `rounded-md border`, drawing a second bordered card inside the page's
+     * rounded shell.
+     */
+    fullWidth?: boolean;
+};
+declare function EmailAutomationsList({ fullWidth }?: EmailAutomationsListProps): React.JSX.Element;
+
+/**
+ * Read-only list of the people in this automation (owner decision 6: no row
+ * actions). Rendered inside a tab, so it keeps its own bordered card (no
+ * `fullWidth`), as PricesList does inside ProductContainer.
+ */
+declare function EmailAutomationRecipientsList(): React.JSX.Element;
+
+type EmailAutomationEditorProps = {
+    automation?: EmailAutomationInterface;
+    propagateChanges?: (automation: EmailAutomationInterface) => void;
+    onSuccess?: () => void | Promise<void>;
+    trigger?: ReactNode;
+    forceShow?: boolean;
+    onClose?: () => void;
+    dialogOpen?: boolean;
+    onDialogOpenChange?: (open: boolean) => void;
+};
+declare function EmailAutomationEditor(props: EmailAutomationEditorProps): React.JSX.Element;
+
+type EmailStepEditorProps = {
+    step?: EmailAutomationStepInterface;
+    automationId: string;
+    /** Canvas position for a step created from the editor. */
+    initialPosition?: {
+        x: number;
+        y: number;
+    };
+    /** The head step's delay counts from entering the automation, not from a previous email. */
+    isHead?: boolean;
+    trigger?: ReactNode;
+    forceShow?: boolean;
+    onClose?: () => void;
+    dialogOpen?: boolean;
+    onDialogOpenChange?: (open: boolean) => void;
+    onSuccess?: () => void | Promise<void>;
+};
+declare function EmailStepEditor(props: EmailStepEditorProps): React.JSX.Element;
+
+/**
+ * Inline on/off for the automation page header, so pausing never needs the
+ * editor sheet. Off holds every enrolment in place (spec § "Sending" 3).
+ */
+declare function EmailAutomationActiveSwitch(): React.JSX.Element | null;
+
+declare function EmailAutomationCanvasTab(): React.JSX.Element;
+
+declare function EmailAutomationCanvas(): React.JSX.Element;
+
+/**
+ * Mounts EmailStepEditor (the EditorSheet the step uses everywhere) on top of
+ * the canvas, driven by `selectedStepId` from EmailAutomationContext. Copy of
+ * the app's ScenarioCanvasInspector with one branch.
+ *
+ *  - We control open state via `forceShow + dialogOpen + onDialogOpenChange`.
+ *  - On `onSuccess` we reload the canvas.
+ *  - The step comes from the context's `steps` (already loaded for the
+ *    canvas), so there is no per-step fetch.
+ */
+declare function EmailAutomationCanvasInspector(): React.JSX.Element | null;
+/**
+ * Build an `onDialogOpenChange` callback that ignores the editor's
+ * initial `open=false` notification. `useEditorDialog` (the hook
+ * inside every EditorSheet) initialises `open` to `false`, then in
+ * an effect sets it to `dialogOpen` (true). The "open=false" effect
+ * fires synchronously on mount and would otherwise wipe our canvas
+ * selection before the editor ever paints.
+ */
+declare function useUserClosedGuard(onClose: () => void): (open: boolean) => void;
+
+declare const TRIGGER_NODE_ID = "trigger";
+declare const TRIGGER_SOURCE_HANDLE = "trigger-source";
+declare const STEP_NODE_PREFIX = "step:";
+declare const STEP_SOURCE_HANDLE_PREFIX = "step-source-";
+declare const STEP_TARGET_HANDLE_PREFIX = "step-target-";
+declare const TRIGGER_NODE_WIDTH = 200;
+declare const TRIGGER_NODE_HEIGHT = 56;
+declare const STEP_NODE_WIDTH = 200;
+declare const STEP_NODE_HEIGHT = 72;
+/**
+ * The fields the canvas reads from a step. `EmailAutomationStepInterface`
+ * satisfies it structurally; the narrow shape keeps this function pure and
+ * testable with plain objects.
+ */
+type CanvasStep = {
+    id: string;
+    subject: string;
+    delayHours: number;
+    positionX?: number;
+    positionY?: number;
+    sentCount: number;
+    next?: {
+        id: string;
+    };
+};
+type TriggerNodeData = {
+    label: string;
+};
+type EmailStepNodeData = {
+    stepId: string;
+    subject: string;
+    sentCount: number;
+    orphan: boolean;
+    manuallyPositioned: boolean;
+};
+type DelayEdgeData = {
+    targetStepId: string;
+    delayHours: number;
+};
+type CanvasGraph = {
+    nodes: Node[];
+    edges: Edge[];
+    orphanIds: string[];
+};
+/**
+ * The head is the oldest step with no incoming NEXT, exactly as the API picks
+ * it (`findHead`). `steps` arrive ordered by createdAt ASC from
+ * `findByAutomation`, so the first step nobody points at is the head.
+ */
+declare function findHeadStepId(steps: CanvasStep[]): string | null;
+/**
+ * Turns the automation's steps into React Flow nodes and edges: the trigger
+ * node, one node per step, a trigger→head edge, and one edge per NEXT link.
+ * Steps not reachable from the head (walking next→next) are orphans: they
+ * never send and render dashed.
+ */
+declare function buildCanvasGraph(steps: CanvasStep[], triggerLabel: string): CanvasGraph;
+
+type TriggerNodeType = Node<{
+    data: TriggerNodeData;
+}>;
+/**
+ * The fixed head of the chain (SecretTargetNode recipe). Source handle only:
+ * people enter here. Plain element, no Base UI inside the node; the click that
+ * opens EmailAutomationEditor is handled by the canvas (`onNodeClick`).
+ */
+declare function TriggerNode({ data }: NodeProps<TriggerNodeType>): React.JSX.Element;
+
+type EmailStepNodeType = Node<{
+    data: EmailStepNodeData;
+}>;
+/**
+ * 200px card (SceneNode recipe): subject bold, "sent N" muted. An orphan (not
+ * reachable from the trigger, so it never sends) is the dashed, faded variant
+ * with a caption. Plain elements only: Base UI menus/popovers do not work
+ * inside React Flow nodes; clicks and context menus are handled by the canvas.
+ */
+declare function EmailStepNode({ data }: NodeProps<EmailStepNodeType>): React.JSX.Element;
+
+type DelayEdgeType = Edge<DelayEdgeData>;
+/**
+ * ClueEdge recipe: a bezier with a label chip at its midpoint. The chip shows
+ * the target step's delay and opens that step's editor. It is a plain
+ * <button>: Base UI popovers do not work inside the React Flow canvas.
+ */
+declare function DelayEdge({ id, sourceX, sourceY, targetX, targetY, sourcePosition, targetPosition, label, data, }: EdgeProps<DelayEdgeType>): React.JSX.Element;
+
+type UnsubscribeScope = "automation" | "all";
+interface Props {
+    token: string;
+    scope: UnsubscribeScope;
+}
+declare function EmailUnsubscribe({ token, scope }: Props): React.JSX.Element;
+
+/** A new step: the provider always sets `automationId` and, when absent, a fresh `id`. */
+type EmailAutomationStepCreateInput = Omit<EmailAutomationStepInput, "id" | "automationId"> & {
+    id?: string;
+    automationId?: string;
+};
+/** A step update: the provider always sets `automationId`. */
+type EmailAutomationStepUpdateInput = Omit<EmailAutomationStepInput, "automationId"> & {
+    automationId?: string;
+};
+interface EmailAutomationContextType {
+    automation: EmailAutomationInterface | undefined;
+    steps: EmailAutomationStepInterface[];
+    reload: () => Promise<void>;
+    selectedStepId: string | null;
+    select: (id: string | null) => void;
+    createStep: (input: EmailAutomationStepCreateInput) => Promise<EmailAutomationStepInterface>;
+    updateStep: (input: EmailAutomationStepUpdateInput) => Promise<EmailAutomationStepInterface>;
+    deleteStep: (id: string) => Promise<void>;
+    setNext: (stepId: string, nextStepId: string | null) => Promise<void>;
+    updatePosition: (stepId: string, x: number, y: number) => Promise<void>;
+    tidy: () => Promise<void>;
+    triggers: EmailAutomationTriggerInterface[];
+}
+type EmailAutomationProviderProps = {
+    automationId: string;
+    children: ReactNode;
+};
+declare const EmailAutomationProvider: ({ automationId, children }: EmailAutomationProviderProps) => React.JSX.Element;
+declare const useEmailAutomation: () => EmailAutomationContextType;
+
+declare function CanvasToolbar({ onTidy }: {
+    onTidy: () => void | Promise<void>;
+}): React.JSX.Element;
+
+declare function EmptyCanvas({ children }: {
+    children: ReactNode;
+}): React.JSX.Element;
+
+type LayoutNode = {
+    id: string;
+    /** node body dimensions in canvas px — used by dagre to allocate space */
+    width: number;
+    height: number;
+    /** if true, dagre leaves position alone and uses these (x, y) verbatim */
+    manuallyPositioned: boolean;
+    x?: number;
+    y?: number;
+};
+type LayoutEdge = {
+    source: string;
+    target: string;
+};
+type LayoutResult = Record<string, {
+    x: number;
+    y: number;
+}>;
+/**
+ * Deterministic LR layout. Pinned nodes keep their (x, y). Unpinned nodes
+ * are laid out by dagre and returned in the result map.
+ */
+declare function autoLayout(nodes: LayoutNode[], edges: LayoutEdge[]): LayoutResult;
+
+declare const LONG_PRESS_MS = 500;
+declare const LONG_PRESS_MOVE_TOLERANCE_PX = 10;
+/**
+ * Touch long-press detector for canvas nodes. A finger held still for
+ * LONG_PRESS_MS on a node fires `onLongPress` with the press point; any move
+ * beyond the tolerance (a pan or a node drag), a lift or a cancel aborts it.
+ * After a fired press, `consumeClick()` returns true once, so the caller can
+ * swallow the click that the finger lift produces.
+ */
+declare function createLongPressTracker(params: {
+    onLongPress: (press: {
+        target: string;
+        clientX: number;
+        clientY: number;
+    }) => void;
+    delayMs?: number;
+    moveTolerancePx?: number;
+    setTimer?: (fn: () => void, ms: number) => unknown;
+    clearTimer?: (handle: unknown) => void;
+}): {
+    down(target: string, clientX: number, clientY: number): void;
+    move(clientX: number, clientY: number): void;
+    up: () => void;
+    cancel: () => void;
+    consumeClick(): boolean;
+};
+
+/**
+ * `context.triggerLabels` maps a trigger key to the label the API declares for
+ * it (EmailAutomationsList loads them). A key the app no longer declares falls
+ * back to the raw key, so a stale automation stays readable.
+ */
+declare const useEmailAutomationTableStructure: UseTableStructureHook<EmailAutomationInterface, EmailAutomationFields>;
+
+declare const useEmailAutomationEnrollmentTableStructure: UseTableStructureHook<EmailAutomationEnrollmentInterface, EmailAutomationEnrollmentFields>;
+
+export { type CanvasGraph, type CanvasStep, CanvasToolbar, DelayEdge, type DelayEdgeData, EmailAutomationActiveSwitch, EmailAutomationCanvas, EmailAutomationCanvasInspector, EmailAutomationCanvasTab, EmailAutomationContainer, type EmailAutomationContainerProps, type EmailAutomationContextType, EmailAutomationEditor, type EmailAutomationEditorProps, EmailAutomationProvider, type EmailAutomationProviderProps, EmailAutomationRecipientsList, type EmailAutomationStepCreateInput, type EmailAutomationStepUpdateInput, EmailAutomationsList, EmailAutomationsListContainer, EmailStepEditor, type EmailStepEditorProps, EmailStepNode, type EmailStepNodeData, EmailUnsubscribe, EmptyCanvas, LONG_PRESS_MOVE_TOLERANCE_PX, LONG_PRESS_MS, type LayoutEdge, type LayoutNode, type LayoutResult, STEP_NODE_HEIGHT, STEP_NODE_PREFIX, STEP_NODE_WIDTH, STEP_SOURCE_HANDLE_PREFIX, STEP_TARGET_HANDLE_PREFIX, TRIGGER_NODE_HEIGHT, TRIGGER_NODE_ID, TRIGGER_NODE_WIDTH, TRIGGER_SOURCE_HANDLE, TriggerNode, type TriggerNodeData, autoLayout, buildCanvasGraph, createLongPressTracker, findHeadStepId, useEmailAutomation, useEmailAutomationEnrollmentTableStructure, useEmailAutomationTableStructure, useUserClosedGuard };