conduyt 1.63.0 → 1.65.0

package/README.md

@@ -36,6 +36,11 @@ conduyt contacts get <id>               # fetch one contact (carries `revision`)
 conduyt contacts update <id> --first Ann --expected-revision <n>   # PATCH; a contact changed since revision n is refused: 409 contact_changed, exit 1, code and current revision printed
 conduyt contacts collaborators add <contactId> <userId> [--expected-revision <n>]      # POST /contacts/{id}/collaborators; prints { added, revision }
 conduyt contacts collaborators remove <contactId> <userId> [--expected-revision <n>]   # DELETE with a body; prints { removed, revision }; 404 when not a collaborator
+conduyt chat channels                   # GET /chat/channels: your channels; also CREATES your auto-channel memberships the first time
+conduyt chat unread                     # GET /chat/unread: per channel { channelId, unread, soundUnread, newestSeq, latestSeq }
+conduyt chat messages <channelId> [--limit 1-100] [--cursor <messageId>]   # newest first; prints { data, hasMore, nextCursor }; every message carries `seq`; does not move the read marker; a 403 "Not a member of this channel" is retried once after `chat channels`
+conduyt chat mark-read <channelId> <messageId>   # readUpTo: marker moves to that message's seq, forward only (older or foreign message = no-op, exit 0); prints the channel's newest message; same one-retry membership bootstrap
+conduyt notifications list [--page n] [--per-page 1-200]   # prints { data, meta }: meta.latestByType = { type: { latest, count } } over the last 24 h, next to unreadCount / unreadByType
 conduyt deals list --pipeline <id>      # list deals
 conduyt deals list --health-summary --pipeline <id>   # Pipeline health strip for the filtered set (totalOpenDeals, atRiskValue, checks[]); add --health-check stale --health-limit 20 for one check's deals, --health-cursor <nextCursor> to page, --health-rows-only for just the page
 conduyt deals health --pipeline <id> --check needs_action   # GET /deals/inspection: the six checks over open deals; --check adds its deals, --cursor/--offset pages
@@ -48,7 +53,7 @@ conduyt pipelines archive <id> --move-open-deals-to <pipelineId|none> [--expecte
 conduyt pipelines settings-revision   # the account settingsRevision to pass as --expected-settings-revision to archive / delete-stage (409 stale_settings_revision when settings changed since)
 conduyt pipelines restore <id>          # bring an archived pipeline back (last in the menu, never the default; 409 name_taken)
 conduyt pipelines reorder --order id1,id2 --expected-revision id1,id2   # board-menu order in one transaction (409 order_changed prints the current revision); `reorder-stages <pipelineId>` does the same for a pipeline's columns
-conduyt pipelines delete-stage <pipelineId> <stageId> [--move-to <stageId>] [--expected-settings-revision N]   # move the live deals to another stage and delete this one; a stale revision is 409 stale_settings_revision
+conduyt pipelines delete-stage <pipelineId> <stageId> [--move-to <stageId>] [--expected-settings-revision N]   # soft delete: an empty stage always deletes (hidden everywhere, then 404, no restore, name reusable); --move-to re-homes live deals first; 409s print the server message (deals in it, used by N active automation(s), DPP map, pipeline_archived, intake_target, stale_settings_revision); a run parked before the delete fails at that step
 conduyt pipelines rot-days set <pipelineId> 21   # days without activity (1-90) before a deal reads "Stale in stage"; `rot-days get [pipelineId]` reads
 conduyt status-metadata list --stage-id <id>   # the status codes + buckets attached to stages; `get | create | update | delete | import` (update / delete take --expected-updated-at; 409 metadata_changed)
 conduyt status-metadata import --file rows.json --mode replace   # set-based import (max 1000; an item key outside stageId, code, bucket, lifecycleStage, dripEligible, dripTrackName, isTerminal, notes is refused before any request); per-item errors print and exit 1; `--mode replace` with no items is refused unless `--confirm-empty-replace` (it deletes every row). Timeouts: archive 75 s, import and the Mailchimp write / action commands 60 s; on a timeout the server may have applied it, so read the state first

package/dist/index.js

@@ -937,7 +937,7 @@ stageRules
 // isSystem included (a system holding stage automations route deals through; hidden from rep pickers, never won or lost)
 pipelines
     .command("update-stage <pipelineId> <stageId>")
-    .description("Update one stage (PATCH — only the fields you pass change). --is-system marks a system holding stage: automations route deals through it, reps never see it in a picker, and it can never be won or lost")
+    .description("Update one stage (PATCH — only the fields you pass change). --is-system marks a system holding stage: automations route deals through it, reps never see it in a picker, and it can never be won or lost. A soft-deleted stage (`pipelines delete-stage`) answers 404")
     .option("--name <name>", "stage name")
     .option("--color <hex>", "stage colour")
     .option("--is-won <bool>", "true|false — entering this stage closes the deal as won")
@@ -1030,7 +1030,7 @@ pipelines
 }));
 pipelines
     .command("delete-stage <pipelineId> <stageId>")
