@octaviaflow/flow-rules 0.8.1 → 0.9.0

package/dist/index.cjs

@@ -5046,7 +5046,6 @@ function validateStepConfig(step) {
   if (!definition)
     return issues;
   const declared = new Map(contractFieldsFor(definition).map((f) => [f.key, f]));
-  const derived = contractDerivedKeys(definition);
   const entries = Object.entries(config);
   for (const [key, value] of entries) {
     const field = declared.get(key);
@@ -5062,7 +5061,7 @@ function validateStepConfig(step) {
     }
     if (!typeMatches(field, value)) {
       issues.push({
-        severity: derived.has(key) ? "warning" : "error",
+        severity: "error",
         code: "FIELD_WRONG_TYPE",
         stepId,
         field: key,

package/dist/index.js

@@ -4932,7 +4932,6 @@ function validateStepConfig(step) {
   if (!definition)
     return issues;
   const declared = new Map(contractFieldsFor(definition).map((f) => [f.key, f]));
-  const derived = contractDerivedKeys(definition);
   const entries = Object.entries(config);
   for (const [key, value] of entries) {
     const field = declared.get(key);
@@ -4948,7 +4947,7 @@ function validateStepConfig(step) {
     }
     if (!typeMatches(field, value)) {
       issues.push({
-        severity: derived.has(key) ? "warning" : "error",
+        severity: "error",
         code: "FIELD_WRONG_TYPE",
         stepId,
         field: key,

package/dist/rules/configContracts.d.ts

@@ -93,12 +93,13 @@ export declare function contractVocabularyDrift(actionId: string): string[];
 /**
  * Keys `contractFieldsFor` ADDED — declared by config.ts but not by inputSchema.
  *
- * The fence treats a type mismatch on one of these as a WARNING, not an error,
- * until it has been measured against real flows. The reason is concrete: the
- * moment http_request's contract declared `queryParams: array`, a fixture that
- * stored it as an object stopped saving. On beta 71 of 131 real config keys
- * were undeclared, so any of them may be stored in a shape the contract does
- * not expect — and refusing the save would leave whoever opens that flow
- * unable to save it. inputSchema-declared keys keep their existing error.
+ * In 0.8.1 the fence treated a type mismatch on one of these as a WARNING,
+ * pending a measurement: the moment http_request's contract declared
+ * `queryParams: array`, a fixture storing it as an object stopped saving, and
+ * with 71 of 131 real keys previously undeclared any might have been stored in
+ * an unexpected shape. Measured 2026-09-26 against every flow on beta — 79
+ * flows, 302 steps — zero mismatches. 0.9.0 promotes them to errors, the same
+ * as any other declared key. This helper remains for tooling that wants to
+ * know which keys the contract added.
  */
 export declare function contractDerivedKeys(definition: ActionDefinition): Set<string>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octaviaflow/flow-rules",
-  "version": "0.8.1",
+  "version": "0.9.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",