@zapier/kitcore 0.8.0 → 0.10.0

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # @zapier/kitcore
 
+## 0.10.0
+
+### Minor Changes
+
+- 4e560c0: Added `isCoreCancelledSignal`, a brand-based guard for the cancellation signal raised by `Controller.resolve`. It recognizes the signal across bundle boundaries where `instanceof CoreCancelledSignal` would not.
+
+## 0.9.0
+
+### Minor Changes
+
+- fffa08a: Added `CallContext` with the `isCallContext`, `rootCallContext`, and `childCallContext` helpers: an explicit per-call context (call id, nesting depth, and a per-invocation annotation bag) that the method boundary threads through nested, `imports`-bound delegations.
+
+  The `depth` passed to `onMethodStart` / `onMethodEnd` hooks is now derived from this context, so nested method calls report the correct `depth` even in environments without Node's `async_hooks` (such as browsers), where it was previously always `0`.
+
+- afa9c95: Added `additionalKeys` to object resolvers for resolving open-keyed records (a `z.record`). The resolution controller collects entries in an add/done loop, prompting for each entry's key and then its value.
+
+### Patch Changes
+
+- ccedc0c: Interactive resolution now reads a method's resolvers only from its `defineMethod` registration. Resolvers attached through the deprecated legacy bridge are no longer surfaced to the resolution controller. Define methods with `defineMethod` to get interactive parameter resolution.
+- d819031: The resolution controller now coerces a free-text answer for an object, array, or record parameter as JSON, so an interactively typed value resolves to the intended shape instead of failing validation. Scalar answers are unchanged.
+
 ## 0.8.0
 
 ### Minor Changes