@cuylabs/channel-slack 0.5.0 → 0.5.1

package/dist/bolt.js

@@ -528,10 +528,11 @@ function createSlackSocketModeRuntime({
   runtimePolicy = "single-instance",
   serverPingTimeoutMs = DEFAULT_SERVER_PING_TIMEOUT_MS
 }) {
+  const processLockConfigured = lockEnabled && runtimePolicy === "single-instance";
   const lock = acquireSlackSocketModeProcessLock({
     appSlug,
     appToken,
-    enabled: lockEnabled && runtimePolicy === "single-instance",
+    enabled: processLockConfigured,
     ...lockDir ? { lockDir } : {},
     ...logger ? { logger } : {}
   });
@@ -545,8 +546,9 @@ function createSlackSocketModeRuntime({
   logger?.info?.("Slack Socket Mode runtime guard configured", {
     autoReconnectEnabled,
     clientPingTimeoutMs,
-    lockEnabled: Boolean(lock),
     pingPongLoggingEnabled,
+    processLockAcquired: Boolean(lock),
+    processLockConfigured,
     restartGuardEnabled,
     restartGuardMaxWarnings,
     restartGuardWindowMs,

package/docs/concepts/bolt-runtime.md

@@ -29,6 +29,11 @@ that can:
 
 Use `runtime.close()` during shutdown so a process lock is released.
 
+The runtime log reports the SDK-local process lock separately as
+`processLockConfigured` and `processLockAcquired`. These fields describe only
+the SDK file/process lock created by `createSlackSocketModeRuntime`; they do not
+describe a distributed Postgres lock acquired separately.
+
 For distributed deployments, `acquireSlackSocketModePostgresLock` can acquire a
 Postgres advisory lock before starting the Socket Mode app:
 

package/docs/concepts/message-policy.md

@@ -16,6 +16,10 @@ const decision = policy.resolve(activity);
 if (!decision.accepted) return;
 ```
 
+`decision.reason` is intended for host-owned logs, metrics, and audit records.
+For example, a host can distinguish `bot-mentioned` from
+`mentioned-thread-reply` without the SDK choosing log levels or log shape.
+
 ## Channel Message Policy
 
 `messagePolicy` controls passive channel messages:
@@ -27,6 +31,15 @@ if (!decision.accepted) return;
 
 DMs and direct mentions are always accepted unless they are duplicates.
 
+Accepted decisions include one of these reasons:
+
+- `direct-message`: the message came from a DM.
+- `bot-mentioned`: the bot was directly mentioned.
+- `mentioned-thread-reply`: a non-mentioned reply continued a remembered
+  mentioned thread.
+- `allowed-channel`: a passive message matched `allowed-channels`.
+- `any-added-channel`: a passive message matched `any-added-channel`.
+
 ## Thread Reply Policy
 
 `threadReplyPolicy` controls non-mentioned replies inside remembered mentioned

package/docs/recipes/app-mention-handler.md

@@ -19,6 +19,11 @@ app.event("app_mention", async ({ event, client }) => {
   const activity = parseSlackMentionActivity(event);
   const decision = policy.resolve(activity);
   if (!decision.accepted) return;
+  logger.info("Slack message accepted", {
+    channelId: activity.channelId,
+    reason: decision.reason,
+    threadTs: activity.threadTs,
+  });
 
   const answer = await runAgent({
     input: decision.text,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cuylabs/channel-slack",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "SDK-neutral Slack channel primitives for AI agents",
   "type": "module",
   "main": "./dist/index.js",