@walkeros/cli 4.0.0-next-1777463920154 → 4.0.0

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # @walkeros/cli
 
-## 4.0.0-next-1777463920154
+## 4.0.0
 
 ### Major Changes
 
@@ -74,6 +74,117 @@
   - See `docs/migrating/v3-to-v4.mdx` on the website for the manual migration
     steps. No automated codemod is shipped.
 
+- 1ef33d9: **BREAKING:** Unified callback signatures across mapping and on.\*
+  subscriptions.
+
+  Every callback in walkerOS now reads `(data, context) => result`. Sources,
+  transformers, destinations, and stores already conformed; mapping and on.\*
+  join the family in v4.1.
+
+  ### Mapping callbacks
+
+  `fn`, `condition`, and `validate` now share a single shape:
+
+  `(value, context: Mapping.Context) => result`
+
+  `Mapping.Options` is removed. Replaced by `Mapping.Context`:
+
+  ```ts
+  interface Context {
+    event: WalkerOS.DeepPartialEvent;
+    mapping: Value | Rule;
+    collector: Collector.Instance; // required
+    logger: Logger.Instance; // required
+    consent?: WalkerOS.Consent; // resolved consent
+  }
+  ```
+
+  Rule-level `condition` is now `(event, context) => boolean`.
+  `Mapping.Options.props` is removed (no production callers).
+
+  #### Mapping upgrade
+
+  ```ts
+  // before
+  const fn: Mapping.Fn = (value, mapping, options) => /* … */;
+  const cond: Mapping.Condition = (value, mapping, collector) => /* … */;
+  const val: Mapping.Validate = (value) => /* … */;
+
+  // after
+  const fn: Mapping.Fn = (value, context) => /* … */;
+  const cond: Mapping.Condition = (value, context) => /* … */;
+  const val: Mapping.Validate = (value, context) => /* … */;
+  ```
+
+  In `$code:` strings (flow.json):
+
+  ```json
+  // before
+  "fn": "$code:(value, mapping, options) => …"
+  "condition": "$code:(value, mapping, collector) => …"
+
+  // after
+  "fn": "$code:(value, context) => …"
+  "condition": "$code:(value, context) => …"
+  ```
+
+  `context.mapping` replaces the second positional arg; `context.collector`,
+  `context.logger`, and `context.consent` are all available.
+
+  One-arg callbacks like `(value) => value.toUpperCase()` continue to work
+  unchanged.
+
+  ### On.\* subscription callbacks
+
+  `walker.on('consent', …)`, `walker.on('ready', …)`, etc. now receive
+  `(data, context: On.Context) => void | Promise<void>`. The legacy `Context`
+  interface, `*Config` aliases, and `Options` discriminated union are removed.
+
+  ```ts
+  interface Context {
+    collector: Collector.Instance; // required
+    logger: Logger.Instance; // required
+  }
+
+  type Fn<TData = unknown> = (
+    data: TData,
+    context: Context,
+  ) => void | Promise<void>;
+
+  type ConsentFn = Fn<WalkerOS.Consent>;
+  type SessionFn = Fn<Collector.SessionData | undefined>;
+  type UserFn = Fn<WalkerOS.User>;
+  type ReadyFn = Fn<void>;
+  type RunFn = Fn<void>;
+  type GenericFn = Fn<unknown>;
+  ```
+
+  The new `On.Subscription` alias is the registerable union for
+  `walker.on(action, X)`.
+
+  #### On.\* upgrade
+
+  ```ts
+  // before
+  walker.on('consent', { marketing: (collector, consent) => /* … */ });
+  walker.on('ready', (collector) => /* … */);
+  walker.on('session', (collector, session) => /* … */);
+
+  // after
+  walker.on('consent', { marketing: (consent, ctx) => /* … */ });
+  walker.on('ready', (_, ctx) => /* … */);
+  walker.on('session', (session, ctx) => /* … */);
+  ```
+
+  `ctx.collector` replaces the positional first arg; `ctx.logger` is also
+  available.
+
+  ### Why both at once
+
+  Both refactors follow the same `(data, context)` pattern. Shipping them in one
+  release means consumers do one search-and-replace pass instead of two, and the
+  codebase reaches full callback-signature consistency in v4.1.
+
 ### Minor Changes
 
 - cfc7469: **Breaking — `@walkeros/core`:** `fetchPackage(name, { baseUrl })`
@@ -121,6 +232,31 @@
 
 ### Patch Changes
 
+- ca237ef: Fix `walkeros push` deadlock for web flows whose destinations await
+  real timers during init.
+
+  Previously, async-drain timer interception captured every `setTimeout` into a
+  pending map and only fired them via a post-`fn` flush. If a destination's init
+  awaited one of those captured timers (e.g.,
+  `@walkeros/web-destination-amplitude`'s engagement plugin awaits a 10s
+  setTimeout to give up on a CDN script load), `init` never resolved,
+  `await collector.push` deadlocked, and Node exited with
+  `Detected unsettled top-level await` (exit 13).
+
+  A drain pump now runs alongside `fn(flowModule)` for non-`--simulate` runs:
+  each tick fires every captured non-cleared timer using a real `setImmediate`
+  reference. Timers fire in delay-ascending order, intervals re-register,
+  callback errors are reported via `console.warn`. Bounded by max-iterations
+  (1000) and wall-clock (30s) caps.
+
+  `--simulate <step>` continues to use the post-`fn` flush path so snapshot
+  ordering remains stable.
+
+  Behavior change (edge case): a destination using `setTimeout` for retry
+  backoff under `walkeros push` (real, non-simulate) now sees its timer fire
+  instantly. This was already the documented contract for `--simulate <step>`
+  snapshots; it now extends to real `push` for consistency.
+
 - 6422b9b: Validate device-code and token responses from the auth server with
   Zod schemas at the trust boundary in `login/index.ts`. Malformed responses now
   surface as structured errors instead of being trusted into config writes or
@@ -154,14 +290,16 @@
     `deploy` action is unchanged.
 
 - Updated dependencies [93ea9c4]
+- Updated dependencies [465775c]
 - Updated dependencies [942a7fe]
 - Updated dependencies [cfc7469]
 - Updated dependencies [8e06b1f]
 - Updated dependencies [3d50dd6]
-  - @walkeros/core@4.0.0-next-1777463920154
-  - @walkeros/collector@4.0.0-next-1777463920154
-  - @walkeros/server-destination-api@4.0.0-next-1777463920154
-  - @walkeros/server-core@4.0.0-next-1777463920154
+- Updated dependencies [1ef33d9]
+  - @walkeros/core@4.0.0
+  - @walkeros/collector@4.0.0
+  - @walkeros/server-destination-api@4.0.0
+  - @walkeros/server-core@4.0.0
 
 ## 3.4.2