@uns-kit/cli 3.0.39 → 3.0.41

package/dist/index.js

@@ -524,6 +524,8 @@ const AGENT_MIGRATION_END = "<!-- uns-kit:migrations:end -->";
 const AGENT_MIGRATION_BLOCK = [
     AGENT_MIGRATION_START,
     "## UNS Kit dependency upgrades",
+    "- When crossing `<3.0.41` to `>=3.0.41`, typed null scalar clears require explicit publisher allowNullData and data.valueType string/number. Update readers first; opt-in peers have a distinct handover compatibility hash, ordinary peers remain unchanged. Never replace null with zero, empty text or a missing update.",
+    "- When crossing `<3.0.40` to `>=3.0.40`, async MQTT consumers may opt into managedInput/setInputHandler and bounded RAM publishBackpressure. Review an initial cold upgrade for the changed input compatibility; await all work, preserve failed input and use one retryable SDK signal owner. Supporting hosts must use launch-bound cooperative stop; a legacy PM2 deadline can still force termination. Follow MIGRATIONS.md and the MQTT drain example.",
     "- When crossing `<3.0.39` to `>=3.0.39`, read-only API handlers may explicitly await runReadOnlyRequest(res, work) before their first async step. Drain waits for actual work after disconnect; undeclared/effectful unknown outcomes stay blocked. Do not infer safety from GET/POST. Follow MIGRATIONS.md and the HTTP example.",
     "- When crossing `<3.0.38` to `>=3.0.38`, correlated-v2 MQTT handover uses format3 on both peers. Review the initial stop-before-start SDK upgrade; never bypass mixed-format refusal. Missing or ambiguous input overlap keeps the source active. Reconcile an unknown result under the same operation, and return ownership through a fresh reverse hot handover. Follow `MIGRATIONS.md` and the SDK example.",
     "- When crossing `<3.0.34` to `>=3.0.34`, paired-to-direct retirement is optional: use the shared declared selectors, startup/readiness and retained policy5 contract; stop/drain both old owners before one launch, preserve the input journal, update the backup helper for manifest2 and reconcile unknown outcomes in the same operation.",

package/dist/service-bundle.js

@@ -77,6 +77,8 @@ export function generateAgentsMarkdown(bundle) {
         "",
         "<!-- uns-kit:migrations:start -->",
         "## UNS Kit dependency upgrades",
+        "- When crossing `<3.0.41` to `>=3.0.41`, typed null scalar clears require explicit publisher allowNullData and data.valueType string/number. Update readers first; opt-in peers have a distinct handover compatibility hash, ordinary peers remain unchanged. Never replace null with zero, empty text or a missing update.",
+        "- When crossing `<3.0.40` to `>=3.0.40`, async MQTT consumers may opt into managedInput/setInputHandler and bounded RAM publishBackpressure. Review an initial cold upgrade for the changed input compatibility; await all work, preserve failed input and use one retryable SDK signal owner. Supporting hosts must use launch-bound cooperative stop; a legacy PM2 deadline can still force termination. Follow MIGRATIONS.md and the MQTT drain example.",
         "- When crossing `<3.0.39` to `>=3.0.39`, read-only API handlers may explicitly await runReadOnlyRequest(res, work) before their first async step. Drain waits for actual work after disconnect; undeclared/effectful unknown outcomes stay blocked. Do not infer safety from GET/POST. Follow MIGRATIONS.md and the HTTP example.",
         "- When crossing `<3.0.38` to `>=3.0.38`, correlated-v2 MQTT handover uses format3 on both peers. Review the initial stop-before-start SDK upgrade; never bypass mixed-format refusal. Missing or ambiguous input overlap keeps the source active. Reconcile an unknown result under the same operation, and return ownership through a fresh reverse hot handover. Follow `MIGRATIONS.md` and the SDK example.",
         "- When crossing `<3.0.34` to `>=3.0.34`, paired-to-direct retirement is optional: use the shared declared selectors, startup/readiness and retained policy5 contract; stop/drain both old owners before one launch, preserve the input journal, update the backup helper for manifest2 and reconcile unknown outcomes in the same operation.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uns-kit/cli",
-  "version": "3.0.39",
+  "version": "3.0.41",
   "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.39"
+    "@uns-kit/core": "3.0.41"
   },
   "unsKitPackages": {
-    "@uns-kit/core": "3.0.39",
-    "@uns-kit/api": "3.0.39",
-    "@uns-kit/cron": "3.0.39",
-    "@uns-kit/database": "3.0.39",
-    "@uns-kit/assistant-workflow": "3.0.39"
+    "@uns-kit/core": "3.0.41",
+    "@uns-kit/api": "3.0.41",
+    "@uns-kit/cron": "3.0.41",
+    "@uns-kit/database": "3.0.41",
+    "@uns-kit/assistant-workflow": "3.0.41"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json",

package/templates/cron/AGENTS.md

@@ -21,6 +21,8 @@ Pointers for AI/code-assist tools when working in this generated project.
 - `pnpm run sync-uns-metadata -- --controller-url ... --token ...` -> pulls topics/tags/assets from the controller and regenerates local TS helpers
 
 <!-- uns-kit:migrations:start -->
+- When crossing `<3.0.41` to `>=3.0.41`, typed null scalar clears require explicit publisher allowNullData and data.valueType string/number. Update readers first; opt-in peers have a distinct handover compatibility hash, ordinary peers remain unchanged. Never replace null with zero, empty text or a missing update.
+- When crossing `<3.0.40` to `>=3.0.40`, async MQTT consumers may opt into managedInput/setInputHandler and bounded RAM publishBackpressure. Review an initial cold upgrade for the changed input compatibility; await all work, preserve failed input and use one retryable SDK signal owner. Supporting hosts must use launch-bound cooperative stop; a legacy PM2 deadline can still force termination. Follow MIGRATIONS.md and the MQTT drain example.
 
 ## UNS Kit dependency upgrades
 

package/templates/default/AGENTS.md

@@ -21,6 +21,8 @@ Pointers for AI/code-assist tools when working in this generated project.
 - `pnpm run sync-uns-metadata -- --controller-url ... --token ...` -> pulls topics/tags/assets from the controller and regenerates local TS helpers
 
 <!-- uns-kit:migrations:start -->
+- When crossing `<3.0.41` to `>=3.0.41`, typed null scalar clears require explicit publisher allowNullData and data.valueType string/number. Update readers first; opt-in peers have a distinct handover compatibility hash, ordinary peers remain unchanged. Never replace null with zero, empty text or a missing update.
+- When crossing `<3.0.40` to `>=3.0.40`, async MQTT consumers may opt into managedInput/setInputHandler and bounded RAM publishBackpressure. Review an initial cold upgrade for the changed input compatibility; await all work, preserve failed input and use one retryable SDK signal owner. Supporting hosts must use launch-bound cooperative stop; a legacy PM2 deadline can still force termination. Follow MIGRATIONS.md and the MQTT drain example.
 
 ## UNS Kit dependency upgrades