create-substrat 0.8.3 → 0.8.4

package/index.js

@@ -36,11 +36,11 @@ 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.94.0';
-const ENGINE_WORKORDER = '^0.10.2';
-const ENGINE_INVOICING = '^0.9.10';
-const BOUNDARY_LINT = '^0.2.1';
-const DEV_ISSUER = '^0.1.8';
+const SUBSTRAT = '^0.95.0';
+const ENGINE_WORKORDER = '^0.10.3';
+const ENGINE_INVOICING = '^0.9.11';
+const BOUNDARY_LINT = '^0.3.0';
+const DEV_ISSUER = '^0.1.9';
 
 const DOCS = 'https://substrat.net';
 

package/package.json

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

package/template/AGENTS.md

@@ -108,7 +108,14 @@ consumers). Rules 1–5 are enforced mechanically by `boundary-lint`.
    handler that runs outside the transaction. An integration is never impossible because
    of this rule — it has an answer.
 3. **Never write `_substrat_*` tables.** Reads are fine (timelines are projections);
-   writes forge the audit spine.
+   writes forge the audit spine. Do the read with `readTimeline` / `readHistory` from
+   `@substrat-run/kernel` rather than a `SELECT` of your own: both take an `EntityRef`,
+   page like a list read, and decode the envelope for you. `readHistory` also returns the
+   payload, the authorization chain (which checks the operation passed, and under which
+   grant), the impersonation stamp and the PII class. On the first three, a `null` is a
+   *fact* rather than data you failed to fetch — the payload was erased, the row predates
+   authorization recording, nobody was impersonating — so render it as that. Neither
+   helper checks a permission; you do, before you call it.
 4. **Another module's tables are private.** Never `SELECT` from `workorder_*` etc. — use
    the engine's exported in-scope functions. This is the rule with no runtime equivalent:
    the shortcut *works* and silently welds you to an engine's private schema forever. Need