@uipath/maestro-builder-sdk 6.8.5 → 6.8.6

package/dist/core/typed-raw-node.d.ts

@@ -0,0 +1,97 @@
+/**
+ * Internal: what `check` and `compile` say about a `rawNode` for a node type
+ * the SDK has a typed factory for, and the Data Fabric input keys it may carry.
+ * Not re-exported from the package entry point.
+ */
+/** The factory to use for one node type, and the versions of it the SDK bundles. */
+export interface TypedFactory {
+    /** The typed spelling, as the refusal names it. */
+    factory: string;
+    /**
+     * Every `<version>` with a `<nodeType>@<version>` entry in `core-definitions.json`.
+     * Listed here rather than read from the file because this module sits under
+     * `node-classes.ts`, which must not import `node:*`; `raw-node-typed-family.test.ts`
+     * pins the two equal.
+     */
+    bundled: readonly string[];
+}
+/**
+ * Every node type the SDK authors as a STEP through a typed factory, with the
+ * factory to use. `raw-node-typed-family.test.ts` pins the key set to the
+ * `flow-coverage.json` rows with `support: 'typed'` and a `bundledKey`, so a
+ * family that gains a factory gains its row here too.
+ *
+ * Two groups of typed rows are left out, because neither is ever a step:
+ * triggers (`core.trigger.*`, placed by `.trigger()`) and agent resources
+ * (`uipath.agent.resource.*`, attached to an agent). `decompile` keeps an
+ * orphaned one as a `rawNode`, and a warning on that round trip would be noise.
+ *
+ * The Data Fabric verbs name their options, because the query and write keys
+ * an author reaches for by hand (`_filters`, `_sort`, `fieldValues`, …) each
+ * have a typed spelling.
+ */
+export declare const TYPED_FACTORIES: Readonly<Record<string, TypedFactory>>;
+/**
+ * Every `entityConfig` key the product reads or persists on a Data Fabric node,
+ * across the four verbs. flow-workbench develop `eed682f19`:
+ *
+ * - services `serialization/entity-vdo.ts` `interface EntityConfig` (:229-272):
+ *   `entityName`, `resultMode`, `_recordLimit`, `_skip`, `_sort`,
+ *   `_selectedFieldNames`, `_filters`, `_entityFields`, `_relatedFields`,
+ *   `_folderKey`, `_entityKey`, `_resourceKey`, `_outputSchema`;
+ *   `CreateEntityConfig` (:719) adds `fieldValues`; `UpdateEntityConfig` (:744)
+ *   adds `recordSource`, `readEntityNodeId`, `recordId`, `fieldUpdates`.
+ * - canvas `properties-panel/EntityConfigField.tsx` `EntityConfigInputs`
+ *   (:85-110) and `entity/useEntityPanelState.ts` `EntitySelectionPatch`
+ *   (:248-270), which the panels persist on an entity pick:
+ *   `_entityDisplayName`, `_choiceSets`, `_folderPath`, `_entitySubType`.
+ * - Create/Update/DeleteEntityConfigField.tsx declare nothing beyond these.
+ *
+ * One union rather than one set per verb: a key another verb reads is at worst
+ * ignored, and a per-verb split would refuse a canvas-written key on a verb
+ * whose panel happens not to declare it. The test pins every key the typed
+ * factories write to this set.
+ */
+export declare const DATAFABRIC_ENTITY_CONFIG_KEYS: ReadonlySet<string>;
+/**
+ * A reminder, as a `warning`, that a `rawNode` stands in for a typed factory,
+ * or `undefined` for a type with no factory.
+ *
+ * A warning and never an error: a factory does not always write every input its
+ * node reads (the Data Fabric verbs do not write `_entityFields`, which a
+ * related-path filter needs), and nothing checks factory coverage family by
+ * family. So the raw node keeps compiling at every version. The one failure
+ * the eval archive measured, an invented key the node never reads, is refused
+ * by {@link dataFabricUnknownInputs} instead.
+ *
+ * @param nodeType - The definition's `nodeType`, as passed to `rawNode`.
+ * @returns The warning, or `undefined` for a type with no typed factory.
+ */
+export declare function typedFamilyRawNodeWarning(nodeType: string): string | undefined;
+/**
+ * Why a `core.datafabric.*` node's inputs carry a key the product never reads,
+ * or `undefined` when they do not.
+ *
+ * This is where the eval failure became possible. A raw node renders its inputs
+ * verbatim, and `core.datafabric.read@1.4`'s registry definition declares only
+ * `entityName` and `resultMode`, so `validate` cannot see any other key. Measured
+ * on the eval archive (2026-09-23, skill-flow-datafabric-native-contract-intake-pipeline):
+ * the agent wrote `_sortOptions: [{ fieldName, isDescending }]` in place of
+ * `_sort`, `check` printed "no issues", `validate` said Valid, and the query
+ * would have run unsorted. The allowed set is what the product reads
+ * ({@link DATAFABRIC_ENTITY_CONFIG_KEYS}), so `_entityFields` and the other
+ * canvas snapshots stay legal.
+ *
+ * Severity follows the version: at a bundled `<nodeType>@<version>` the key set
+ * is known, so the key is refused (`error`); at a version this SDK has not
+ * synced, a newer node could read a new key, so it is reported (`warning`).
+ *
+ * @param nodeType - The node's type.
+ * @param version - The version the node is emitted at.
+ * @param inputs - The node's inputs, before rendering.
+ * @returns The diagnostic, or `undefined` for a clean node or a non-Data-Fabric type.
+ */
+export declare function dataFabricUnknownInputs(nodeType: string, version: string, inputs: unknown): {
+    severity: 'error' | 'warning';
+    message: string;
+} | undefined;

