@walkeros/core 4.8.1 → 4.8.3-next-1793115089237

package/CHANGELOG.md

@@ -1,5 +1,101 @@
 # @walkeros/core
 
+## 4.8.3-next-1793115089237
+
+### Patch Changes
+
+- 34fd225: The mapping rule descriptions shown in property tables and
+  `package_get` now match the behaviour: a `condition` that returns false moves
+  on to the next rule, `batch` works only on a destination with `pushBatch`,
+  `extend` applies only in `@walkeros/transformer-ga4`'s `settings.mapping`, and
+  the `mappingKey` and batch `key` examples are `"product view"`.
+- 5313635: A destination package can publish `examples.minimal` from
+  `src/examples/minimal.ts` (`MINIMAL_EXAMPLE_FILE`): the settings it needs to
+  deliver, credentials named as secrets. `composeQuickstart` from
+  `@walkeros/core/dev` turns it into the install line, the integrated code and a
+  complete flow reading each credential as `$secret`, and throws when they
+  cannot be built. `packageMetaOf` writes a package's `$meta`, a single platform
+  as a list.
+- 5313635: Schema descriptions now match the behaviour: `setup` on destinations,
+  stores and flow steps runs only through `walkeros setup`; an event cache's
+  `stop` defaults to true on sources, and `update` changes only a source's
+  response, on HIT and MISS. They appear in the flow JSON Schema and in MCP.
+- 5313635: The source config descriptions of `require`, `setup` and `ingest` now
+  match the behaviour: `require` delays only `on()` calls, not init or event
+  capture; `setup` runs only through `walkeros setup`; `ingest` resolves against
+  the normalized request scope of server sources.
+- 5313635: `@walkeros/core/dev` exports `toSerializable`, which turns a value
+  into what `walkerOS.json` publishes: functions become `{ $code }` objects with
+  their source text, Zod schemas are left out, and everything else is copied.
+  The package build and the step example runner both use it, so tests run what
+  is published.
+- 5313635: The sample events from `getEvent` now use the standard event names:
+  `checkout start` replaces `checkout view`, an order carries `tax` and `total`,
+  a promotion names its placement `slot`, and product events carry `currency`.
+  Order `value` is now the merchandise value: the `order complete` sample goes
+  from 555 to 462, and the gross amount charged is `total` (467.22). The
+  destination examples read `data.tax`, `data.slot` and the search keys
+  `data.term` and `data.results`, and gross fields such as Matomo `grandTotal`
+  read `data.total` first, then `data.value`. The CLI ships default event
+  contracts for common site types in `examples/contracts/`.
+- 34fd225: The `PushResult.error` description now says when it is set: for a
+  rejected event or a failure before the destinations. A destination's failure
+  is reported in `failed`, under its id with a `reason`, and leaves `error`
+  unset.
+- 5313635: `@walkeros/core` exports the `StepType` type, the kind of a step
+  package (`source`, `transformer`, `destination` or `store`), read from
+  `STEP_TYPES` on `@walkeros/core/dev`. `StepKind`, `FlowStepType` and `stepId`
+  use it, as do the step kinds `resolveExportName` in `@walkeros/cli` and the
+  simulate tool of `@walkeros/mcp` take, so the kinds are listed in one place.
+
+## 4.8.2
+
+### Patch Changes
+
+- 2374f54: `logger.throw` only throws and no longer writes a log line; the
+  collector writes the one failure line. A rule `condition` that throws fails
+  the event instead of falling through. A mapping value without an operator is
+  dropped and reported. The wildcard lookup tries exact, `entity *`, `* action`,
+  then `* *`, and falls through a tier whose conditions all fail.
+- 7e5fc27: A JSON log line above 32 KiB now truncates its message as well as its
+  context and sets `messageTruncated: true`, so one oversized line can no longer
+  break a log pipeline. Mapping problems report under the step `mapping.<rule>`,
+  one line per rule.
+- 2374f54: `logger.format: 'json'` prints one JSON object per line on server
+  flows, with `severity`, `message`, `time`, `scope` and `context`; errors and
+  warnings go to stderr. Web flows reject it. A log handler receives the cause
+  code, status, retryable flag and suppressed count as structured fields, so
+  lines can be forwarded without parsing.
+- 964590a: Tag Mode's `moin` and the preview activator `browserSwapActivator`
+  (with `SwapActivatorConfig` and `SESSION_STORAGE_KEY`) moved to
+  `@walkeros/web-core`, and `isElementOrDocument` is removed.
+  `serializeStoreValue`, `deserializeStoreValue` and `StoreCodecError` moved to
+  `@walkeros/core/node`. `getFlowSettings` reads `$env` only from the `env` you
+  pass it, never from `process.env`. Errors keep `cause` in every browser.
+- 4100ede: `getEvent` returns the same event on every run: a fixed timestamp and
+  an id derived from the event name. It accepts only standard event names, so a
+  typo no longer compiles; `createEvent` builds any other event and uses the
+  same fixed default timestamp. `order complete` carries the order amount as
+  `data.value` instead of `data.total`, and the package examples read
+  `data.value`.
+- 2374f54: New `StepError` carries a code, an HTTP status and `retryable`;
+  `acknowledge(result)` tells a producer to ack, retry or reject a message, and
+  `reportCause` writes one failure line per cause. `SendResponse` is `{ data }`.
+  An `init` of a destination, transformer or store can no longer return `false`:
+  throw a `StepError`, and untyped `false` fails with `not-ready`.
+- 2374f54: Flow validation now rejects unknown keys in step `config`,
+  destination and store entries, the `collector` block, inline `code` and
+  contract rules, mapping keys with no effect at their position, values without
+  an operator or with two producers, and malformed whole-value references.
+  Inline code may define `pushBatch`, `on` and `destroy`. Strict `$flow` treats
+  an empty value as unresolved.
+- 15eb7b2: The error for an empty `$flow` reference names only the setting to
+  fill in; it no longer suggests a `walkeros deploy` command.
+- 33a2779: `$flow` references now accept flow names with a hyphen, such as
+  `$flow.tracking-server.url`.
+- 33a2779: Tag Mode's loader now hears the app's call on sites that block
+  messages from origins they do not know.
+
 ## 4.8.1
 
 ### Patch Changes
@@ -710,9 +806,6 @@
     and `event.context` remain required.
   - Each source self-registers via TypeScript module augmentation of `SourceMap`
     in `@walkeros/core`.
-  - App-side coordination (`/workspaces/developer/app`) is a follow-up plan, not
-    part of this release. Telemetry from v4 CLI/MCP will not validate against
-    the existing app schema until that follow-up ships.
   - `Mapping.Rule.skip` is renamed to `Mapping.Rule.silent`. Customer flow.json
     configs using `skip: true` in mapping rules must rename to `silent: true`.
     Hard cut: no legacy alias, the field is gone.