@reventlessdev/reventless-aws 3.0.0-alpha.221 → 3.0.0-alpha.222

package/CHANGELOG.md

@@ -3,6 +3,22 @@
 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.222 (2026-07-22)
+
+* refactor!: retire the stale "core" vocabulary for platform things ([34e7480](https://github.com/ReventlessDev/reventless-core/commit/34e7480992bd58906a250b0a1ce6ff2c5ba45260))
+
+### BREAKING CHANGES
+
+* the built-in extension point is renamed Core.Plugin ->
+Platform.Plugin. This replaces the CorePluginExtPointCmdTopic SQS queue
+with PlatformPluginExtPointCmdTopic (a replacement, not an update) and
+breaks every already-deployed plugin's connection until redeployed.
+Wipe the alpha stack and redeploy fresh rather than migrating.
+
+Build clean; 1349 tests green (interop 50, core 518, local 501, aws 280).
+
+
+
 # 3.0.0-alpha.221 (2026-07-22)
 
 ### Features

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/reventless-aws",
-  "version": "3.0.0-alpha.221",
+  "version": "3.0.0-alpha.222",
   "description": "AWS adapters for Reventless",
   "license": "Apache-2.0",
   "dependencies": {
@@ -8,17 +8,17 @@
     "@aws-sdk/client-cloudfront": "3.970.0",
     "sury": "11.0.0-alpha.4",
     "uuid": "^13.0.0",
-    "@reventlessdev/rescript-effect": "0.1.0-alpha.30",
     "@reventlessdev/rescript-aws-sdk": "2.2.0-alpha.24",
-    "@reventlessdev/rescript-jest": "1.0.0-alpha.9",
     "@reventlessdev/rescript-pulumi-aws": "2.4.0-alpha.57",
+    "@reventlessdev/rescript-effect": "0.1.0-alpha.30",
+    "@reventlessdev/rescript-jest": "1.0.0-alpha.9",
     "@reventlessdev/rescript-pulumi-pulumi": "2.3.0-alpha.17",
-    "@reventlessdev/reventless-core": "3.0.0-alpha.175",
-    "@reventlessdev/reventless-infra": "3.0.0-alpha.103",
-    "@reventlessdev/reventless-postgres": "3.0.0-alpha.39",
-    "@reventlessdev/reventless-spec": "3.0.0-alpha.80",
     "@reventlessdev/rescript-uuid": "1.1.0-alpha.17",
-    "@reventlessdev/reventless-interop": "3.0.0-alpha.28"
+    "@reventlessdev/reventless-core": "3.0.0-alpha.176",
+    "@reventlessdev/reventless-postgres": "3.0.0-alpha.40",
+    "@reventlessdev/reventless-interop": "3.0.0-alpha.29",
+    "@reventlessdev/reventless-infra": "3.0.0-alpha.104",
+    "@reventlessdev/reventless-spec": "3.0.0-alpha.80"
   },
   "devDependencies": {
     "rescript": "12.3.0",

package/src/Platform.res

@@ -234,7 +234,7 @@ module MakeWithConfig = (
 
   // Populate apiConfig with both domain and platform API references.
   // In platform/monolithic mode, platformApi starts as domainApi and is updated
-  // by deployPlatform/makePlatform once the core API resource is created (split mode).
+  // by deployPlatform/makePlatform once the platform API resource is created (split mode).
   let () = apiConfigRef := Some({
     domainApi: domainApi,
     domainApiRole: domainApiRole,
@@ -980,7 +980,7 @@ module MakeWithConfig = (
     }
   }
 
-  // In split mode, create a dedicated core AppSync API and push the core schema.
+  // In split mode, create a dedicated platform AppSync API and push the platform schema.
   // In unified mode, makePlatform is a no-op (schema stitching handled by events).
   let makePlatform = (~version, ~plugins: array<module(PluginMaker)>) => {
     log.info(~comp="Platform", `v${version}`)

package/src/adapter/Mcp/MCP_Lambda.res

@@ -102,11 +102,11 @@ let generateConfig = (
   {serverName, serverVersion, tools, resources, eventHistoryResources}
 }
 
-/** Generate the core-only MCP config for split mode.
-    Contains only core administrative tools (Plugin_Activate, Plugin_Deactivate, Clone)
-    and core resources (Plugin, Plugins). No plugin-contributed entries.
+/** Generate the platform-only MCP config for split mode.
+    Contains only platform administrative tools (Plugin_Activate, Plugin_Deactivate, Clone)
+    and platform resources (Plugin, Plugins). No plugin-contributed entries.
 
-    The commandTopicArns and queryDbTableNames must map core field names to their
+    The commandTopicArns and queryDbTableNames must map platform field names to their
     corresponding AWS resource ARNs/names. When Lambda Function URL deployment is
     available (Step 13), these will be wired from Pulumi stack outputs. */
 let generateAdminConfig = (

package/src/adapter/Runtime/AdminEventCollectorEntryPoint.mjs

@@ -6,7 +6,7 @@
 //
 // {
 //   "queueUrl":                       string  // SQS URL of the EventCollector this Lambda drains
-//   "pluginExtensionPointCmdTopicUrl":string  // SQS URL of CorePluginExtPoint cmd topic (admin's Plugin EP)
+//   "pluginExtensionPointCmdTopicUrl":string  // SQS URL of PlatformPluginExtPoint cmd topic (admin's Plugin EP)
 //   "eventTopicArn":                  string  // SNS ARN the EP's outgoing events publish to ("NOT_AVAILABLE" if none)
 //   "pluginReadModelTableName":       string  // DynamoDB table for Plugin RM (used by QueryEngine.scan)
 //   "pluginSchemaPersistenceTableName":string // DynamoDB table holding deploy-time SDL fragments
@@ -30,7 +30,7 @@
 //   "connectExtension": {                      // The auto-included PluginConnectExtension entry; null for admin Lambda
 //     "specModule":         string,
 //     "mappingsModule":     string,
-//     "extensionPointName": string             // service key for incomingConnectExtensionEventHandlers (e.g. "Core.Plugin")
+//     "extensionPointName": string             // service key for incomingConnectExtensionEventHandlers (e.g. "Platform.Plugin")
 //   } | null,
 //   "extensions": [                            // User-declared extensions — wired into incoming/outgoing dicts at cold start
 //     {

package/src/plugin/heartbeat/HeartbeatRunner_CloudWatchEvents.res

@@ -14,7 +14,7 @@ let make: ReventlessCore.Heartbeat_Adapter.runnerMaker<runtimeParts> = (
     EventRule.make(
       ~name=Pulumi.Pulumi.getStackName() ++ ("-" ++ name),
       ~args={
-        description: "Send a heartbeat to the Core Plugin ExtensionPoint"->Pulumi.Input.make,
+        description: "Send a heartbeat to the Platform Plugin ExtensionPoint"->Pulumi.Input.make,
         scheduleExpression: EventRule.ScheduleExpression.every(timeout->Minutes),
         tags: AWS.Tags.make(
           ~name=Pulumi.Pulumi.getStackName() ++ ("-" ++ name),
@@ -29,14 +29,14 @@ let make: ReventlessCore.Heartbeat_Adapter.runnerMaker<runtimeParts> = (
 
   let lambda = runtime.parts.lambda
   let lambdaRole = runtime.parts.lambdaRole
-  let coreSqsQueue = remoteChannel.resources->Util_SQS.findResolvedResource
+  let platformSqsQueue = remoteChannel.resources->Util_SQS.findResolvedResource
 
-  // Grant sqs:SendMessage on the Core Plugin ExtensionPoint command topic at
-  // TOP LEVEL. Previously this RolePolicy was created inside the
+  // Grant sqs:SendMessage on the Platform Plugin ExtensionPoint command topic
+  // at TOP LEVEL. Previously this RolePolicy was created inside the
   // `Pulumi.Output.apply` below — and a resource created inside an apply
   // callback does not reliably register with the engine, which intermittently
-  // left the heartbeat Lambda without this grant (IAM AccessDenied:
-  // `sqs:sendmessage on CorePluginExtPointCmdTopic`). `coreSqsQueue.urn` is an
+  // left the heartbeat Lambda without this grant (IAM AccessDenied on the
+  // extension point's command-topic queue). `platformSqsQueue.urn` is an
   // already-resolved ARN string from the remote channel and `lambdaRole.id` an
   // Output, so neither needs an apply. Mirrors the EC `pta` grant fix — see
   // docs/analysis/ec-publish-to-aggregates-grant-broken.md.
@@ -48,7 +48,7 @@ let make: ReventlessCore.Heartbeat_Adapter.runnerMaker<runtimeParts> = (
           sid: "AllowLambdaToSendSQS",
           effect: Allow,
           actions: Action("sqs:SendMessage"),
-          resources: Resource(coreSqsQueue.urn),
+          resources: Resource(platformSqsQueue.urn),
         },
       ],
     )

package/src/plugin/heartbeat/HeartbeatRunner_CloudWatchEvents.res.mjs

@@ -20,7 +20,7 @@ import * as Cloudwatch_EventTarget$PulumiAws from "@reventlessdev/rescript-pulum
 function make(name, remoteChannel, timeout, runtime, opts) {
   let opts$1 = Util_Pulumi$ReventlessCore.ComponentResourceOptions.toCustomResourceOptions(opts);
   let cloudwatchEventRule = new (Aws.cloudwatch.EventRule)(Pulumi.getStack() + ("-" + name), {
-    description: "Send a heartbeat to the Core Plugin ExtensionPoint",
+    description: "Send a heartbeat to the Platform Plugin ExtensionPoint",
     scheduleExpression: Primitive_option.some(Cloudwatch_EventRule$PulumiAws.ScheduleExpression.every({
       TAG: "Minutes",
       _0: timeout
@@ -29,12 +29,12 @@ function make(name, remoteChannel, timeout, runtime, opts) {
   }, opts$1);
   let lambda = runtime.parts.lambda;
   let lambdaRole = runtime.parts.lambdaRole;
-  let coreSqsQueue = Util_SQS$ReventlessAws.findResolvedResource(remoteChannel.resources);
+  let platformSqsQueue = Util_SQS$ReventlessAws.findResolvedResource(remoteChannel.resources);
   let heartbeatLambdaSendMessagePolicyDocument = PolicyDocument$PulumiAws.make(undefined, undefined, [{
       Sid: "AllowLambdaToSendSQS",
       Effect: "Allow",
       Action: "sqs:SendMessage",
-      Resource: coreSqsQueue.urn
+      Resource: platformSqsQueue.urn
     }]);
   new (Aws.iam.RolePolicy)(name + "RolePolicy", {
     policy: PolicyDocument$PulumiAws.mergePolicyDocuments(name + "Policy", [

package/src/plugin/runtime/PluginRuntime_Builder.res

@@ -608,7 +608,7 @@ module Make = (
 
     // Plugin EC sqs:SendMessage grants on the aggregate / StateChangeSlice
     // command-topic queues that user extensions publish to. The default
-    // AllowLambdaSendSQS only covers CorePluginExtPointCmdTopic (added because
+    // AllowLambdaSendSQS only covers PlatformPluginExtPointCmdTopic (added because
     // the auto-included Connect extension publishes there), so without this
     // grant every cross-plugin extension's first command publish fails with
     // IAM AccessDenied (e.g. Catalog's Orders_Extension → RecordProductDemand).