@burgan-tech/vnext-meta 0.0.67 → 0.0.69-alpha.1

package/features.json

@@ -29,6 +29,12 @@
       "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[]"
+    },
+    "stateStoreTask": {
+      "since": "0.0.64",
+      "status": "stable",
+      "description": "Built-in StateStoreTask (TaskType=17, discriminator 'statestore') that reads and writes a Dapr state store component from the workflow/function pipeline. When the task config omits storeName, the store is resolved from the executing runtime's DAPR_STATE_STORE_NAME configuration value, so each runtime targets its own component with no hard-coded name. Runs through the Execution API like the other Dapr tasks: the StateStoreTaskExecutor performs input/output mapping and delegates a TaskEnvelope to the StateStoreTaskInvoker, which uses DaprClient. Command names mirror the Dapr state API verbs: get (GetStateAndETagAsync; a cache miss returns success with metadata Found=false and null data, so the error boundary is not tripped), set (SaveStateAsync / TrySaveStateAsync when an ETag is supplied, with optional ttlInSeconds TTL, and StateOptions concurrency FirstWrite/LastWrite + consistency Eventual/Strong), and delete (single key via DeleteStateAsync, key list via DeleteBulkStateAsync, or tag/pattern via the Dapr state Query API which requires a query-capable state store). An explicit storeName must be exposed by the Execution sidecar; the repo ships a 'vnext-state' component there for that purpose. All task-supplied keys are stored under the fixed 'custom:' prefix to namespace task-written entries away from engine-owned cache keys sharing the same store.",
+      "schemaPath": "task.type=17"
     }
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@burgan-tech/vnext-meta",
-  "version": "0.0.67",
+  "version": "0.0.69-alpha.1",
   "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,15 @@
 {
   "versions": {
+    "0.0.68": {
+      "schemaVersion": "0.0.49",
+      "releasedAt": "2026-07-02",
+      "releaseNotes": "https://burgan-tech.github.io/vnext-docs/blog/release-v0-0-68"
+    },
+    "0.0.67": {
+      "schemaVersion": "0.0.48",
+      "releasedAt": "2026-06-30",
+      "releaseNotes": "https://burgan-tech.github.io/vnext-docs/blog"
+    },
     "0.0.66": {
       "schemaVersion": "0.0.48",
       "releasedAt": "2026-06-28",