package/dist/core/typed-raw-node.js

@@ -0,0 +1,199 @@
+/**
+ * Internal: what `check` and `compile` say about a `rawNode` for a node type
+ * the SDK has a typed factory for, and the Data Fabric input keys it may carry.
+ * Not re-exported from the package entry point.
+ */
+/**
+ * Every node type the SDK authors as a STEP through a typed factory, with the
+ * factory to use. `raw-node-typed-family.test.ts` pins the key set to the
+ * `flow-coverage.json` rows with `support: 'typed'` and a `bundledKey`, so a
+ * family that gains a factory gains its row here too.
+ *
+ * Two groups of typed rows are left out, because neither is ever a step:
+ * triggers (`core.trigger.*`, placed by `.trigger()`) and agent resources
+ * (`uipath.agent.resource.*`, attached to an agent). `decompile` keeps an
+ * orphaned one as a `rawNode`, and a warning on that round trip would be noise.
+ *
+ * The Data Fabric verbs name their options, because the query and write keys
+ * an author reaches for by hand (`_filters`, `_sort`, `fieldValues`, …) each
+ * have a typed spelling.
+ */
+export const TYPED_FACTORIES = {
+    'core.action.http': { factory: 'http({ managed: false })', bundled: ['1.0.0'] },
+    'core.action.http.v2': { factory: 'http({ managed: true })', bundled: ['2.3'] },
+    'core.action.queue.create': { factory: 'queueItem()', bundled: ['1.2'] },
+    'core.action.queue.create-and-wait': { factory: 'queueItem({ wait: true })', bundled: ['1.2'] },
+    'core.action.script': { factory: 'script()', bundled: ['1.0.0', '1.1'] },
+    'core.action.transform': { factory: 'transform()', bundled: ['1.0.0', '1.1'] },
+    'core.action.transform.filter': { factory: "transform({ variant: 'filter' })", bundled: ['1.0.0', '1.1'] },
+    'core.action.transform.group-by': { factory: "transform({ variant: 'group-by' })", bundled: ['1.0.0', '1.1'] },
+    'core.action.transform.map': { factory: "transform({ variant: 'map' })", bundled: ['1.0.0', '1.1'] },
+    'core.control.end': { factory: '.return()', bundled: ['1.0.0', '1.0'] },
+    'core.datafabric.read': {
+        factory: "dataFabricRead({ entity, resultMode: 'single' | 'multiple', filters: [{ field, operator, value, or }], "
+            + 'sort: { field, direction }, limit, skip, fields, folderKey })',
+        bundled: ['1.0', '1.4'],
+    },
+    'core.datafabric.create': {
+        factory: 'dataFabricCreate({ entity, values: { <field>: <value> }, folderKey })',
+        bundled: ['1.3'],
+    },
+    'core.datafabric.update': {
+        factory: 'dataFabricUpdate({ entity, record: { byId } | { fromRead }, set: { <field>: <value> }, folderKey })',
+        bundled: ['1.0', '1.3'],
+    },
+    'core.datafabric.delete': {
+        factory: 'dataFabricDelete({ entity, record: { byId } | { fromRead }, folderKey })',
+        bundled: ['1.3'],
+    },
+    'core.logic.decision': { factory: '.branch()', bundled: ['1.0.0', '1.3'] },
+    'core.logic.delay': { factory: 'delay({ duration })', bundled: ['1.0.0', '1.0'] },
+    'core.logic.dowhile': { factory: '.doWhile(name, condition, body, { limit, breakEnabled })', bundled: ['1.0'] },
+    'core.logic.loop': { factory: '.loop()', bundled: ['1.0.0', '2.4'] },
+    'core.logic.merge': { factory: '.parallel() rejoin', bundled: ['1.0.0', '1.0'] },
+    'core.logic.mock': { factory: 'mock()', bundled: ['1.0.0', '1.0'] },
+    'core.logic.switch': { factory: '.switch()', bundled: ['1.0.0', '1.1'] },
+    'core.logic.terminate': { factory: '.terminate()', bundled: ['1.0.0', '1.0'] },
+    'core.subflow': { factory: 'subflow(child, inputs)', bundled: ['1.0.0', '1.0'] },
+    'uipath.agent.conversational': { factory: 'conversationalAgent()', bundled: ['1.6', '1.7'] },
+    'uipath.agent.voice': { factory: 'voiceAgent()', bundled: ['1.0', '1.1'] },
+    'uipath.conversational.get-conversation-context': { factory: 'conversationContext()', bundled: ['1.0'] },
+    'uipath.conversational.send-message': { factory: 'sendMessage()', bundled: ['1.0', '1.1'] },
+    'uipath.conversational.voice.create-outgoing-call': { factory: 'createOutgoingCall()', bundled: ['1.0'] },
+    'uipath.conversational.voice.end-call': { factory: 'endCall()', bundled: ['1.0'] },
+    'uipath.conversational.wait-for-message': { factory: 'waitForMessage()', bundled: ['1.0', '1.1'] },
+    'uipath.document.classify': { factory: 'documentClassify()', bundled: ['1.0'] },
+    'uipath.human-in-the-loop': { factory: 'hitl()', bundled: ['1.0', '1.1', '1.2'] },
+    'uipath.human-in-the-loop.coded-action-app': {
+        factory: "hitl({ variant: 'action-app' })",
+        bundled: ['1.0', '1.1'],
+    },
+    'uipath.human-in-the-loop.document-validation': {
+        factory: "hitl({ variant: 'document-validation' })",
+        bundled: ['1.0'],
+    },
+    'uipath.human-in-the-loop.quick-form': { factory: "hitl({ variant: 'quick-form' })", bundled: ['1.0', '1.1'] },
+    'uipath.pattern.batch-transform': { factory: 'batchTransform()', bundled: ['1.0'] },
+    'uipath.pattern.deep-rag': { factory: 'summarize()', bundled: ['1.0'] },
+    'uipath.ixp.extract-document-builder': { factory: 'dynamicExtract()', bundled: ['1.0.0'] },
+};
+/**
+ * Every `entityConfig` key the product reads or persists on a Data Fabric node,
+ * across the four verbs. flow-workbench develop `eed682f19`:
+ *
+ * - services `serialization/entity-vdo.ts` `interface EntityConfig` (:229-272):
+ *   `entityName`, `resultMode`, `_recordLimit`, `_skip`, `_sort`,
+ *   `_selectedFieldNames`, `_filters`, `_entityFields`, `_relatedFields`,
+ *   `_folderKey`, `_entityKey`, `_resourceKey`, `_outputSchema`;
+ *   `CreateEntityConfig` (:719) adds `fieldValues`; `UpdateEntityConfig` (:744)
+ *   adds `recordSource`, `readEntityNodeId`, `recordId`, `fieldUpdates`.
+ * - canvas `properties-panel/EntityConfigField.tsx` `EntityConfigInputs`
+ *   (:85-110) and `entity/useEntityPanelState.ts` `EntitySelectionPatch`
+ *   (:248-270), which the panels persist on an entity pick:
+ *   `_entityDisplayName`, `_choiceSets`, `_folderPath`, `_entitySubType`.
+ * - Create/Update/DeleteEntityConfigField.tsx declare nothing beyond these.
+ *
+ * One union rather than one set per verb: a key another verb reads is at worst
+ * ignored, and a per-verb split would refuse a canvas-written key on a verb
+ * whose panel happens not to declare it. The test pins every key the typed
+ * factories write to this set.
+ */
+export const DATAFABRIC_ENTITY_CONFIG_KEYS = new Set([
+    'entityName', 'resultMode',
+    '_recordLimit', '_skip', '_sort', '_selectedFieldNames', '_filters',
+    '_entityFields', '_relatedFields', '_choiceSets', '_outputSchema',
+    '_folderKey', '_folderPath', '_entityKey', '_resourceKey', '_entityDisplayName', '_entitySubType',
+    'fieldValues', 'fieldUpdates', 'recordSource', 'readEntityNodeId', 'recordId',
+]);
+/**
+ * What the Data Fabric factories write, and what they do not, as the typed-family
+ * warning states it. The factories do not author the canvas's column snapshots,
+ * so a related-path filter (`customer.Name`) still needs a raw node carrying
+ * `_entityFields` (core/actions.ts `DataFabricFilter.field`).
+ */
+const DATAFABRIC_HINT = ' The factory writes the query and write keys: `filters` becomes `_filters` (flat rows; `or: true` '
+    + 'starts each OR alternative), `sort` is `_sort`, `limit`/`skip`/`fields` are '
+    + '`_recordLimit`/`_skip`/`_selectedFieldNames`, `values`/`set` are `fieldValues`/`fieldUpdates`, '
+    + 'and `record` is `recordSource`. It does not write the column snapshots `_entityFields`, '
+    + '`_relatedFields`, `_choiceSets` or `_outputSchema`; a related-path filter such as '
+    + '`customer.Name` needs `_entityFields`, so for that a raw node is still the way.';
+/**
+ * A reminder, as a `warning`, that a `rawNode` stands in for a typed factory,
+ * or `undefined` for a type with no factory.
+ *
+ * A warning and never an error: a factory does not always write every input its
+ * node reads (the Data Fabric verbs do not write `_entityFields`, which a
+ * related-path filter needs), and nothing checks factory coverage family by
+ * family. So the raw node keeps compiling at every version. The one failure
+ * the eval archive measured, an invented key the node never reads, is refused
+ * by {@link dataFabricUnknownInputs} instead.
+ *
+ * @param nodeType - The definition's `nodeType`, as passed to `rawNode`.
+ * @returns The warning, or `undefined` for a type with no typed factory.
+ */
+export function typedFamilyRawNodeWarning(nodeType) {
+    if (typeof nodeType !== 'string')
+        return undefined;
+    const entry = TYPED_FACTORIES[nodeType];
+    if (entry === undefined)
+        return undefined;
+    const hint = nodeType.startsWith('core.datafabric.') ? DATAFABRIC_HINT : '';
+    return `rawNode("${nodeType}"): this SDK has a typed factory, ${entry.factory}. A raw node keeps its `
+        + `inputs verbatim, and \`validate\` cannot see a key the registry definition does not declare, so a `
+        + `misspelled input compiles and is ignored at run time. Prefer the factory unless you need an input it `
+        + `does not write.${hint}`;
+}
+const isPlainObject = (v) => typeof v === 'object' && v !== null && !Array.isArray(v) && Object.getPrototypeOf(v) === Object.prototype;
+/**
+ * Why a `core.datafabric.*` node's inputs carry a key the product never reads,
+ * or `undefined` when they do not.
+ *
+ * This is where the eval failure became possible. A raw node renders its inputs
+ * verbatim, and `core.datafabric.read@1.4`'s registry definition declares only
+ * `entityName` and `resultMode`, so `validate` cannot see any other key. Measured
+ * on the eval archive (2026-09-23, skill-flow-datafabric-native-contract-intake-pipeline):
+ * the agent wrote `_sortOptions: [{ fieldName, isDescending }]` in place of
+ * `_sort`, `check` printed "no issues", `validate` said Valid, and the query
+ * would have run unsorted. The allowed set is what the product reads
+ * ({@link DATAFABRIC_ENTITY_CONFIG_KEYS}), so `_entityFields` and the other
+ * canvas snapshots stay legal.
+ *
+ * Severity follows the version: at a bundled `<nodeType>@<version>` the key set
+ * is known, so the key is refused (`error`); at a version this SDK has not
+ * synced, a newer node could read a new key, so it is reported (`warning`).
+ *
+ * @param nodeType - The node's type.
+ * @param version - The version the node is emitted at.
+ * @param inputs - The node's inputs, before rendering.
+ * @returns The diagnostic, or `undefined` for a clean node or a non-Data-Fabric type.
+ */
+export function dataFabricUnknownInputs(nodeType, version, inputs) {
+    if (typeof nodeType !== 'string' || !nodeType.startsWith('core.datafabric.'))
+        return undefined;
+    if (!isPlainObject(inputs))
+        return undefined;
+    const unknown = Object.keys(inputs).filter((k) => k !== 'entityConfig');
+    const cfg = inputs.entityConfig;
+    if (isPlainObject(cfg)) {
+        for (const k of Object.keys(cfg))
+            if (!DATAFABRIC_ENTITY_CONFIG_KEYS.has(k))
+                unknown.push(`entityConfig.${k}`);
+    }
+    if (unknown.length === 0)
+        return undefined;
+    const bundled = TYPED_FACTORIES[nodeType]?.bundled.includes(version) ?? false;
+    const named = unknown.map((k) => `\`${k}\``).join(', ');
+    const factory = TYPED_FACTORIES[nodeType]?.factory;
+    const base = `${nodeType}@${version} carries ${named}, which the platform never reads: Data Fabric `
+        + `nodes read only \`inputs.entityConfig\`, with the keys ${[...DATAFABRIC_ENTITY_CONFIG_KEYS].join(', ')} `
+        + `(flow-workbench entity-vdo.ts \`EntityConfig\` and the entity panels). \`validate\` cannot see `
+        + `the key, so it compiles and is ignored at run time; for example a sort is \`_sort: { field, direction }\`, `
+        + `not \`_sortOptions\`.${factory ? ` The typed factory, ${factory}, writes only keys the node reads.` : ''}`;
+    if (bundled)
+        return { severity: 'error', message: base };
+    return {
+        severity: 'warning',
+        message: `${base} This SDK does not bundle ${nodeType}@${version}, so a newer node may read the key; `
+            + 'it compiles as written.',
+    };
+}

