@zksecurity/slack-events 0.2.0 → 0.2.1

package/README.md

@@ -73,7 +73,7 @@ slack-events history C012345 --limit 50 --cursor NEXT_CURSOR
 slack-events thread C012345 1788881468.871969 --limit 50
 slack-events file F012345
 slack-events download F012345 ./attachment.pdf
-slack-events listen --resolve
+slack-events listen
 ```
 
 Use `users` and `channels` to discover IDs before making individual reads. They return Slack JSON with `members` or `channels` arrays containing IDs and names. `channels` includes public/private channels and direct/group conversations available to your user grant. Follow `response_metadata.next_cursor` with `--cursor` until it is empty; each call returns one page, and `--limit` accepts 1-200. The existing `list` command lists feed subscriptions, not Slack conversations.
@@ -87,7 +87,7 @@ subscriber's user grant, refuses to overwrite existing paths, and writes mode
 0600. External files without a Slack-hosted download are unsupported. A failed
 transfer may leave a partial output file; remove that file before retrying.
 
-`listen --resolve` adds `context.users` / `context.channels` name maps while preserving the original event and cursor. It fetches a complete user and conversation name snapshot in the background at startup and every six hours, caching the entire snapshot in memory until the next successful refresh. Failed refreshes keep the previous snapshot; unknown names fall back to IDs without blocking delivery. Restarting the listener fetches a fresh snapshot. Standalone file shares also get `context.files` metadata, fetched separately with a two-second deadline; failure leaves the original event intact and the files list empty. Use `file` or `download` to retry retrieving the file.
+`listen` adds `context.users` / `context.channels` name maps while preserving the original event and cursor. It fetches a complete user and conversation name snapshot in the background at startup and every six hours, caching the entire snapshot in memory until the next successful refresh. Failed refreshes keep the previous snapshot; unknown names fall back to IDs without blocking delivery. Restarting the listener fetches a fresh snapshot. Standalone file shares also get `context.files` metadata, fetched separately with a two-second deadline; failure leaves the original event intact and the files list empty. Use `file` or `download` to retry retrieving the file.
 No read command changes the ACK cursor. The CLI uses its existing paired feed
 credential; Slack user tokens stay on the server. No bot credential is used.
 

package/dist/cli.js

@@ -4,7 +4,7 @@ import { chmodSync, mkdirSync, readFileSync, writeFileSync, createWriteStream }
 import { homedir } from "node:os";
 import { dirname, join } from "node:path";
 export async function runSlackEventsCli(args) {
-    const usage = `Usage: slack-events pair <server> [code] | listen [--resolve] | ack <committed-cursor> | list | revoke <subscription-id>
+    const usage = `Usage: slack-events pair <server> [code] | listen | ack <committed-cursor> | list | revoke <subscription-id>
   users [--limit N] [--cursor C]      List users and their IDs
   channels [--limit N] [--cursor C]   List conversations and their IDs
   user USER_ID                       Get user profile/name
@@ -100,9 +100,9 @@ Read commands print Slack JSON including pagination cursors. They never ACK even
         return;
     }
     if (command === "listen") {
-        if (args.length > 2 || (args[1] && args[1] !== "--resolve"))
+        if (args.length !== 1)
             throw new Error(usage);
-        await listen(credential, args[1] === "--resolve");
+        await listen(credential);
         return;
     }
     throw new Error(usage);
@@ -136,23 +136,18 @@ async function pairDevice(server) {
     }
     throw new Error("Pairing expired. Run the pairing command again for a new link.");
 }
-async function listen(credential, resolve = false) {
+async function listen(credential) {
     const metadataAbort = new AbortController();
     const names = createNameResolver((operation, cursor) => request(credential.server, `/v1/events/slack/${operation}?${new URLSearchParams({ limit: "200", cursor })}`, { token: credential.token, signal: metadataAbort.signal }));
     const threadRoot = createThreadResolver((channel, ts) => request(credential.server, `/v1/events/slack/message?${new URLSearchParams({ id: channel, ts })}`, { token: credential.token, timeoutMs: 2_000, signal: metadataAbort.signal }));
     let after;
     try {
         for (;;) {
-            if (resolve)
-                void names.refresh();
+            void names.refresh();
             const path = `/v1/events?wait_ms=30000${after === undefined ? "" : `&after=${after}`}`;
             const response = await request(credential.server, path, { token: credential.token });
             const events = Array.isArray(response.events) ? response.events : [];
             for (const event of events) {
-                if (!resolve) {
-                    await writeStdout(`${JSON.stringify(event)}\n`);
-                    continue;
-                }
                 const enriched = names.enrich(requireObject(event));
                 const root = await threadRoot(requireObject(event));
                 if (root) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zksecurity/slack-events",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Pair a terminal with a pi-mom Slack event feed",
   "type": "module",
   "bin": { "slack-events": "bin/slack-events.mjs" },

package/skills/slack-events/SKILL.md

@@ -14,7 +14,7 @@ and user reauthorization before they work.
 ## Reading incoming events
 
 `listen` emits JSONL with `sequence`, stable `eventId`, `teamId`, `eventType`,
-`eventTime`, `receivedAt`, and the inner Slack `event`. `listen --resolve` adds
+`eventTime`, `receivedAt`, and the inner Slack `event`. `listen` adds
 `context.users`, `context.channels`, and file metadata for `file_shared` events.
 For replies, optional `context.threadRoot` supplies the root timestamp, user,
 author name, and text. Root lookups have a two-second deadline and are cached;
@@ -95,7 +95,7 @@ use the authenticated CLI download rather than unauthenticated curl.
 
 ```sh
 slack-events pair https://YOUR-EVENT-HOST
-slack-events listen --resolve
+slack-events listen
 slack-events list
 ```