@uns-kit/cli 3.0.35 → 3.0.37

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uns-kit/cli",
-  "version": "3.0.35",
+  "version": "3.0.37",
   "description": "Command line scaffolding tool for UNS applications",
   "type": "module",
   "license": "MIT",
@@ -26,14 +26,14 @@
   ],
   "dependencies": {
     "azure-devops-node-api": "^15.1.2",
-    "@uns-kit/core": "3.0.35"
+    "@uns-kit/core": "3.0.37"
   },
   "unsKitPackages": {
-    "@uns-kit/core": "3.0.35",
-    "@uns-kit/api": "3.0.35",
-    "@uns-kit/cron": "3.0.35",
-    "@uns-kit/database": "3.0.35",
-    "@uns-kit/assistant-workflow": "3.0.35"
+    "@uns-kit/core": "3.0.37",
+    "@uns-kit/api": "3.0.37",
+    "@uns-kit/cron": "3.0.37",
+    "@uns-kit/database": "3.0.37",
+    "@uns-kit/assistant-workflow": "3.0.37"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json",

package/templates/default/AGENTS.md

@@ -24,6 +24,8 @@ Pointers for AI/code-assist tools when working in this generated project.
 
 ## UNS Kit dependency upgrades
 
+- When crossing SDK3.0.37, inspect actual ownership wiring, HTTP/cron cleanup and accepted asynchronous effects. Opt-in applications defer discovery until handlers are prepared, declare readiness explicitly, and transfer bounded versioned application state when unfinished windows/sessions affect results. API-only owners use `prepareHandover`, not a fake MQTT data proxy. Never advertise stateful capability from a dependency version alone; follow `MIGRATIONS.md`.
+
 - When crossing `<3.0.32` to `>=3.0.32`, existing services remain unchanged. Enabling a Runtime MQTT outbox on an authorized process group requires the separate reviewed protocol3 transition and shared capability declaration. Preserve input/output journals, stop admission and drain accepted input before stopping the publisher on rollback, and block restoration on pending output or unknown outcomes. Never add application-specific Controller rules.
 
 - When crossing `<3.0.31` to `>=3.0.31`, ordinary services remain unchanged. Optional Runtime-managed MQTT outboxes require explicit `output.publishQueue.storage: runtime`, a trusted private per-Controller external mount and matching backup support. Preserve schema1 queues; restoring managed state requires a stopped source and an empty offline target. Read the version-bounded migration before enabling it.
@@ -31,6 +33,7 @@ Pointers for AI/code-assist tools when working in this generated project.
 - When crossing `<3.0.29` to `>=3.0.29`, configuration-owned process groups opt into shared protocol2/policy4. Keep business resources in the app, bind immutable snapshots and journal generations, use reviewed generation/version transitions, and preserve old journals/policies. Ordinary services and existing file groups need no migration.
 
 - Before changing any `@uns-kit/*` version, record the installed source version and intended target version.
+- When crossing SDK3.0.36, preserve absent units and gate background publications with isActive() until ownership. Mixed old/new state formats refuse before freeze; use a reviewed initial cold upgrade, never bypass compatibility.
 - When opting into SDK 3.0.35 state-preserving MQTT handover, declare protocol2 and per-proxy semantic contracts. Never infer compatibility from package version or matching paths. Use a reviewed reverse handover for return ownership; a cold restart cannot recover counter baselines from RAM. See the version-bounded migration and SDK example.
 - After installing the target version, read `node_modules/@uns-kit/core/MIGRATIONS.md` and apply every migration whose version boundary is crossed. Do not apply unrelated migrations.
 - When crossing `<2.0.71` to `>=2.0.71`, inspect MQTT proxy ownership and follow the documented shutdown migration. Process-owned and standalone proxies have different shutdown paths.