package/dist/registry/library-build/build.js

@@ -15,6 +15,7 @@ import { pyStr } from "../compat/pystr.js";
 import { mapConcurrent } from "../concurrency.js";
 import { Refusal, messageOf } from "../errors.js";
 import { registrySearchConnectors } from "../uip/commands.js";
+import { failureReason } from "../uip/envelope.js";
 import { applyCuratedOverrides, extractCanonical, filterNodeTypesByTier, mergeConnectorRecord, nodeOf, scopedConnectorKey, selectPublishedConnectors, } from "./canonical.js";
 import { SEARCH_RESULTS_NAME, createBuildContext, isConnectorGet, registryCacheName, registryGet, } from "./context.js";
 import { enrichAll } from "./enrich.js";
@@ -53,7 +54,7 @@ export async function registrySearch(ctx) {
         ctx.reporter.info("Running registry search...");
         const result = await ctx.client.run(registrySearchConnectors(), ctx.timeoutMs === undefined ? undefined : { timeoutMs: ctx.timeoutMs });
         if (result.code !== 0)
-            throw new Refusal(`Registry search failed: ${result.stderr}`, "REGISTRY_SEARCH_FAILED");
+            throw new Refusal(`Registry search failed: ${failureReason(result)}`, "REGISTRY_SEARCH_FAILED");
         ctx.caches.registry.write(SEARCH_RESULTS_NAME, undefined, result.stdout);
     }
     const data = ctx.caches.registry.read(SEARCH_RESULTS_NAME);

