@reventlessdev/reventless-core 3.0.0-alpha.207 → 3.0.0-alpha.208

package/CHANGELOG.md

@@ -3,6 +3,13 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# 3.0.0-alpha.208 (2026-08-03)
+
+### Bug Fixes
+
+* **aws:** make the slice callback protocol one declaration, not three ([d49e543](https://github.com/ReventlessDev/reventless-core/commit/d49e543f4715c955c75cec8bd691ee0927b7e2f4))
+
+
 # 3.0.0-alpha.207 (2026-08-03)
 
 ### Bug Fixes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/reventless-core",
-  "version": "3.0.0-alpha.207",
+  "version": "3.0.0-alpha.208",
   "description": "Core package for Reventless framework",
   "license": "Apache-2.0",
   "jest": {
@@ -29,14 +29,14 @@
     "sury": "11.0.0-alpha.4",
     "uuid": "^13.0.0",
     "@reventlessdev/rescript-effect": "0.1.0-alpha.32",
+    "@reventlessdev/rescript-fast-csv": "2.0.0-alpha.1",
+    "@reventlessdev/rescript-jest": "1.0.0-alpha.10",
     "@reventlessdev/rescript-hash-object": "1.2.0-alpha.14",
     "@reventlessdev/rescript-node": "2.0.0-alpha.1",
-    "@reventlessdev/rescript-jest": "1.0.0-alpha.10",
-    "@reventlessdev/rescript-fast-csv": "2.0.0-alpha.1",
     "@reventlessdev/rescript-pulumi-pulumi": "2.3.0-alpha.18",
-    "@reventlessdev/rescript-uuid": "2.0.0-alpha.0",
     "@reventlessdev/rescript-ssh2": "2.0.0-alpha.1",
     "@reventlessdev/reventless-infra": "3.0.0-alpha.124",
+    "@reventlessdev/rescript-uuid": "2.0.0-alpha.0",
     "@reventlessdev/reventless-interop": "3.0.0-alpha.30",
     "@reventlessdev/reventless-spec": "3.0.0-alpha.99"
   },

package/src/components/AutomationSlice/AutomationSlice_Callback.res

@@ -31,6 +31,30 @@ type todoRow = {
   retryCount: int,
 }
 
+/**
+The runtime protocol between a built callback and whoever drives it — the same
+arrangement as `OutboundTranslationSlice_Callback`, and for the same reason. The
+AWS entry point builds callbacks dynamically and has to ascribe a structural type
+at the JS boundary; pointing that ascription at these aliases is what keeps it
+from becoming an unreconcilable second declaration of the shape.
+
+Unlike outbound, phase 1 here takes *raw* envelope JSONs: the callback routes by
+`meta.service` and unwraps `{id, meta, event}` itself, per-source, through the
+registered Mappings.
+*/
+type phase1 = (array<JSON.t>, Reventless.AutomationSlice.context) => unit
+
+/** Phase 2: process all pending items, publishing commands. */
+type phase2 = ReventlessInfra.CommandTopic.publishJsons => promise<unit>
+
+/** The whole protocol as a value, for a driver that holds a built callback and
+    knows nothing of the Spec behind it. */
+type runtime = {
+  todoItems: Dict.t<todoRow>,
+  phase1: phase1,
+  phase2: phase2,
+}
+
 module type T = {
   module Spec: Reventless.AutomationSlice.Spec
   module Automation: Reventless.AutomationSlice.Automation with module Spec := Spec
@@ -40,10 +64,10 @@ module type T = {
 
   /** Phase 1: update TODO list from a batch of raw event JSONs. Internally
       decodes per-source via the registered Mappings. */
-  let phase1: (array<JSON.t>, Reventless.AutomationSlice.context) => unit
+  let phase1: phase1
 
   /** Phase 2: process all pending items, publishing commands via publishJsons. */
-  let phase2: ReventlessInfra.CommandTopic.publishJsons => promise<unit>
+  let phase2: phase2
 }
 
 module Make = (

package/src/components/OutboundTranslationSlice/OutboundTranslationSlice_Callback.res

@@ -22,6 +22,34 @@ type todoRow = {
   lastError?: string,
 }
 
+/**
+The runtime protocol between a built callback and whoever drives it.
+
+Defined here, once, and referenced by every party — `module type T` below, the
+in-process builder, and the AWS entry point, which cannot name `T` because it
+builds callbacks dynamically per `HANDLER_CONFIG` entry and must ascribe a
+structural type at the JS boundary.
+
+That ascription is the reason these aliases exist. A driver that restates the
+shape instead of referencing it becomes a second source of truth that the
+compiler cannot reconcile with this one: when `phase1` gained its `sourceId`,
+the AWS entry point kept passing bare events and nothing complained, because its
+hand-written copy was internally consistent. The mismatch surfaced only at
+runtime, as `undefined` destructured from a tuple that was never a tuple.
+*/
+type phase1<'event> = array<(string, 'event)> => unit
+
+/** Phase 2: translate all pending items, optionally publishing commands. */
+type phase2 = ReventlessInfra.CommandTopic.publishJsons => promise<unit>
+
+/** The whole protocol as a value — what a driver holding a built callback needs,
+    with no knowledge of the Spec it was built from. */
+type runtime<'event> = {
+  todoItems: Dict.t<todoRow>,
+  phase1: phase1<'event>,
+  phase2: phase2,
+}
+
 module type T = {
   module Spec: Reventless.OutboundTranslationSlice.Spec
   module Translation: Reventless.OutboundTranslationSlice.Translation with module Spec := Spec
@@ -32,10 +60,10 @@ module type T = {
   /** Phase 1: update TODO list from a batch of `(sourceId, event)` pairs
       (collect only, no resolve). `sourceId` is the envelope id of the entity the
       event was published for. */
-  let phase1: array<(string, Spec.consumedEvent)> => unit
+  let phase1: phase1<Spec.consumedEvent>
 
   /** Phase 2: translate all pending items, optionally publishing commands via publishJsons. */
-  let phase2: ReventlessInfra.CommandTopic.publishJsons => promise<unit>
+  let phase2: phase2
 }
 
 module Make = (