@hogsend/cli 0.14.0 → 0.16.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hogsend/cli",
-  "version": "0.14.0",
+  "version": "0.16.0",
   "type": "module",
   "license": "MIT",
   "repository": {
@@ -34,7 +34,7 @@
     "tsup": "^8.5.1",
     "tsx": "^4.22.4",
     "vitest": "^4.1.7",
-    "@hogsend/studio": "^0.14.0",
+    "@hogsend/studio": "^0.16.0",
     "@repo/typescript-config": "0.0.0"
   },
   "engines": {
@@ -44,8 +44,8 @@
     "@clack/prompts": "^1.5.0",
     "better-auth": "^1.6.11",
     "picocolors": "^1.1.1",
-    "@hogsend/db": "^0.14.0",
-    "@hogsend/engine": "^0.14.0"
+    "@hogsend/db": "^0.16.0",
+    "@hogsend/engine": "^0.16.0"
   },
   "scripts": {
     "prebuild": "node scripts/bundle-studio.mjs",

package/skills/hogsend-authoring-emails/references/tracking-and-unsubscribe.md

@@ -184,3 +184,12 @@ Semantics at click time:
 - The answering journey reads the payload from
   `ctx.waitForEvent(...) → { timedOut, properties }` — see the
   hogsend-authoring-journeys skill.
+- **No landing page?** `href={HOSTED_ANSWER_HREF}` (from `@hogsend/email`)
+  resolves to the engine-hosted answer page: a thanks page with an optional
+  free-text box whose submission ingests `<event>.comment` (one comment per
+  send + event). Possession of the link is the auth, like unsubscribe.
+- **Cross-device stitch (opt-in):** `TRACKING_IDENTITY_TOKEN=true` appends an
+  encrypted one-hour `hs_t` token to tracked redirects; the landing site
+  exchanges it at `POST /v1/t/identify` for the distinct id and calls
+  `posthog.identify`. Never put a raw email in a URL — the token exists so
+  you don't have to.

package/skills/hogsend-conditions/SKILL.md

@@ -37,10 +37,12 @@ Not every surface accepts all four types — match the type to the field:
 
 - **`trigger.where`** (journey) → `PropertyCondition[]` ONLY. Property
   conditions, AND-ed together, evaluated against the triggering event's
-  properties. No event/engagement/composite legs here.
+  properties. No event/engagement/composite legs here. Authoring sugar: a
+  builder function — `where: (b) => b.prop("score").lte(6)` (or an array of
+  terminals) — resolves ONCE at `defineJourney` time to the identical POJOs.
 - **`exitOn[].where`** (journey) → `PropertyCondition[]` ONLY. Same shape;
   AND-ed against the incoming event's properties. Omit `where` to exit on the
-  event name alone.
+  event name alone. Accepts the same builder-function sugar.
 - **`criteria`** (bucket) → a single `ConditionEval` tree — ALL FOUR types,
   composed with `composite` / `b.all()` / `b.any()`. This is the only surface
   that runs against the database (event counts, engagement, windows).
@@ -57,7 +59,8 @@ Not every surface accepts all four types — match the type to the field:
 
 ## Golden rules
 
-1. `trigger.where` and `exitOn[].where` take `PropertyCondition[]` only — if
+1. `trigger.where` and `exitOn[].where` take `PropertyCondition[]` (write them
+   with the `(b) => b.prop(...)` builder for short) — if
    you need an event count or a time window, that logic belongs in the
    journey's `run` body (`ctx.history.hasEvent`) or in a bucket's `criteria`,
    not in `where`.

package/skills/hogsend-conditions/references/examples.md

@@ -14,6 +14,23 @@ properties. Only `property` conditions are valid here — there is no `within`,
 no event count, no composite. (Need a count or a window? Put that logic in the
 `run` body via `ctx.history.hasEvent`, or model it as a bucket.)
 
+Author it either way — the builder form resolves once at `defineJourney` time
+to the identical data (same machinery as bucket criteria):
+
+```ts
+// Builder form (recommended)
+trigger: {
+  event: Events.NPS_DETRACTOR,
+  where: (b) => b.prop("score").lte(3),
+},
+
+// Multiple conditions: return an array (AND-ed)
+trigger: {
+  event: Events.CHECKOUT_ABANDONED,
+  where: (b) => [b.prop("plan").eq("pro"), b.prop("cartValue").gte(100)],
+},
+```
+
 ```ts
 import { days, hours } from "@hogsend/core";
 import { defineJourney, sendEmail } from "@hogsend/engine";
@@ -56,7 +73,8 @@ export const proCheckoutAbandoned = defineJourney({
 
 `exitOn` is an array of `{ event, where? }`. The engine matches the incoming
 event name; if `where` is present it must pass (`PropertyCondition[]`, AND-ed)
-for the exit to fire. Omit `where` to exit on the event name alone.
+for the exit to fire. Omit `where` to exit on the event name alone. The
+builder form works here too: `where: (b) => b.prop("plan").eq("pro")`.
 
 ```ts
 meta: {