package/dist/registry/library-build/context.d.ts

@@ -60,6 +60,32 @@ export declare function registryCacheName(nodeType: string): string;
 export declare const SEARCH_RESULTS_NAME = "_search_results.json";
 /** `json.dump(payload, f)`: cache bytes shaped as Python wrote them. */
 export declare function writeCache(cache: ResponseCache, name: string, payload: unknown): void;
+/** A `registry get` that did not answer with the node, and why. */
+export interface RegistryMiss {
+    nodeType: string;
+    /** The CLI's own reason ({@link failureReason}); never empty. */
+    reason: string;
+    /**
+     * True only for the CLI's "Node not found" answer — the node is absent. False
+     * for every failure of the LOOKUP (an error, a refusal, a timeout), which says
+     * nothing about whether the node exists.
+     */
+    notFound: boolean;
+}
+/** {@link registryProbe}'s answer: the cache name of the reply, or the miss. */
+export type RegistryProbe = {
+    name: string;
+} | {
+    miss: RegistryMiss;
+};
+/**
+ * Cached `uip maestro flow registry get <nodeType>`, reporting nothing.
+ *
+ * The caller gets the miss with its reason and decides what to say — a caller
+ * probing which namespace an operation lives in puts every probe's reason into
+ * one refusal instead of a WARN per probe.
+ */
+export declare function registryProbe(ctx: BuildContext, nodeType: string): Promise<RegistryProbe>;
 /**
  * `registry_get`: cached `uip maestro flow registry get <nodeType>`.
  *

package/dist/registry/library-build/context.js

@@ -18,7 +18,7 @@ import { pyJsonStringify } from "../codecs/pyjson.js";
 import { sortedByKeys } from "../compat/compare.js";
 import { isConnectorsMetadata, isResourcesDescribeObject, isResourcesDescribeOperation, isResourcesList as isResourcesListArgv, registryGet as registryGetArgv, } from "../uip/commands.js";
 import { CACHED_FAILURE, isCachedFailure, safeCacheName } from "../uip/response-cache.js";
-import { pyStrip } from "../compat/pystr.js";
+import { failureReason, isNodeNotFound } from "../uip/envelope.js";
 import { get, isRecord, pyOr, truthy } from "./py.js";
 export function createBuildContext(ports, scope = {}) {
     const parentFields = scope.parentFields instanceof Map
@@ -116,25 +116,38 @@ function envelope(payload) {
     return payload;
 }
 /**
- * `registry_get`: cached `uip maestro flow registry get <nodeType>`.
+ * Cached `uip maestro flow registry get <nodeType>`, reporting nothing.
  *
- * Returns the cache name the raw stdout lives under, or `undefined` when the
- * call failed. `quiet` suppresses the failure WARN — for a caller probing which
- * of several node-type namespaces an action lives in, where a miss is an
- * expected answer rather than a problem to report.
+ * The caller gets the miss with its reason and decides what to say — a caller
+ * probing which namespace an operation lives in puts every probe's reason into
+ * one refusal instead of a WARN per probe.
  */