-    .description("Delete a stage (owner / admin key). Without --move-to the stage must have no deals; with it the live deals move to another stage of the SAME pipeline (same won / lost setting, not a system stage) and the stage is deleted in one transaction. A stage a soft-deleted deal still points at is refused. With --expected-settings-revision the answer is { id, deleted: true, settingsRevision }. Refusals exit 1 with the code printed: stale_settings_revision, pipeline_archived, intake_target (other 409s name the cause)")
+    .description("Soft-delete a stage (owner / admin key). An EMPTY stage can always be deleted, even if deals once used it: the row is kept so deal history and reports keep its name, but it is hidden from every pipeline / stage list, GET / PATCH on it answer 404, there is NO restore in v1, and its name may be reused by a new stage; its stage rule, outcome mappings and status metadata go with it. With --move-to the live deals move to another stage of the SAME pipeline (same won / lost setting, not a system stage) and the stage is deleted in one transaction. With --expected-settings-revision the answer is { id, deleted: true, settingsRevision }. A refusal exits 1 with the server's message printed verbatim and its code when it has one (never retried): deals currently in the stage and no --move-to; 'Cannot delete stage: it is used by N active automation(s) (names). Change their stage or pause them first.' (a published automation uses the stage in an action, trigger, condition or wait-until); the DPP status map selects it; stale_settings_revision, pipeline_archived, intake_target. A --move-to that is not a valid target is a 400. Accepted window: a run parked or in flight before the delete is not tracked; at the step that targets the deleted stage it fails or is skipped with a clear reason in the execution log")
     .option("--move-to <stageId>", "another stage of the same pipeline the live deals move to")
     .option("--expected-settings-revision <n>", "the settingsRevision from `pipelines settings-revision`; refused 409 stale_settings_revision when settings changed since")
     .action(run(async (client, pipelineId, stageId, opts) => {
@@ -3289,6 +3289,66 @@ ai
         Object.assign(body, jsonArg(opts.json, "--json"));
     return client.post("/api/v1/ai/enrich-contact", body);
 }));
