create-substrat 0.9.0 → 0.9.1

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.99.0';
-const ENGINE_WORKORDER = '^0.10.7';
-const ENGINE_INVOICING = '^0.9.15';
+const SUBSTRAT = '^0.100.0';
+const ENGINE_WORKORDER = '^0.10.8';
+const ENGINE_INVOICING = '^0.9.16';
 const BOUNDARY_LINT = '^0.4.2';
-const DEV_ISSUER = '^0.1.14';
+const DEV_ISSUER = '^0.1.15';
 
 const DOCS = 'https://substrat.net';
 

package/package.json

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

package/template/AGENTS.md

@@ -112,10 +112,14 @@ consumers). Rules 1–5 are enforced mechanically by `boundary-lint`.
    `@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.
+   grant), the impersonation stamp, the PII class, the `operation` the event was emitted
+   from (the exact `invoke()` string) and the `version` the emitting code was deployed as.
+   On all but the PII class, a `null` is a *fact* rather than data you failed to fetch —
+   the payload was erased, the row predates authorization recording, nobody was
+   impersonating, a consumer emitted it (or the row predates the column), no version
+   identity was present — so render it as that. `version` comes from the outbox column
+   only, never the envelope, so this helper is the one way to join an event to the push
+   that wrote it. 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

package/template/src/worker.ts

@@ -73,6 +73,8 @@ export { ConfigDO };
  * `/internal/delete-scope` removes them. Costs nothing while the roster is empty.
  */
 export const SweeperDO = defineScopeSweeperDO<Env>({
+  // #1232: the pass reports the version whose code actually ran (the deploy-injected binding).
+  versionId: (env) => env.SUBSTRAT_VERSION_ID ?? null,
   intervalMs: 120_000,
   host: hostFor,
 });
@@ -102,6 +104,8 @@ const DEV_NODE: Node = {
 };
 
 interface Env {
+  /** Injected at deploy (#1242); absent locally — the sweep record then reads NULL. */
+  SUBSTRAT_VERSION_ID?: string;
   /** One DO per scope — the vertical's only durable store (sandbox-clean). */
   SCOPE: DurableObjectNamespace;
   /** The roster-keeping sweep singleton — the deployment's own timer (#461). */