create-substrat 0.11.3 → 0.11.5

package/index.js

@@ -36,12 +36,12 @@ const TEMPLATE = join(HERE, 'template');
 // The runtime packages release together off one version line (the changesets `fixed`
 // group), so one constant is right for all of them. Engines do NOT share a line —
 // each versions on its own, so one pin per engine, deliberately.
-const SUBSTRAT = '^0.143.0';
-const ENGINE_WORKORDER = '^0.12.27';
-const ENGINE_INVOICING = '^0.11.27';
+const SUBSTRAT = '^0.145.0';
+const ENGINE_WORKORDER = '^0.12.29';
+const ENGINE_INVOICING = '^0.11.29';
 const BOUNDARY_LINT = '^0.7.0';
-const DEV_ISSUER = '^0.2.25';
-const ATTACHMENT_EXTRACTORS = '^0.2.4';
+const DEV_ISSUER = '^0.2.27';
+const ATTACHMENT_EXTRACTORS = '^0.2.6';
 
 const DOCS = 'https://substrat.net';
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-substrat",
-  "version": "0.11.3",
+  "version": "0.11.5",
   "description": "Scaffold a Substrat vertical — `npm create substrat <dir>`.",
   "license": "Apache-2.0",
   "repository": {

package/template/AGENTS.md

@@ -196,13 +196,18 @@ matter what the operation supports, forget the second and it answers with an
 envelope where it used to answer with an array. That is the case for not
 hand-mounting anything an operation can declare.
 
-**An operation the model describes completely says who writes its handler.** Four
+**An operation the model describes completely says who writes its handler.** These
 shapes are derivable: a `GET` of one row by its id, a `GET` that is a `paged.over` page of the
-entity's own rows behind declared filters, a `PATCH` field bag with `concurrency`, and
-a `DELETE` of a row nothing declares as parent. Declare `derive: 'get'` (or `'list'`,
-`'update'`, `'delete'`) and write no handler: `operationsFor` leaves it out of the map
-it requires and supplies the platform's handler, which checks the declared key first,
-reads and writes only declared columns and emits the declared event. Keep a handler
+entity's own rows behind declared filters, a `PATCH` field bag with `concurrency`, a
+`DELETE` of a row nothing declares as parent, a `POST` that inserts a row every column of
+which comes from the input, the parent its check narrows to, a minted id or the entity's
+declared `stamps`, and, on an entity that declares `archive` or `trash`, its four moves and
+its bin. Declare `derive: 'get'` (or `'list'`, `'update'`, `'delete'`, `'create'`,
+`'archive'`, `'unarchive'`, `'trash'`, `'restore'`, `'trashed'`) and write no handler:
+`operationsFor` leaves it out of the map it requires and supplies the platform's handler,
+which checks the declared key first, reads and writes only declared columns and emits the
+declared event (the bin is checked row by row instead, and a move's event is the kernel's).
+Keep a handler
 only with `authored: '<what the derived one would get wrong here>'`. `defineOperations`
 refuses at module load a derivable operation that declares neither, a `derive` whose
 declaration is not that shape, and an `authored` on an operation nothing could derive.