@pumped-fn/core-next 0.5.82 → 0.5.84

package/CHANGELOG.md

@@ -1,5 +1,80 @@
 # @pumped-fn/core-next
 
+## 0.5.84
+
+### Patch Changes
+
+- 252db92: Simplify Extension.Operation types and remove generic from wrap method
+
+  - Consolidated 5 operation kinds (execute, journal, subflow, parallel, resolve) into 2 kinds (execution, resolve)
+  - Removed generic type parameter from Extension.wrap method for simpler type signatures
+  - Updated all wrapWithExtensions implementations to use type assertions
+  - Migrated all tests to new operation type structure
+  - Updated documentation for simplified 2-kind operation model
+  - Benefits: Simpler mental model, easier AI explanation, more flexible tag-based nesting context
+
+- 5f190c0: Fix validation bug, simplify flow execution, and fix tag/metadata access
+
+  **Bug Fix:**
+
+  - Fixed: Non-journaled flows now validate input/output (previously skipped validation)
+  - All flows with schemas now guarantee validation on every execution
+  - Fixed: flowMeta.depth calculation when parent depth is undefined (was NaN, now 0)
+  - Fixed: Tag access via ctx.get() - Tag objects are functions, not objects (typeof check was wrong)
+  - Fixed: Child context created before operation (extensions now see correct depth metadata)
+  - Fixed: FlowContext.get() now checks scope.tags after execution tags
+  - Fixed: Test using ctx.get() changed to ctx.find() for optional tags
+
+  **Refactor:**
+
+  - Simplified exec() from 190 lines to ~50 lines via functional decomposition
+  - Extracted pure helper functions: createChildContext, executeFlowHandler, executeJournaledFlow, executeNonJournaledFlow, executeJournaledFn, executeNonJournaledFn, executeAndWrap, executeWithTimeout
+  - Enforced safety via TypeScript: UnwrappedExecutor type prevents returning without extension wrapping, ContextConfig type requires parent linkage
+  - Eliminated 4 execution paths into single route with helpers
+  - Removed duplicate validation/wrapping logic across paths
+
+  **Enhanced:**
+
+  - custom() now accepts optional validator function for inline validation:
+    ```ts
+    custom<number>((value) => {
+      if (typeof value !== "number") {
+        return { success: false, issues: [{ message: "Expected number" }] };
+      }
+      return value;
+    });
+    ```
+
+  **Testing:**
+
+  - Rebuilt test suite from scratch: 2 files, ~500 lines total
+  - flow-execution.test.ts: API behavior for app developers (22/22 tests passing ✅)
+  - flow-extensions.test.ts: Extension integration (20/20 tests passing ✅)
+  - Added comprehensive result inspection throughout tests
+  - Deleted 8 overlapping legacy test files
+  - All 268 core-next tests passing ✅
+
+- 13f84a4: Internal refactoring: consolidate duplicate patterns
+
+  - Extract `wrapWithExtensions` to internal/extension-utils.ts (eliminates duplication between flow.ts and scope.ts)
+  - Consolidate dependency resolution via internal `resolveShape` utility
+  - Simplify FlowDefinition.handler overload implementation
+  - Increase packages/next/src by +0.72% (+33 LOC) due to new internal utilities and comprehensive test coverage
+
+  No public API changes. All tests pass. Performance neutral or improved.
+
+## 0.5.83
+
+### Patch Changes
+
+- 811926e: Refactor FlowContext.exec for improved maintainability and add comprehensive extension tests
+
+  - Reduce exec method from 323 to 138 lines (72% reduction)
+  - Extract shared utilities: abort-utils, journal-utils
+  - Add helper methods: parseExecOverloads, executeJournaledFn, executeSubflow
+  - Add comprehensive extension tests with full operation metadata validation
+  - Verify extension wrapping order and nested operations
+
 ## 0.5.82
 
 ### Patch Changes