@alfe.ai/openclaw-chat 0.9.15 → 0.9.16

package/dist/plugin.d.cts

@@ -472,6 +472,10 @@ interface RunEventGate {
  * Isolation is preserved: turns to a daemon are serialised
  * (`enqueueAgentTurn`) and the listener is torn down before the next turn
  * dispatches, so the first relevant event locks onto THIS turn's main run.
+ * For callers that supply an idempotency key the gate is instead PRE-ARMED
+ * with that service run id (see `resolveRequestedRunId` / `withReplyRunId`,
+ * which seed the same value as the runtime's own run id), so no lock-on step
+ * is needed and only the service-owned run is ever admitted.
  * Concurrent heartbeat/cron runs and subagent / side-question runs carry a
  * different `runId` and are excluded — exactly the leakage the gate exists to
  * prevent. When a run IS control-UI-visible and both keys are present, a

package/dist/plugin.d.ts

@@ -472,6 +472,10 @@ interface RunEventGate {
  * Isolation is preserved: turns to a daemon are serialised
  * (`enqueueAgentTurn`) and the listener is torn down before the next turn
  * dispatches, so the first relevant event locks onto THIS turn's main run.
+ * For callers that supply an idempotency key the gate is instead PRE-ARMED
+ * with that service run id (see `resolveRequestedRunId` / `withReplyRunId`,
+ * which seed the same value as the runtime's own run id), so no lock-on step
+ * is needed and only the service-owned run is ever admitted.
  * Concurrent heartbeat/cron runs and subagent / side-question runs carry a
  * different `runId` and are excluded — exactly the leakage the gate exists to
  * prevent. When a run IS control-UI-visible and both keys are present, a

package/dist/plugin2.cjs

@@ -2284,6 +2284,10 @@ function getAgentApiClient(apiKeyOverride) {
 * Isolation is preserved: turns to a daemon are serialised
 * (`enqueueAgentTurn`) and the listener is torn down before the next turn
 * dispatches, so the first relevant event locks onto THIS turn's main run.
+* For callers that supply an idempotency key the gate is instead PRE-ARMED
+* with that service run id (see `resolveRequestedRunId` / `withReplyRunId`,
+* which seed the same value as the runtime's own run id), so no lock-on step
+* is needed and only the service-owned run is ever admitted.
 * Concurrent heartbeat/cron runs and subagent / side-question runs carry a
 * different `runId` and are excluded — exactly the leakage the gate exists to
 * prevent. When a run IS control-UI-visible and both keys are present, a

package/dist/plugin2.js

@@ -2284,6 +2284,10 @@ function getAgentApiClient(apiKeyOverride) {
 * Isolation is preserved: turns to a daemon are serialised
 * (`enqueueAgentTurn`) and the listener is torn down before the next turn
 * dispatches, so the first relevant event locks onto THIS turn's main run.
+* For callers that supply an idempotency key the gate is instead PRE-ARMED
+* with that service run id (see `resolveRequestedRunId` / `withReplyRunId`,
+* which seed the same value as the runtime's own run id), so no lock-on step
+* is needed and only the service-owned run is ever admitted.
 * Concurrent heartbeat/cron runs and subagent / side-question runs carry a
 * different `runId` and are excluded — exactly the leakage the gate exists to
 * prevent. When a run IS control-UI-visible and both keys are present, a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alfe.ai/openclaw-chat",
-  "version": "0.9.15",
+  "version": "0.9.16",
   "description": "OpenClaw chat plugin for Alfe — web widget and mobile app channels",
   "type": "module",
   "main": "./dist/plugin.js",
@@ -28,7 +28,7 @@
   ],
   "dependencies": {
     "@alfe.ai/agent-api-client": "^0.17.1",
-    "@alfe.ai/chat": "^0.0.18",
+    "@alfe.ai/chat": "^0.0.19",
     "@alfe.ai/config": "^0.4.1",
     "@alfe.ai/openclaw-plugin-kit": "0.2.0"
   },