@octaviaflow/flow-rules 0.10.0 → 0.11.0

package/dist/rules/configContracts.d.ts

@@ -54,13 +54,12 @@ export interface ConfigContract {
     };
 }
 /**
- * Every action that has a `config.ts`. Keyed by action id.
- *
- * Fourteen actions have no contract yet (group, ai_agent, idp_extract, the
- * file-format and storage actions, connector_trigger). For those,
- * `contractFor` returns undefined and consumers fall back to `inputSchema`
- * alone — which is exactly what they did before, so nothing regresses. Adding a
- * contract for one of them is a `config.ts` plus one line here.
+ * Every action in the catalog, keyed by action id — since 0.11.0 all 37
+ * definitions carry one (the last fifteen: group, ai_agent, idp_extract,
+ * connector_trigger, the five file-format actions and the six storage
+ * actions). `contractFor` is undefined only for an id the catalog does not
+ * know, and then consumers fall back to `inputSchema` alone. A new action is
+ * a `config.ts` plus one line here; the drift test covers it from then on.
  */
 export declare const CONFIG_CONTRACTS: Readonly<Record<string, ConfigContract>>;
 export declare function contractFor(actionId: string | undefined): ConfigContract | undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octaviaflow/flow-rules",
-  "version": "0.10.0",
+  "version": "0.11.0",
   "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",
   "type": "module",
   "main": "./dist/index.cjs",