@warlock.js/cascade 5.19.0 → 5.20.0

package/llms.txt

@@ -6,19 +6,19 @@
 
 ## Skills
 
-- [aggregate-data](@warlock.js/cascade/aggregate-data/SKILL.md): Use aggregates and groupBy in @warlock.js/cascade; use when you need to aggregate data.
-- [alter-migration](@warlock.js/cascade/alter-migration/SKILL.md): Alter a migration in @warlock.js/cascade; use when you need to alter migration.
+- [aggregate-data](@warlock.js/cascade/aggregate-data/SKILL.md): (no description)
+- [alter-migration](@warlock.js/cascade/alter-migration/SKILL.md): (no description)
 - [cascade-basics](@warlock.js/cascade/cascade-basics/SKILL.md): Start here for @warlock.js/cascade models, data sources, migrations, and query workflows.
-- [configure-delete-strategy](@warlock.js/cascade/configure-delete-strategy/SKILL.md): Use delete strategies in @warlock.js/cascade; use when you need to configure delete strategy.
-- [define-model](@warlock.js/cascade/define-model/SKILL.md): Define a model in @warlock.js/cascade; use when you need to define model.
-- [define-relations](@warlock.js/cascade/define-relations/SKILL.md): Define and query relations in @warlock.js/cascade; use when you need to define relations.
-- [manage-data-sources](@warlock.js/cascade/manage-data-sources/SKILL.md): Manage data sources in @warlock.js/cascade; use when you need to manage data sources.
-- [manage-transactions](@warlock.js/cascade/manage-transactions/SKILL.md): Use transactions in @warlock.js/cascade; use when you need to manage transactions.
-- [paginate-results](@warlock.js/cascade/paginate-results/SKILL.md): Paginate results in @warlock.js/cascade; use when you need to paginate results.
-- [perform-atomic-ops](@warlock.js/cascade/perform-atomic-ops/SKILL.md): Use atomic operations in @warlock.js/cascade; use when you need to perform atomic ops.
-- [query-data](@warlock.js/cascade/query-data/SKILL.md): Query data in @warlock.js/cascade; use when you need to query data.
-- [run-cascade-cli](@warlock.js/cascade/run-cascade-cli/SKILL.md): Run the cascade CLI / Operations API in @warlock.js/cascade; use when you need to run cascade cli.
-- [search-by-vector](@warlock.js/cascade/search-by-vector/SKILL.md): Use vector search in @warlock.js/cascade; use when you need to search by vector.
-- [subscribe-to-model-events](@warlock.js/cascade/subscribe-to-model-events/SKILL.md): Use model events in @warlock.js/cascade; use when you need to subscribe to model events.
-- [track-changes](@warlock.js/cascade/track-changes/SKILL.md): Track changes in @warlock.js/cascade; use when you need to track changes.
-- [write-migration](@warlock.js/cascade/write-migration/SKILL.md): Write a migration in @warlock.js/cascade; use when you need to write migration.
+- [configure-delete-strategy](@warlock.js/cascade/configure-delete-strategy/SKILL.md): (no description)
+- [define-model](@warlock.js/cascade/define-model/SKILL.md): (no description)
+- [define-relations](@warlock.js/cascade/define-relations/SKILL.md): (no description)
+- [manage-data-sources](@warlock.js/cascade/manage-data-sources/SKILL.md): (no description)
+- [manage-transactions](@warlock.js/cascade/manage-transactions/SKILL.md): (no description)
+- [paginate-results](@warlock.js/cascade/paginate-results/SKILL.md): (no description)
+- [perform-atomic-ops](@warlock.js/cascade/perform-atomic-ops/SKILL.md): (no description)
+- [query-data](@warlock.js/cascade/query-data/SKILL.md): (no description)
+- [run-cascade-cli](@warlock.js/cascade/run-cascade-cli/SKILL.md): (no description)
+- [search-by-vector](@warlock.js/cascade/search-by-vector/SKILL.md): (no description)
+- [subscribe-to-model-events](@warlock.js/cascade/subscribe-to-model-events/SKILL.md): (no description)
+- [track-changes](@warlock.js/cascade/track-changes/SKILL.md): (no description)
+- [write-migration](@warlock.js/cascade/write-migration/SKILL.md): (no description)