-export async function registryGet(ctx, nodeType, quiet = false) {
+export async function registryProbe(ctx, nodeType) {
     const name = registryCacheName(nodeType);
     if (ctx.caches.registry.has(name))
-        return name;
+        return { name };
     const result = await runUip(ctx, registryGetArgv(nodeType, ctx.connectionId));
     if (result.code !== 0) {
-        if (!quiet)
-            ctx.reporter.warn(`  WARN: registry get failed for ${nodeType}: ${pyStrip(result.stderr)}`);
-        return undefined;
+        return { miss: { nodeType, reason: failureReason(result), notFound: isNodeNotFound(result) } };
     }
     ctx.caches.registry.write(name, undefined, result.stdout);
-    return name;
+    return { name };
+}
+/**
+ * `registry_get`: cached `uip maestro flow registry get <nodeType>`.
+ *
+ * Returns the cache name the raw stdout lives under, or `undefined` when the
+ * call failed. `quiet` suppresses the failure WARN — for a caller probing which
+ * of several node-type namespaces an action lives in, where a miss is an
+ * expected answer rather than a problem to report.
+ */
+export async function registryGet(ctx, nodeType, quiet = false) {
+    const probe = await registryProbe(ctx, nodeType);
+    if ("name" in probe)
+        return probe.name;
+    if (!quiet)
+        ctx.reporter.warn(`  WARN: registry get failed for ${nodeType}: ${probe.miss.reason}`);
+    return undefined;
 }
 function noteFailedFieldDescribe(ctx, connectorKey, objectName, operation, message) {
     if (ctx.parentFields.size > 0) {

package/dist/registry/library-build/events.js

@@ -18,6 +18,7 @@ import { lowerFirst, pyStr, pyStrip, startsWithUpper } from "../compat/pystr.js"
 import { mapConcurrent } from "../concurrency.js";
 import { Refusal } from "../errors.js";
 import { isTriggersDescribe, isTriggersObjects } from "../uip/commands.js";
+import { failureReason } from "../uip/envelope.js";
 import { safeCacheName } from "../uip/response-cache.js";
 import { schemaCacheScope, writeCache } from "./context.js";
 import { objectsComeFromTheConnection } from "./generic-expand.js";
@@ -66,8 +67,8 @@ async function runJson(client, argv, timeoutMs) {
         payload = JSON.parse(result.stdout);
     }
     catch {
-        const text = codePointSlice(pyStrip(result.stderr || result.stdout), 0, 300);
-        throw new EventDiscoveryError(`${head} did not answer JSON: ${text || "no output"}`, result.refused === true);
+        const text = codePointSlice(failureReason(result), 0, 300);
+        throw new EventDiscoveryError(`${head} did not answer JSON: ${text}`, result.refused === true);
     }
     if (get(payload, "Result") !== "Success") {
         // `refused` is carried here too, although the refusing client in this tree

package/dist/registry/prepare/actions.d.ts

@@ -5,7 +5,8 @@ import type { UipClient } from "../uip/client.js";
  * Exact prefix only: the same search returns
  * `uipath.agent.resource.tool.connector.<key>.<action>` and
  * `uipath.connector.trigger.<key>.<event>`, which are not actions of this node
- * and would read as alternatives an author could pass.
+ * and would read as alternatives an author could pass as an action. The events
+ * are listed separately, by {@link registryEventIds}.
  */
 export declare function registryActionIds(payload: unknown, connectorKey: string): string[];
 /**
@@ -19,8 +20,44 @@ export declare function registryActionIds(payload: unknown, connectorKey: string
  */
 export declare function closestActions(action: string, candidates: readonly string[]): string[];
 /**
- * `_registry_actions`: the action ids the registry serves for `connectorKey`,
- * or `[]` when the search fails or does not answer JSON. This runs only on the
- * failure path, where an empty answer is itself the message ("returned nothing").
+ * {@link closestActions}, kept only where the candidate is plausibly what was
+ * meant: it shares MOST of the wanted id's words (`list-all-records` →
+ * `list-records`), or it is a near spelling (`record-creatd` → `record-created`,
+ * `send-mail` → `send-email`). One shared word is not enough: `record-created`
+ * shares "record" with every Data Fabric action, and offering
+ * `update-entity-record` as the closest match to an EVENT name points the
+ * author at the wrong namespace.
  */
-export declare function registryActions(client: UipClient, connectorKey: string, timeoutMs?: number): Promise<string[]>;
+export declare function plausibleMatches(wanted: string, candidates: readonly string[]): string[];
+/** The two node-type forms a connector event is served in. */
+export type EventForm = "trigger" | "event";
+/** One event id in a `registry search` reply, with the forms it was served in. */
+export interface RegistryEvent {
+    id: string;
+    /** `trigger` = `uipath.connector.trigger.<key>.<id>` (starts a flow), `event` = `…event…` (waits mid-flow). */
+    forms: EventForm[];
+}
+/**
+ * The event ids in a `registry search <key>` reply, sorted, each with its forms.
+ *
+ * The form is kept because the two can come and go separately: on 2026-09-16
+ * the Data Fabric `.event.` pair was still served after its `.trigger.` pair
+ * was gone, and `prepare` probes the `.trigger.` form.
+ */
+export declare function registryEventIds(payload: unknown, connectorKey: string): RegistryEvent[];
+/** What `registry search <key>` served, or why it could not say. */
+export interface RegistryCatalog {
+    actions: string[];
+    events: RegistryEvent[];
+    /**
+     * Set when the search itself failed or did not answer JSON. The lists are
+     * then empty because nothing was read, NOT because the catalog is empty, and
+     * a message must not say "returned nothing".
+     */
+    failure?: string;
+}
+/**
+ * `registry search <key>`, read for both catalogs. This runs only on the
+ * failure path, to tell the author what the catalog does serve.
+ */
+export declare function registryCatalog(client: UipClient, connectorKey: string, timeoutMs?: number): Promise<RegistryCatalog>;

package/dist/registry/prepare/actions.js

@@ -3,9 +3,14 @@
  *
  * When `registry get uipath.connector.<key>.<action>` finds nothing — and the
  * event namespaces do not have it either — the one question left is what the
- * tenant actually serves for that connector, so the refusal can list it. That
- * is a `registry search <key>` against the live catalog rather than a cached
- * index, because a stale index is one of the ways this failure happens.
+ * catalog actually serves for that connector, so the refusal can list it: its
+ * actions AND its events, because the author's name may have meant either.
+ * That is one `registry search <key>`.
+ *
+ * `registry get` and `registry search` both answer from the CLI's local node
+ * index and pull the tenant catalog only when that index is missing (uipath-cli
+ * `packages/maestro-sdk/src/registry/node-sync-service.ts:307-323`, `:570-597`),
+ * so what they list can be stale; the refusal says how to refresh it.
  *
  * Ported from `_registry_actions` / `_closest_actions` in
  * `prepare_connector.py`. The fetch goes through the injected {@link UipClient};
@@ -13,6 +18,7 @@
  */
 import { compareCodePoints, sortedStrings } from "../compat/compare.js";
 import { registrySearch } from "../uip/commands.js";
+import { failureReason, findJsonDocument, tail } from "../uip/envelope.js";
 import { isPlainObject, pyOr } from "./support.js";
 /**
  * The action ids in a `registry search <key>` reply, sorted.
@@ -20,7 +26,8 @@ import { isPlainObject, pyOr } from "./support.js";
  * Exact prefix only: the same search returns
  * `uipath.agent.resource.tool.connector.<key>.<action>` and
  * `uipath.connector.trigger.<key>.<event>`, which are not actions of this node
- * and would read as alternatives an author could pass.
+ * and would read as alternatives an author could pass as an action. The events
+ * are listed separately, by {@link registryEventIds}.
  */
 export function registryActionIds(payload, connectorKey) {
     // `json.loads(stdout).get("Data") or []`: a reply that is not an object has
@@ -74,21 +81,88 @@ export function closestActions(action, candidates) {
     });
     return scored.map(({ candidate }) => candidate);
 }
+/** Levenshtein distance, two rows. Short strings only (operation ids). */
+function editDistance(a, b) {
+    let prev = Array.from({ length: b.length + 1 }, (_, i) => i);
+    for (let i = 1; i <= a.length; i++) {
+        const cur = [i];
+        for (let j = 1; j <= b.length; j++) {
+            cur[j] = Math.min(prev[j] + 1, cur[j - 1] + 1, prev[j - 1] + (a[i - 1] === b[j - 1] ? 0 : 1));
+        }
+        prev = cur;
+    }
+    return prev[b.length];
+}
 /**
- * `_registry_actions`: the action ids the registry serves for `connectorKey`,
- * or `[]` when the search fails or does not answer JSON. This runs only on the
- * failure path, where an empty answer is itself the message ("returned nothing").
+ * {@link closestActions}, kept only where the candidate is plausibly what was
+ * meant: it shares MOST of the wanted id's words (`list-all-records` →
+ * `list-records`), or it is a near spelling (`record-creatd` → `record-created`,
+ * `send-mail` → `send-email`). One shared word is not enough: `record-created`
+ * shares "record" with every Data Fabric action, and offering
+ * `update-entity-record` as the closest match to an EVENT name points the
+ * author at the wrong namespace.
  */
-export async function registryActions(client, connectorKey, timeoutMs) {
-    const result = await client.run(registrySearch(connectorKey), timeoutMs === undefined ? undefined : { timeoutMs });
-    if (result.code !== 0)
+export function plausibleMatches(wanted, candidates) {
+    const words = new Set(wanted.split("-"));
+    const limit = Math.max(2, Math.floor(wanted.length / 3));
+    const kept = closestActions(wanted, candidates)
+        .map((candidate, rank) => ({ candidate, rank, distance: editDistance(wanted, candidate) }))
+        .filter(({ candidate, distance }) => {
+        const shared = [...words].filter((word) => candidate.split("-").includes(word)).length;
+        return shared * 2 > words.size || distance <= limit;
+    });
+    // Nearest spelling first; the word-overlap rank breaks ties.
+    kept.sort((a, b) => a.distance - b.distance || a.rank - b.rank);
+    return kept.map(({ candidate }) => candidate);
+}
+/**
+ * The event ids in a `registry search <key>` reply, sorted, each with its forms.
+ *
+ * The form is kept because the two can come and go separately: on 2026-09-16
+ * the Data Fabric `.event.` pair was still served after its `.trigger.` pair
+ * was gone, and `prepare` probes the `.trigger.` form.
+ */
+export function registryEventIds(payload, connectorKey) {
+    if (!isPlainObject(payload))
         return [];
-    let payload;
-    try {
-        payload = JSON.parse(result.stdout);
-    }
-    catch {
+    const data = pyOr(payload.Data, []);
+    if (!Array.isArray(data))
         return [];
+    const forms = new Map();
+    for (const entry of data) {
+        if (!isPlainObject(entry))
+            continue;
+        const nodeType = pyOr(entry.NodeType, "");
+        if (typeof nodeType !== "string")
+            continue;
+        for (const form of ["trigger", "event"]) {
+            const prefix = `uipath.connector.${form}.${connectorKey}.`;
+            if (!nodeType.startsWith(prefix))
+                continue;
+            const rest = nodeType.slice(prefix.length);
+            if (rest.includes("."))
+                continue;
+            if (!forms.has(rest))
+                forms.set(rest, new Set());
+            forms.get(rest).add(form);
+        }
+    }
+    return sortedStrings(forms.keys()).map((id) => ({
+        id,
+        forms: ["trigger", "event"].filter((form) => forms.get(id).has(form)),
+    }));
+}
+/**
+ * `registry search <key>`, read for both catalogs. This runs only on the
+ * failure path, to tell the author what the catalog does serve.
+ */
+export async function registryCatalog(client, connectorKey, timeoutMs) {
+    const result = await client.run(registrySearch(connectorKey), timeoutMs === undefined ? undefined : { timeoutMs });
+    if (result.code !== 0)
+        return { actions: [], events: [], failure: failureReason(result) };
+    const payload = findJsonDocument(result.stdout);
+    if (payload === undefined) {
+        return { actions: [], events: [], failure: `it did not answer JSON: ${tail(result.stdout.trim()) || "no output"}` };
     }
-    return registryActionIds(payload, connectorKey);
+    return { actions: registryActionIds(payload, connectorKey), events: registryEventIds(payload, connectorKey) };
 }

package/dist/registry/prepare/connections.js

@@ -23,10 +23,9 @@
  */
 import { existsSync, readFileSync, rmSync, writeFileSync } from "node:fs";
 import { pyJsonStringify } from "../codecs/pyjson.js";
-import { pyStrip } from "../compat/pystr.js";
 import { Refusal, messageOf } from "../errors.js";
 import { isConnectionsList } from "../uip/commands.js";
-import { dataItems, parseEnvelope } from "../uip/envelope.js";
+import { dataItems, failureReason, parseEnvelope } from "../uip/envelope.js";
 import { isPlainObject, notJsonReason, pyGet, pyOr, pyRepr, pyStrAny, pyTruthy } from "./support.js";
 /** No usable connection, with the reason and the way forward (`_connections.ConnectionError_`). */
 export class ConnectionRefusal extends Refusal {
@@ -44,7 +43,7 @@ export class ConnectionRefusal extends Refusal {
 export async function listConnections(client, options) {
     const result = await client.run(isConnectionsList({ allFolders: options.allFolders, byoa: options.byoa }));
     if (result.code !== 0) {
-        throw new ConnectionRefusal(`listing connections failed: ${pyStrip(result.stderr) || "no output"}`, "CONNECTION_LISTING_FAILED");
+        throw new ConnectionRefusal(`listing connections failed: ${failureReason(result)}`, "CONNECTION_LISTING_FAILED");
     }
     const envelope = parseEnvelope(result.stdout);
     if (envelope === undefined) {