@octaviaflow/flow-rules 0.19.1 → 0.21.0

package/dist/rules/nodeConfigStatus.d.ts

@@ -31,3 +31,26 @@ export interface NodeConfigStatusResult {
  * - "unconfigured" → Action definition not found (unknown action type)
  */
 export declare function getNodeConfigStatus(node: WorkflowNode): NodeConfigStatusResult;
+/**
+ * Settings the action's CONFIG CONTRACT requires that its `inputSchema` does
+ * not (absent there, or declared optional), left empty on this node (DEV-629).
+ *
+ * `getNodeConfigStatus` reads `inputSchema` alone, and some actions keep a
+ * required setting only in the contract: Google Chat's `space` is one. A step
+ * with no space passed `check_flow` and the editor, then failed at run time.
+ * These are reported as WARNINGS (owner decision, 2026-11-09): they name a
+ * real gap without blocking activation of a flow that was valid before.
+ * The drift test pins the list of such keys, so a new one is a decision.
+ */
+export declare function missingContractRequired(node: WorkflowNode): string[];
+/**
+ * What the action's own contract check (`validate()`, the check its config
+ * panel runs) says is wrong with this node, deduplicated (DEV-643).
+ *
+ * `getNodeConfigStatus` only asks whether each required setting is filled in;
+ * a Variables step whose `fields` holds a row with no key passed it, so
+ * `check_flow` and the canvas called the flow fine while the panel and the
+ * MCP's `add_step` said "Each field needs a key". A validator that throws is
+ * treated as silent: a broken check must not invent a problem.
+ */
+export declare function contractValidationErrors(node: WorkflowNode): string[];

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@octaviaflow/flow-rules",
-  "version": "0.19.1",
-  "description": "The flow action catalog and the rules engine behind Flow Doctor — one definition of what a step accepts and what makes a flow valid, shared by the editor and the server",
+  "version": "0.21.0",
+  "description": "The flow action catalog and the rules engine behind Flow Doctor \u2014 one definition of what a step accepts and what makes a flow valid, shared by the editor and the server",
   "type": "module",
   "main": "./dist/index.cjs",
   "module": "./dist/index.js",