@burgan-tech/vnext-meta 0.0.65 → 0.0.66

package/features.json

@@ -23,6 +23,12 @@
       "apiEndpoints": [
         "POST {domain}/workflows/{workflow}/instances/{instance}/longpoll/ack"
       ]
+    },
+    "stateNotification": {
+      "since": "0.0.63",
+      "status": "stable",
+      "description": "Declarative state-level notifications. A state may declare a notifications[] array; each entry has a type (default 'state' — only 'state' is processed today, 'command' is reserved), an optional rule (compiled to IConditionMapping), and a mapping (compiled to IStateNotificationMapping, same contract as the NotificationTask state channel). After the transition pipeline settles and the instance state/status is finalized and committed, the engine schedules a durable one-shot background job (handler 'state.notify') that rebuilds a ScriptContext from the carried request context (Headers, RouteValues, Body), evaluates each entry's rule (absent rule => always processed; present rule => only entries whose rule returns true), and dispatches the applicable entries through the platform-managed state Dapr binding (vnext-notification-state) off the request thread, so the client response is never blocked. Fires once per settle (not on intermediate auto-chain hops). The state-channel payload is the slim pointer { domain, flow, id, version } — consumers re-fetch full state via the State function. Independent of and backward-compatible with the existing NotificationTask state channel.",
+      "schemaPath": "state.notifications[]"
     }
   }
 }

package/migrations.json

@@ -1,3 +1,15 @@
 {
-  "items": []
+  "items": [
+    {
+      "id": "state-channel-slim-payload",
+      "type": "behavior",
+      "component": "notification",
+      "path": "notificationTask.channels[state]",
+      "since": "0.0.63",
+      "severity": "warning",
+      "title": "State notification channel payload slimmed to a pointer",
+      "description": "The platform-managed 'state' notification channel (NotificationTask state channel and the new state-level notification directive) no longer embeds the full State function output (GetInstanceStateOutput) in the message data. The data payload is now the slim pointer { domain, flow, id, version } inside the CloudEvents envelope; consumers must re-fetch the full state via the State function. Binding metadata and IStateNotificationMapping enrichment are unchanged.",
+      "action": "Update state-channel consumers to treat the message as a change pointer and call the State function for full state instead of reading data.data.* fields."
+    }
+  ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@burgan-tech/vnext-meta",
-  "version": "0.0.65",
+  "version": "0.0.66",
   "description": "vNext Runtime metadata package — version manifest, feature catalog, deprecation registry, and component metadata for offline consumption by Forge Studio, CLI, and domain packages.",
   "main": "index.js",
   "files": [

package/version-manifest.json

@@ -1,5 +1,25 @@
 {
   "versions": {
+    "0.0.66": {
+      "schemaVersion": "0.0.48",
+      "releasedAt": "2026-06-28",
+      "releaseNotes": "https://burgan-tech.github.io/vnext-docs/blog/release-v0-0-66"
+    },
+    "0.0.65": {
+      "schemaVersion": "0.0.47",
+      "releasedAt": "2026-06-25",
+      "releaseNotes": "https://burgan-tech.github.io/vnext-docs/blog"
+    },
+    "0.0.64": {
+      "schemaVersion": "0.0.47",
+      "releasedAt": "2026-06-19",
+      "releaseNotes": "https://burgan-tech.github.io/vnext-docs/blog"
+    },
+    "0.0.63": {
+      "schemaVersion": "0.0.47",
+      "releasedAt": "2026-06-18",
+      "releaseNotes": "https://burgan-tech.github.io/vnext-docs/blog"
+    },
     "0.0.62": {
       "schemaVersion": "0.0.47",
       "releasedAt": "2026-06-18",