@octaviaflow/flow-rules 0.10.0 → 0.11.1

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/dist/rules/configSafety.d.ts

@@ -33,8 +33,26 @@
  * An enumerated field's options are checked but only WARN, for the same
  * reason — see the note at that check.
  */
+import { type FieldConfig } from "../catalog/types";
 /** Largest config a single step may carry, serialised. */
 export declare const MAX_STEP_CONFIG_BYTES: number;
+/**
+ * Keys that belong to the PLATFORM, not to any action — on nearly every step,
+ * declared by no contract, and rightly so:
+ *
+ *   - `flowId`: NodeConfigPanel seeds every custom panel's config with the flow
+ *     it belongs to, and it is saved with the step;
+ *   - `outputAs`: the Engine reads it for EVERY step type — the step's key in
+ *     the run's data bag.
+ *
+ * Type-checked like a declared field; never reported as undeclared; never
+ * advertised by `contractFieldsFor` (an agent is told the action's own keys).
+ * Before this, every panel-built step raised one to four UNDECLARED_FIELD
+ * warnings for these and the editor's own `_` snapshots, which drowned the
+ * warnings that mean something — `connection` on a storage step, `message` on
+ * a Slack step (DEV-412).
+ */
+export declare const PLATFORM_CONFIG_KEYS: Readonly<Record<string, FieldConfig>>;
 export type ConfigIssueCode = "FORBIDDEN_KEY" | "CONFIG_TOO_LARGE" | "CONFIG_TOO_DEEP" | "FIELD_WRONG_TYPE" | "FIELD_BAD_OPTION" | "UNDECLARED_FIELD";
 export interface ConfigIssue {
     severity: "error" | "warning";

package/package.json

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