@akanjs/cli 3.1.0-rc.24 → 3.1.0-rc.26

package/.build-stamp

@@ -1 +1 @@
-bf09952cfa342516d477d043aa7edae07aa3a15412cc50590fcadb0d1d6c0083
+97f9c99b37757e29b66df933d826193b592050f9934def1cb9b2f50d0679aeef

package/guidelines/conventions/conventions.instruction.md

@@ -324,9 +324,10 @@ orchestration in `service`, client state in `store`; `Template` is forms, `Unit`
   `sort: {}` always present. Chain methods validate → mutate → `return this`, never `save()` (the caller saves, so
   `org.removeUser(id).removeInvite(id).save()` composes), with a one-line transition comment above each. Atomic
   counters live on the Model class with the updater callback, returning `!!modifiedCount`; indexes and derived
-  totals go in `static override _onSchema`. **Removal is always soft** and reads see live rows unless
-  `{ withRemoved: true }`. `updateById` / `removeById` fire no hooks — a cascading or `_postRemove` model removes
-  through `remove<Model>(id)`, and `pickAndWrite` writes through the save hooks (`queryRule`).
+  totals go in `static override _onSchema`. **Removal is soft** and reads see live rows unless
+  `{ withRemoved: true }`; the one hard delete is `purge<Filter>` / `purgeMany`, for data past retention.
+  `updateById` / `removeById` fire no hooks — a cascading or `_postRemove` model removes through
+  `remove<Model>(id)`, and `pickAndWrite` writes through the save hooks (`queryRule`).
 - **`<model>.service.ts`** — a few lines: load → chain → `return await ….save()` (keep the `return await`). Side
   effects go in `override async _preUpdate` / `_postCreate`; fire-and-forget is `void`-ed. Load every referenced
   document, then save, then notify. Return `null` / `false` for not allowed or not found; the signal decides

package/guidelines/queryRule/queryRule.instruction.md

@@ -88,8 +88,12 @@ this is the full contract behind them.
 
 ## Soft Removal And The Facade's Writes
 
-- **Removal is always soft** — the framework has no hard delete for a model table, and `delete` is deliberately
-  left unused so it can mean one later. Every read and query-level write sees live rows only (`removedAt IS NULL`).
+- **Removal is soft** — every remove stamps `removedAt`, and every read and query-level write sees live rows only
+  (`removedAt IS NULL`).
+- **`purge<Filter>(...)` / `purgeMany(query)` is the one hard delete**, for data you mean to lose, such as logs past
+  their retention. It deletes every row the query matches, removed rows too (`{ removedAt: q.lt(cutoff) }` clears old
+  removals), and returns the count. The search mirror's rows go with each row, and it runs no hook, cascade or live
+  event and has no undo. It deletes 1,000 rows per statement, and it refuses a query that matches every row.
 - **`{ withRemoved: true }` reaches removed rows**: the third argument of `find` / `findOne` / `findById`
   (projection second, `null` when none), the last of `count` / `exists` / `updateMany`, or inside `updateOne` /
   `updateById`'s options. Without it, a `removedAt` condition only a removed row can meet (`q.exists("removedAt")`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akanjs/cli",
-  "version": "3.1.0-rc.24",
+  "version": "3.1.0-rc.26",
   "sourceType": "module",
   "type": "module",
   "publishConfig": {
@@ -39,7 +39,7 @@
     "@earendil-works/pi-tui": "1.3.0",
     "@inquirer/prompts": "^8.7.3",
     "@tailwindcss/node": "^4.3.3",
-    "akanjs": "3.1.0-rc.24",
+    "akanjs": "3.1.0-rc.26",
     "chalk": "^6.0.1",
     "commander": "^15.0.0",
     "dayjs": "^1.11.23",