package/package.json

@@ -11,11 +11,11 @@
     "@mongez/copper": "^2.1.2",
     "@mongez/dotenv": "^1.3.2",
     "@mongez/events": "^2.2.7",
-    "@mongez/reinforcements": "^4.0.1",
-    "@mongez/supportive-is": "^2.1.4",
-    "@warlock.js/context": "5.19.0",
-    "@warlock.js/logger": "5.19.0",
-    "@warlock.js/seal": "5.19.0",
+    "@mongez/reinforcements": "^4.0.2",
+    "@mongez/supportive-is": "^2.1.5",
+    "@warlock.js/context": "5.20.0",
+    "@warlock.js/logger": "5.20.0",
+    "@warlock.js/seal": "5.20.0",
     "citty": "^0.2.2",
     "fast-glob": "^3.3.3"
   },
@@ -51,7 +51,7 @@
   ],
   "author": "hassanzohdy",
   "license": "MIT",
-  "version": "5.19.0",
+  "version": "5.20.0",
   "main": "./cjs/index.cjs",
   "module": "./esm/index.mjs",
   "types": "./esm/index.d.mts",

package/skills/aggregate-data/SKILL.md

@@ -1,165 +1,165 @@
----
-name: aggregate-data
-description: "Use aggregates and groupBy in @warlock.js/cascade; use when you need to aggregate data."
----
-
-# Use aggregates and groupBy
-
-Cascade's query builder isn't only for finding records — it crunches numbers too. The same calls run on MongoDB and Postgres.
-
-## Scalar aggregates
-
-```ts
-const total      = await Order.count();                  // count is static on the model
-const revenue    = await Order.query().sum("total");
-const avgTicket  = await Order.query().avg("total");
-const cheapest   = await Order.query().min("total");
-const priciest   = await Order.query().max("total");
-
-// Filtered
-const monthRevenue = await Order.query()
-  .whereDateAfter("created_at", startOfMonth)
-  .sum("total");
-```
-
-Each returns a single number (`Promise<number>`). Only `count` is a static shortcut on the model; `sum` / `avg` / `min` / `max` (and the date helpers) are query-builder methods — reach them via `Order.query()` or chain off `Order.where(...)`. Date filters take a single date: `whereDate(field, value)` (exact day, time ignored), `whereDateAfter` / `whereDateBefore` (one-sided), `whereDateBetween(field, [a, b])` (range) — there is no 3-arg `whereDate(field, op, value)`. By Cascade convention the scalar terminators return **`0` on zero rows — not `null`** — so you can use the result directly without a null guard.
-
-## Grouped rollups — two-arg `groupBy(fields, aggregates)`
-
-To compute aggregates *per group*, pass a second argument to `groupBy`: an object mapping output aliases to aggregate expressions. Build the expressions with the `$agg` helpers:
-
-```ts
-import { $agg } from "@warlock.js/cascade";
-
-const stats = await Order.query()
-  .groupBy("category", {
-    total: $agg.sum("amount"),
-    orders: $agg.count(),
-    avg: $agg.avg("amount"),
-  })
-  .get();
-// each row: { category, total, orders, avg }
-```
-
-`fields` is a string or string array (`groupBy(["status", "country"], {...})` groups by each combination). Single-arg `groupBy("category")` / `groupBy(["a","b"])` groups **without** computing aggregates.
-
-### `$agg` helpers — six cross-driver, four MongoDB-only
-
-Cross-driver (identical call on MongoDB **and** Postgres):
-
-- `$agg.count()` · `$agg.countDistinct(field)` · `$agg.sum(input)` · `$agg.sumRaw(expression)` · `$agg.avg(field)` · `$agg.min(field)` · `$agg.max(field)`
-- `$agg.countDistinct(field)` counts distinct values per group: Postgres `COUNT(DISTINCT col)`; MongoDB `$addToSet` in `$group` finalized with `$size` in the renaming `$project`.
-
-### Summing a computed expression — `$agg.sum(expr)` / `$agg.sumRaw`
-
-`$agg.sum` accepts either a bare column name (`$agg.sum("amount")`, unchanged) **or** a typed, cross-driver column expression so you can sum a computed value like `price * quantity` without dropping to raw SQL. Build the expression with the `$expr` combinators (grouped under one object, like `$agg`): `$expr.col` / `$expr.lit` / `$expr.mul` / `$expr.add` / `$expr.sub` / `$expr.div`.
-
-```ts
-import { $agg, $expr } from "@warlock.js/cascade";
-
-const revenue = await OrderItem.query()
-  .groupBy("product_id", {
-    revenue: $agg.sum($expr.mul("price", "quantity")),                       // SUM(price * quantity)
-    net:     $agg.sum($expr.mul($expr.sub($expr.lit(1), "discount"), "price")),// SUM((1 - discount) * price)
-  })
-  .get();
-```
-
-Cross-driver: Postgres emits `SUM(("price" * "quantity"))`, MongoDB emits `{ $sum: { $multiply: ["$price", "$quantity"] } }`. Column names flow through the driver's identifier-quoting path — they're never string-interpolated. The bare-string form (`$agg.sum("amount")`) produces a byte-for-byte-identical payload to before, so existing call sites are unchanged.
-
-When the typed combinators can't express what you need, reach for the raw escape hatch `$agg.sumRaw("price * quantity * (1 - discount)")` — the string is emitted verbatim (**never** build it from untrusted input). `$agg.sumRaw` is **Postgres-only**: on MongoDB it throws, since a raw SQL fragment isn't portable to a pipeline. Use the typed `$agg.sum(...)` form for cross-driver code.
-
-MongoDB-only — on Postgres these **throw at the `.groupBy()` call** with an actionable message (there is no honest single-scalar `GROUP BY` equivalent):
-
-- `$agg.distinct(field)` · `$agg.floor(field)` · `$agg.first(field)` · `$agg.last(field)`
-
-If you need those shapes on Postgres, drop to `selectRaw` / `havingRaw` with explicit SQL (e.g. `array_agg(DISTINCT …)`, a window function).
-
-### Driver-specific escape hatch
-
-When `$agg.*` can't express it, pass a raw expression in the same slot:
-
-```ts
-.groupBy("category", { total: "SUM(amount)" })          // Postgres
-.groupBy("category", { total: { $sum: "$amount" } })    // MongoDB
-```
-
-Raw strings pass through verbatim. A MongoDB operator object passed on Postgres throws ("not portable to SQL") — keep raw expressions driver-correct.
-
-## Date-bucketed rollups — `.groupByDate(column, unit, aggregates?)`
-
-For time-series reports ("revenue per month", "signups per week") use `groupByDate` instead of grouping on the raw timestamp — it truncates the column to a bucket and groups by the bucket, portably across drivers:
-
-```ts
-import { $agg, $expr } from "@warlock.js/cascade";
-
-const monthly = await Order.query()
-  .whereDateAfter("created_at", startOfYear)
-  .groupByDate("created_at", "month", {
-    revenue: $agg.sum($expr.mul("price", "quantity")),
-    orders: $agg.count(),
-  })
-  .orderBy("created_at", "asc")
-  .get();
-// each row: { created_at: <bucket start>, revenue, orders }
-```
-
-`unit` is `"day" | "week" | "month" | "year"`. The bucketed value comes back under the **column's own name** (`created_at` above). The optional third argument is the same aggregates object as the two-arg `groupBy` (`$agg.*` helpers or driver-native raw expressions). Cross-driver: Postgres emits `date_trunc('<unit>', "column")`; MongoDB emits `{ $dateTrunc: { date: "$column", unit } }` in the `$group` `_id`. Calling `groupByDate` with no aggregates buckets and groups without computing any.
-
-## `.having(...)` — filter groups by a computed aggregate
-
-`.where()` filters rows *before* grouping (cheap, uses indexes). `.having()` filters *after* aggregation, by the alias you defined:
-
-```ts
-const big = await Order.query()
-  .groupBy("category", { total: $agg.sum("amount") })
-  .having("total", ">", 1000)
-  .get();
-```
-
-Works identically on both drivers. (Internally Postgres can't reference a SELECT alias in `HAVING`, so Cascade substitutes the underlying expression for you.) `having` accepts the same shapes as `where`: `having("total", 1000)`, `having("total", ">", 1000)`, `having({ total: 1000, orders: 5 })`. A `having()` on a **grouped column** (not an aggregate alias) is left as a plain column filter.
-
-## OrderBy on aggregates
-
-```ts
-await Order.query()
-  .groupBy("category", { revenue: $agg.sum("amount") })
-  .orderBy("revenue", "desc")
-  .get();
-```
-
-The `orderBy` reference matches the alias from the aggregates object.
-
-## Pipeline stages — `.unwind()` / `.addFields()` / pipeline `join()` (MongoDB)
-
-```ts
-// One row per tag, then filter the tags (stages run in call order)
-const rows = await Post.query().unwind("tags").where("tags", "news").lean().get();
-
-// Keep posts with no tags; record each tag's position
-await Post.query().unwind("tags", { preserveNullAndEmptyArrays: true, includeArrayIndex: "position" }).get();
-
-// Computed field, existing fields kept
-await Post.query().addFields({ score: { $add: ["$likes", "$shares"] } }).orderBy("score", "desc").get();
-
-// Pipeline $lookup
-await Post.query().join({ table: "comments", localField: "id", foreignField: "postId",
-  alias: "approved", pipeline: [{ $match: { approved: true } }] }).lean().get();
-```
-
-`unwind()` returns several rows for one stored document. Use `.lean()` when you only read them. `addFields` expressions are raw aggregation expressions: write them in code, never from request data. Computed columns in the output also work with `selectRaw({ alias: expr })` (`$project`). There is no `$facet` method yet.
-
-Raw stages: `joinRaw({ $lookup: { from, let, pipeline, as } })` (or an array of stages) is emitted verbatim in call order. `raw((pipeline) => [...pipeline, { $sample: { size: 5 } }])` gets the pipeline built so far; return a new array or mutate it and return nothing. Anything else (a SQL string, a non-stage object) throws `UnsupportedQueryOperationError`. Build these in code, never from request data.
-
-**Postgres:** `unwind()` and `addFields()` throw `UnsupportedQueryOperationError` (`operation`, `driver`) when you call them. They are never dropped without an error. Use `selectRaw` with `jsonb_array_elements()` / `unnest()`, or a related table, instead.
-
-## Gotchas
-
-- **`where` vs `having`.** Row filters go in `.where()` (before grouping, index-friendly); aggregate filters go in `.having()`.
-- **Empty sets.** Scalar terminators return `0` on zero rows (above). For *grouped* reports, a group with no rows simply doesn't appear — a report over an empty range returns `[]`, not a row of zeros.
-- **Don't `.all()` then `array.reduce`.** Always push aggregates to the database.
-
-## See also
-
-- [`@warlock.js/cascade/query-data/SKILL.md`](@warlock.js/cascade/query-data/SKILL.md) — the broader query vocabulary
-- [`@warlock.js/cache/use-cached-hof/SKILL.md`](@warlock.js/cache/use-cached-hof/SKILL.md) — caching expensive aggregate results
+---
+name: aggregate-data
+description: 'Compute aggregates over a query — scalar `.count()` / `.sum(field)` / `.avg` / `.min` / `.max`, plus grouped rollups via the two-arg `.groupBy(fields, { alias: $agg.* })`, portable date-bucketing via `.groupByDate(col, unit, aggregates?)`, the `$agg` helpers (including expression-aware `$agg.sum($expr.mul("price","quantity"))` / `$agg.sumRaw`), and `.having(alias, op, value)` on computed aggregates, plus MongoDB pipeline stages `.unwind(field, options?)` / `.addFields(fields)` / pipeline-form `join()` (`UnsupportedQueryOperationError` on Postgres). Triggers: `.unwind`, `.addFields`, `.joinRaw`, `.raw`, `$unwind`, `$lookup`, `.count`, `.sum`, `.avg`, `.min`, `.max`, `.groupBy`, `.groupByDate`, `.having`, `$agg`, `$agg.sum`, `$agg.sumRaw`, `$agg.count`, `$expr`, `$expr.mul`, `$expr.col`, `$expr.lit`; "monthly revenue report", "revenue per month", "X per category", "group by status", "sum price times quantity", "dashboard rollup"; typical import `import { Model, $agg, $expr } from "@warlock.js/cascade"`. Skip: row queries — `@warlock.js/cascade/query-data/SKILL.md`; cached aggregates — `@warlock.js/cache/use-cached-hof/SKILL.md`; competing tools raw SQL `GROUP BY`, `mongoose aggregate`, `prisma` `groupBy`.'
+---
+
+# Use aggregates and groupBy
+
+Cascade's query builder isn't only for finding records — it crunches numbers too. The same calls run on MongoDB and Postgres.
+
+## Scalar aggregates
+
+```ts
+const total      = await Order.count();                  // count is static on the model
+const revenue    = await Order.query().sum("total");
+const avgTicket  = await Order.query().avg("total");
+const cheapest   = await Order.query().min("total");
+const priciest   = await Order.query().max("total");
+
+// Filtered
+const monthRevenue = await Order.query()
+  .whereDateAfter("created_at", startOfMonth)
+  .sum("total");
+```
+
+Each returns a single number (`Promise<number>`). Only `count` is a static shortcut on the model; `sum` / `avg` / `min` / `max` (and the date helpers) are query-builder methods — reach them via `Order.query()` or chain off `Order.where(...)`. Date filters take a single date: `whereDate(field, value)` (exact day, time ignored), `whereDateAfter` / `whereDateBefore` (one-sided), `whereDateBetween(field, [a, b])` (range) — there is no 3-arg `whereDate(field, op, value)`. By Cascade convention the scalar terminators return **`0` on zero rows — not `null`** — so you can use the result directly without a null guard.
+
+## Grouped rollups — two-arg `groupBy(fields, aggregates)`
+
+To compute aggregates *per group*, pass a second argument to `groupBy`: an object mapping output aliases to aggregate expressions. Build the expressions with the `$agg` helpers:
+
+```ts
+import { $agg } from "@warlock.js/cascade";
+
+const stats = await Order.query()
+  .groupBy("category", {
+    total: $agg.sum("amount"),
+    orders: $agg.count(),
+    avg: $agg.avg("amount"),
+  })
+  .get();
+// each row: { category, total, orders, avg }
+```
+
+`fields` is a string or string array (`groupBy(["status", "country"], {...})` groups by each combination). Single-arg `groupBy("category")` / `groupBy(["a","b"])` groups **without** computing aggregates.
+
+### `$agg` helpers — six cross-driver, four MongoDB-only
+
+Cross-driver (identical call on MongoDB **and** Postgres):
+
+- `$agg.count()` · `$agg.countDistinct(field)` · `$agg.sum(input)` · `$agg.sumRaw(expression)` · `$agg.avg(field)` · `$agg.min(field)` · `$agg.max(field)`
+- `$agg.countDistinct(field)` counts distinct values per group: Postgres `COUNT(DISTINCT col)`; MongoDB `$addToSet` in `$group` finalized with `$size` in the renaming `$project`.
+
+### Summing a computed expression — `$agg.sum(expr)` / `$agg.sumRaw`
+
+`$agg.sum` accepts either a bare column name (`$agg.sum("amount")`, unchanged) **or** a typed, cross-driver column expression so you can sum a computed value like `price * quantity` without dropping to raw SQL. Build the expression with the `$expr` combinators (grouped under one object, like `$agg`): `$expr.col` / `$expr.lit` / `$expr.mul` / `$expr.add` / `$expr.sub` / `$expr.div`.
+
+```ts
+import { $agg, $expr } from "@warlock.js/cascade";
+
+const revenue = await OrderItem.query()
+  .groupBy("product_id", {
+    revenue: $agg.sum($expr.mul("price", "quantity")),                       // SUM(price * quantity)
+    net:     $agg.sum($expr.mul($expr.sub($expr.lit(1), "discount"), "price")),// SUM((1 - discount) * price)
+  })
+  .get();
+```
+
+Cross-driver: Postgres emits `SUM(("price" * "quantity"))`, MongoDB emits `{ $sum: { $multiply: ["$price", "$quantity"] } }`. Column names flow through the driver's identifier-quoting path — they're never string-interpolated. The bare-string form (`$agg.sum("amount")`) produces a byte-for-byte-identical payload to before, so existing call sites are unchanged.
+
+When the typed combinators can't express what you need, reach for the raw escape hatch `$agg.sumRaw("price * quantity * (1 - discount)")` — the string is emitted verbatim (**never** build it from untrusted input). `$agg.sumRaw` is **Postgres-only**: on MongoDB it throws, since a raw SQL fragment isn't portable to a pipeline. Use the typed `$agg.sum(...)` form for cross-driver code.
+
+MongoDB-only — on Postgres these **throw at the `.groupBy()` call** with an actionable message (there is no honest single-scalar `GROUP BY` equivalent):
+
+- `$agg.distinct(field)` · `$agg.floor(field)` · `$agg.first(field)` · `$agg.last(field)`
+
+If you need those shapes on Postgres, drop to `selectRaw` / `havingRaw` with explicit SQL (e.g. `array_agg(DISTINCT …)`, a window function).
+
+### Driver-specific escape hatch
+
+When `$agg.*` can't express it, pass a raw expression in the same slot:
+
+```ts
+.groupBy("category", { total: "SUM(amount)" })          // Postgres
+.groupBy("category", { total: { $sum: "$amount" } })    // MongoDB
+```
+
+Raw strings pass through verbatim. A MongoDB operator object passed on Postgres throws ("not portable to SQL") — keep raw expressions driver-correct.
+
+## Date-bucketed rollups — `.groupByDate(column, unit, aggregates?)`
+
+For time-series reports ("revenue per month", "signups per week") use `groupByDate` instead of grouping on the raw timestamp — it truncates the column to a bucket and groups by the bucket, portably across drivers:
+
+```ts
+import { $agg, $expr } from "@warlock.js/cascade";
+
+const monthly = await Order.query()
+  .whereDateAfter("created_at", startOfYear)
+  .groupByDate("created_at", "month", {
+    revenue: $agg.sum($expr.mul("price", "quantity")),
+    orders: $agg.count(),
+  })
+  .orderBy("created_at", "asc")
+  .get();
+// each row: { created_at: <bucket start>, revenue, orders }
+```
+
+`unit` is `"day" | "week" | "month" | "year"`. The bucketed value comes back under the **column's own name** (`created_at` above). The optional third argument is the same aggregates object as the two-arg `groupBy` (`$agg.*` helpers or driver-native raw expressions). Cross-driver: Postgres emits `date_trunc('<unit>', "column")`; MongoDB emits `{ $dateTrunc: { date: "$column", unit } }` in the `$group` `_id`. Calling `groupByDate` with no aggregates buckets and groups without computing any.
+
+## `.having(...)` — filter groups by a computed aggregate
+
+`.where()` filters rows *before* grouping (cheap, uses indexes). `.having()` filters *after* aggregation, by the alias you defined:
+
+```ts
+const big = await Order.query()
+  .groupBy("category", { total: $agg.sum("amount") })
+  .having("total", ">", 1000)
+  .get();
+```
+
+Works identically on both drivers. (Internally Postgres can't reference a SELECT alias in `HAVING`, so Cascade substitutes the underlying expression for you.) `having` accepts the same shapes as `where`: `having("total", 1000)`, `having("total", ">", 1000)`, `having({ total: 1000, orders: 5 })`. A `having()` on a **grouped column** (not an aggregate alias) is left as a plain column filter.
+
+## OrderBy on aggregates
+
+```ts
+await Order.query()
+  .groupBy("category", { revenue: $agg.sum("amount") })
+  .orderBy("revenue", "desc")
+  .get();
+```
+
+The `orderBy` reference matches the alias from the aggregates object.
+
+## Pipeline stages — `.unwind()` / `.addFields()` / pipeline `join()` (MongoDB)
+
+```ts
+// One row per tag, then filter the tags (stages run in call order)
+const rows = await Post.query().unwind("tags").where("tags", "news").lean().get();
+
+// Keep posts with no tags; record each tag's position
+await Post.query().unwind("tags", { preserveNullAndEmptyArrays: true, includeArrayIndex: "position" }).get();
+
+// Computed field, existing fields kept
+await Post.query().addFields({ score: { $add: ["$likes", "$shares"] } }).orderBy("score", "desc").get();
+
+// Pipeline $lookup
+await Post.query().join({ table: "comments", localField: "id", foreignField: "postId",
+  alias: "approved", pipeline: [{ $match: { approved: true } }] }).lean().get();
+```
+
+`unwind()` returns several rows for one stored document. Use `.lean()` when you only read them. `addFields` expressions are raw aggregation expressions: write them in code, never from request data. Computed columns in the output also work with `selectRaw({ alias: expr })` (`$project`). There is no `$facet` method yet.
+
+Raw stages: `joinRaw({ $lookup: { from, let, pipeline, as } })` (or an array of stages) is emitted verbatim in call order. `raw((pipeline) => [...pipeline, { $sample: { size: 5 } }])` gets the pipeline built so far; return a new array or mutate it and return nothing. Anything else (a SQL string, a non-stage object) throws `UnsupportedQueryOperationError`. Build these in code, never from request data.
+
+**Postgres:** `unwind()` and `addFields()` throw `UnsupportedQueryOperationError` (`operation`, `driver`) when you call them. They are never dropped without an error. Use `selectRaw` with `jsonb_array_elements()` / `unnest()`, or a related table, instead.
+
+## Gotchas
+
+- **`where` vs `having`.** Row filters go in `.where()` (before grouping, index-friendly); aggregate filters go in `.having()`.
+- **Empty sets.** Scalar terminators return `0` on zero rows (above). For *grouped* reports, a group with no rows simply doesn't appear — a report over an empty range returns `[]`, not a row of zeros.
+- **Don't `.all()` then `array.reduce`.** Always push aggregates to the database.
+
+## See also
+
+- [`@warlock.js/cascade/query-data/SKILL.md`](@warlock.js/cascade/query-data/SKILL.md) — the broader query vocabulary
+- [`@warlock.js/cache/use-cached-hof/SKILL.md`](@warlock.js/cache/use-cached-hof/SKILL.md) — caching expensive aggregate results