+// ---- team chat (app 10-09, live sha 3869c79ba) ----
+const chat = program.command("chat").description("Team chat: unread vector, messages (each carries `seq`), read acknowledgement");
+/** The messages route's membership refusal (403 "Not a member of this channel"); any other 403 (a permission) is not this one. */
+function isMembershipRefusal(err) {
+    return err instanceof Error && /\b403\b/.test(err.message) && /Not a member of this channel/.test(err.message);
+}
+/** `chat unread` lists AUTO channels the caller has no membership row in yet; the messages route answers 403 for them until GET /chat/channels
+ *  creates it. On that one refusal: call /chat/channels ONCE, retry ONCE. A second refusal, or a 403 for any other reason, is the caller's. */
+async function withChatMembership(client, read) {
+    try {
+        return await read();
+    }
+    catch (err) {
+        if (!isMembershipRefusal(err))
+            throw err;
+        await client.get("/api/v1/chat/channels");
+        return read();
+    }
+}
+chat
+    .command("channels")
+    .description("GET /chat/channels: your channels (id, name, kind, members, last message). SIDE EFFECT: also creates your memberships in the account's auto channels (needs-a-hand, new-leads, wins) the first time. `chat messages` and `chat mark-read` do this once for you on a 403 'Not a member of this channel'")
+    .action(run(async (client) => client.get("/api/v1/chat/channels")));
+chat
+    .command("unread")
+    .description("GET /chat/unread: per channel { channelId, unread, soundUnread, newestSeq, latestSeq }; a row can be an AUTO channel you have not opened yet (no membership row: reading it first answers 403, which `chat messages` / `chat mark-read` recover from once). unread is the badge count (auto channels 0 by design); soundUnread counts every channel; newestSeq = seq of the newest message not written by you (null = none), latestSeq the same including panic cards. Read-only")
+    .action(run(async (client) => client.get("/api/v1/chat/unread")));
+chat
+    .command("messages <channelId>")
+    .description("List a channel's messages, newest first (GET /chat/channels/{id}/messages); every message carries `seq`, its commit-ordered position in the channel. Prints { data, hasMore, nextCursor }. Needs channel membership (else 403). Does NOT move your read marker: use `chat mark-read`. On a 403 'Not a member of this channel' it calls GET /chat/channels once and retries ONCE (a second refusal or any other 403 exits 1 as is)")
+    .option("--limit <n>", "messages per page, 1-100 (default 50)")
+    .option("--cursor <messageId>", "nextCursor from the previous page (a message UUID)")
+    .action(run(async (client, channelId, opts) => {
+    assertUuid(channelId, "channel id");
+    const limit = opts.limit !== undefined ? intFlag(opts.limit, "--limit", 1, 100) : undefined;
+    const cursor = opts.cursor !== undefined ? uuidOf(opts.cursor, "--cursor") : undefined;
+    // the live route answers { data: { data, hasMore, nextCursor } }: print() unwraps the outer envelope, leaving { data, hasMore, nextCursor }
+    return withChatMembership(client, () => client.get(`/api/v1/chat/channels/${encodeURIComponent(channelId)}/messages${buildQuery({ limit, cursor })}`));
+}));
+chat
+    .command("mark-read <channelId> <messageId>")
+    .description("Acknowledge the channel as read up to one message you were served (GET /chat/channels/{id}/messages?readUpTo=<messageId>&limit=1). The marker moves to that message's seq and only FORWARD: an older message, or one outside this channel, is a no-op (still exit 0: re-check `chat unread`); a malformed id is refused here; a 403 'Not a member of this channel' is retried ONCE after GET /chat/channels (a second refusal or any other 403 exits 1). Prints the channel's newest message, not a confirmation of the move")
+    .action(run(async (client, channelId, messageId) => {
+    assertUuid(channelId, "channel id");
+    const readUpTo = uuidOf(messageId, "message id");
+    return withChatMembership(client, () => client.get(`/api/v1/chat/channels/${encodeURIComponent(channelId)}/messages${buildQuery({ limit: 1, readUpTo })}`));
+}));
+// ---- notifications (read side; meta.latestByType, app 10-09) ----
+const notifications = program.command("notifications").description("Your in-app notifications");
+notifications
+    .command("list")
+    .description("List your notifications (GET /notifications). Prints { data, meta } whole: meta carries page, per_page, total, unreadCount, unreadByType { type: n } and latestByType { type: { latest, count } } (per type over the last 24 h: newest createdAt as an ISO string and the row count, read state ignored)")
+    .option("--page <n>", "page number (default 1)")
+    .option("--per-page <n>", "results per page, 1-200 (default 50)")
+    .action(run(async (client, opts) => {
+    const page = opts.page !== undefined ? intFlag(opts.page, "--page", 1, 1_000_000) : undefined;
+    const per_page = opts.perPage !== undefined ? intFlag(opts.perPage, "--per-page", 1, 200) : undefined;
+    // the live route answers { data: { data, meta } }: print() unwraps the outer envelope, leaving { data, meta }
+    return client.get(`/api/v1/notifications${buildQuery({ page, per_page })}`);
+}));
 // ---- raw escape hatch ----
 program
     .command("api <method> <path>")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "conduyt",
-  "version": "1.63.0",
+  "version": "1.65.0",
   "description": "Command-line interface for Conduyt CRM — manage contacts, deals, pipelines, and run insight queries from your terminal.",
   "type": "module",
   "main": "dist/index.js",