@floomhq/signaldash 0.40.0 → 0.41.0

package/README.md

@@ -120,7 +120,7 @@ setup installs both from the same pinned npm package
 the human chose to execute:
 
 ```bash
-npx -y @floomhq/signaldash@0.40.0 <invite-code>
+npx -y @floomhq/signaldash@0.41.0 <invite-code>
 ```
 
 Run that command in a terminal, not in an agent chat. Do not ask an agent to
@@ -218,6 +218,7 @@ timer, scheduler entry, Buffer item, or provider write.
 - `li_like_comment(post_id, parent_comment_id, comment_id, expected_watermark?)`
 - `li_delete_message(chat_id, message_id, confirm)`
 - `li_delete_comment(post_id, comment_id, confirm)`
+- `li_delete_post(post_id, expected_text_prefix, confirm)` (own post only, bound account only, capability `linkedin_post_delete`)
 - `li_draft_post(text, publish, scheduled_at?, content_pipeline_id?, content_pipeline_override?, mentions?, attachments?, first_comment?, confirm?, approval_hash?)`
 - `li_set_scheduled_post_first_comment(id, first_comment, confirm)`
 - `li_save_post_draft(text, mentions?, attachments?, first_comment?, source_key?, metadata?)`

package/bin/sd.mjs

@@ -864,12 +864,14 @@ const TOOLS = [
   {
     name: "li_send_invitation",
     path: "/li/send_invitation",
-    description: "Preview or send one exact LinkedIn invitation. First call without confirm, obtain approval, then repeat the exact provider_id and note with confirm:true.",
+    description: "Preview or send one exact LinkedIn invitation. First call without confirm, obtain approval, then repeat the exact provider_id, note, follow_up and note_mode with confirm:true. DEFAULT: a note is NOT put on the invitation (free accounts get notes refused); the invitation goes out bare and the note text is sent once as the first message after the person is proven to have accepted. Set note_mode \"inline\" only when the note must ride on the invitation itself. The preview shows the exact follow-up text; list or cancel pending follow-ups with sd_invitation_followups / sd_invitation_followup_cancel.",
     inputSchema: {
       type: "object",
       properties: {
         provider_id: { type: "string", minLength: 1, maxLength: 500 },
-        note: { type: "string", maxLength: 300 },
+        note: { type: "string", maxLength: 300, description: "With the default note_mode follow_up this text becomes the after-acceptance message; with note_mode inline it rides on the invitation." },
+        follow_up: { type: "string", minLength: 1, maxLength: 5000, description: "Exact message to send once after acceptance. Use instead of note (default mode), or alongside an inline note." },
+        note_mode: { type: "string", enum: ["follow_up", "inline"], default: "follow_up" },
         confirm: { type: "boolean", default: false },
       },
       required: ["provider_id"],
@@ -1859,6 +1861,21 @@ const TOOLS = [
       additionalProperties: false,
     },
   },
+  {
+    name: "li_delete_post",
+    path: "/li/delete_post",
+    description: "Delete ONE LinkedIn post authored by this authenticated account. Irreversible; disabled unless the operator enables the linkedin_post_delete capability. Acts only as the account bound to this SignalDash session. Requires the exact social_id from li_my_posts (urn:li:activity:<digits>), expected_text_prefix (the first 10-500 characters of the post text, exactly) and confirm:true. Before deleting, SignalDash reads the post with the same account and refuses unless the author is this sender (post_not_own), it is not a repost, and the text starts with expected_text_prefix (text_prefix_mismatch). Returns the post evidence and a post-delete readback; a replay of the same post is refused as duplicate_delete. Deletion is remediation, not rollback.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        post_id: { type: "string", pattern: "^urn:li:activity:[0-9]{1,30}$", maxLength: 60 },
+        expected_text_prefix: { type: "string", minLength: 10, maxLength: 500 },
+        confirm: { type: "boolean", const: true },
+      },
+      required: ["post_id", "expected_text_prefix", "confirm"],
+      additionalProperties: false,
+    },
+  },
   {
     name: "li_draft_post",
     path: "/li/create_post",
@@ -2325,6 +2342,48 @@ const TOOLS = [
       additionalProperties: false,
     },
   },
+  {
+    name: "sd_invitation_followups",
+    path: "/sd/invitation_followups",
+    description: "List this user's invitation follow-ups: exact messages that are sent once a LinkedIn invitation is proven accepted. States: pending (waiting for acceptance, or accepted and waiting for a send slot), sending, sent, cancelled, expired (not accepted within 30 days), needs_review (the thread moved, e.g. they wrote first, or the outcome is unknown; never retried automatically).",
+    inputSchema: {
+      type: "object",
+      properties: {
+        state: { type: "string", enum: ["pending", "sending", "sent", "cancelled", "expired", "needs_review"] },
+      },
+      additionalProperties: false,
+    },
+  },
+  {
+    name: "sd_invitation_followup_create",
+    path: "/sd/invitation_followup_create",
+    description: "Register an after-acceptance follow-up message for an invitation that was ALREADY sent. First call without confirm: SignalDash proves a pending sent invitation to this exact provider_id exists and shows the exact text. After the human approves, repeat the same provider_id, text and invitation_id with confirm:true.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        provider_id: { type: "string", minLength: 1, maxLength: 500 },
+        text: { type: "string", minLength: 1, maxLength: 5000 },
+        invitation_id: { type: "string", minLength: 1, maxLength: 500 },
+        confirm: { type: "boolean", default: false },
+      },
+      required: ["provider_id", "text"],
+      additionalProperties: false,
+    },
+  },
+  {
+    name: "sd_invitation_followup_cancel",
+    path: "/sd/invitation_followup_cancel",
+    description: "Cancel one exact invitation follow-up while it is still pending. Requires id and confirm:true. It cannot stop or unsend one already being sent or sent.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        id: { type: "string", format: "uuid" },
+        confirm: { type: "boolean", const: true },
+      },
+      required: ["id", "confirm"],
+      additionalProperties: false,
+    },
+  },
   {
     name: "sd_followup_create",
     path: "/sd/followup_create",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@floomhq/signaldash",
-  "version": "0.40.0",
+  "version": "0.41.0",
   "description": "Secure LinkedIn, WhatsApp, and email access for AI agents",
   "type": "module",
   "bin": {
@@ -19,7 +19,7 @@
   },
   "scripts": {
     "test": "node --test",
-    "check": "node --check bin/sd.mjs && node --check server/server.cjs && node --check server/outbound-text-policy.cjs && node --check server/intro-request-notifier.cjs && node --check server/content-pipeline.cjs && node --check server/x-signal-engine.cjs && node --check server/buffer-calendar.cjs && node --check server/composio-email.cjs && node --check server/attachments.cjs && node --check server/media-fetch.cjs && node --check server/write-control.cjs && node --check server/secretary-store.cjs && node --check server/secretary-collector.cjs && node --check server/secretary-latest.cjs && node --check server/secretary-approvals.cjs && node --check server/secretary-push.cjs && node --check server/secretary-rules.cjs && node --check server/secretary-shadow-gate.cjs && node --check server/secretary-vault-importer.cjs && node --check server/secretary-inspiration.cjs && node --check server/linkedin-archive-importer.cjs && node --check server/voice-profile.cjs && node --check server/campaign-store.cjs && node --check server/campaign-runner.cjs && node --check server/withdrawal-store.cjs && node --check server/post-scheduler.cjs && node --check server/draft-rewrite-worker.cjs && node --check server/message-scheduler.cjs && node --check server/wa-chat-index.cjs && node --check scripts/import-linkedin-archive.mjs && node --check scripts/import-secretary-vault-snapshot.mjs && node --check scripts/rebuild-secretary-actors.mjs && node --check scripts/extract-conversation-inspiration.mjs && node --check scripts/render-content-board.mjs && node --check scripts/collect-x-signals.mjs && node --check bin/signaldash.js && node --check lib/cli.js && node --check lib/config-file.js && node --check lib/mcp.js && node --check lib/rate-guard.js && node --check lib/secrets.js && node --check lib/unipile.js && node --check lib/x-signal-collector.cjs"
+    "check": "node --check bin/sd.mjs && node --check server/server.cjs && node --check server/outbound-text-policy.cjs && node --check server/intro-request-notifier.cjs && node --check server/content-pipeline.cjs && node --check server/x-signal-engine.cjs && node --check server/buffer-calendar.cjs && node --check server/composio-email.cjs && node --check server/attachments.cjs && node --check server/media-fetch.cjs && node --check server/write-control.cjs && node --check server/secretary-store.cjs && node --check server/secretary-collector.cjs && node --check server/secretary-latest.cjs && node --check server/secretary-approvals.cjs && node --check server/secretary-push.cjs && node --check server/secretary-rules.cjs && node --check server/secretary-shadow-gate.cjs && node --check server/secretary-vault-importer.cjs && node --check server/secretary-inspiration.cjs && node --check server/linkedin-archive-importer.cjs && node --check server/voice-profile.cjs && node --check server/campaign-store.cjs && node --check server/campaign-runner.cjs && node --check server/withdrawal-store.cjs && node --check server/post-scheduler.cjs && node --check server/draft-rewrite-worker.cjs && node --check server/message-scheduler.cjs && node --check server/invitation-followups.cjs && node --check server/wa-chat-index.cjs && node --check scripts/import-linkedin-archive.mjs && node --check scripts/import-secretary-vault-snapshot.mjs && node --check scripts/rebuild-secretary-actors.mjs && node --check scripts/extract-conversation-inspiration.mjs && node --check scripts/render-content-board.mjs && node --check scripts/collect-x-signals.mjs && node --check bin/signaldash.js && node --check lib/cli.js && node --check lib/config-file.js && node --check lib/mcp.js && node --check lib/rate-guard.js && node --check lib/secrets.js && node --check lib/unipile.js && node --check lib/x-signal-collector.cjs"
   },
   "keywords": [
     "mcp",

package/skills/signaldash/SKILL.md

@@ -417,7 +417,7 @@ Use the exact tool names and argument keys below. Limits are optional.
 | `li_mark_read` | `chat_id` required | Explicitly clear one LinkedIn chat's unread state. Reading never clears unread automatically. |
 | `li_start_chat` | `member_ids` required array of 1-10 exact `ACo`, `ACw`, or `AE` provider member IDs; `text` required exact first message; `confirm`, `approval_hash`, and `dry_run:true` apply only after preview | Start one direct or group chat. Preview first, show the complete member-ID set and exact text, then repeat that exact payload with the returned approval hash only after explicit approval. SignalDash resolves every member live, blocks protected or suppressed contacts, returns an existing exact member-set chat without sending, and charges one thread-message plus aggregate action for a new chat regardless of member count. `dry_run:true` proves the full path up to the provider write without consuming approval or budget. |
 | `li_send_message` | Manual path: `chat_id` and `text` required; `expected_watermark` optional exact 64-character watermark; `mark_read` optional boolean, default true. Secretary path: `secretary_receipt_id` alone. | Send one approved LinkedIn reply after an immediate read of that exact chat. A Secretary receipt derives the exact stored chat and text and refuses every caller-supplied override. |
-| `li_send_invitation` | `provider_id` required; `note` optional, max 300 exact characters; `confirm` optional, default false | First preview one exact target and note. The server verifies relationship, both invitation directions, and absence of an existing one-to-one chat. After exact approval, repeat the identical call with `confirm:true`; jitter completes before the final preflight and action reservation. |
+| `li_send_invitation` | `provider_id` required; `note` optional, max 300 exact characters; `follow_up` optional, max 5000; `note_mode` optional, `follow_up` (default) or `inline`; `confirm` optional, default false | First preview one exact target, note and follow-up. By default a note is NOT put on the invitation (free accounts get notes refused with provider_http_400/422): the invitation goes out bare and the note text becomes a pending invitation follow-up, sent once as the first message after the person is proven to have accepted. `note_mode:"inline"` keeps the note on the invitation. The server verifies relationship, both invitation directions, and absence of an existing one-to-one chat. After exact approval, repeat the identical call with `confirm:true`; jitter completes before the final preflight and action reservation. |
 | `li_invitations_received` | `limit` integer 1-100, default 50; `cursor` optional | List one bounded page of received invitations. This read authorizes only the exact returned invitation IDs for a later accept. |
 | `li_accept_invitation` | `invitation_id` required; `confirm:true` required | Accept one exact currently pending received invitation after a fresh `li_invitations_received` read and approval. |
 | `li_invitations_sent` | `limit` integer 1-100, default 50; `cursor` optional | List one bounded page of sent invitations. This read authorizes only the exact returned invitation IDs for a later withdrawal. |
@@ -478,6 +478,9 @@ Use the exact tool names and argument keys below. Limits are optional.
 | `sd_schedule_message` | `channel` required, `whatsapp` or `linkedin`; `chat_id` required, max 500; `text` required, max 5000; `scheduled_at` required offset-qualified ISO date-time from 60 seconds to 365 days ahead; `confirm:true` required | Schedule one exact message into one chat you have already read. Read that exact chat first, at `limit` 10 or more on LinkedIn: SignalDash records what the thread looked like and refuses at send time if the conversation moved. Text only; attachments are refused rather than dropped. One message at one time, never a sequence. |
 | `sd_scheduled_messages` | `state` optional, one of `scheduled`, `executing`, `sent`, `cancelled`, `failed`, `needs_review`; `channel` optional | List only this authenticated user's scheduled messages and their durable states. Returns every matching row, unpaginated, and always reports `needs_review_count` outside your filter. |
 | `sd_cancel_scheduled_message` | `id` required UUID; `confirm:true` required | Cancel one exact message while its state is still `scheduled`. It cannot stop one already being sent, and it cannot unsend one that has been sent. |
+| `sd_invitation_followups` | `state` optional: `pending`, `sending`, `sent`, `cancelled`, `expired`, `needs_review` | List invitation follow-ups and their durable states, with `needs_review_count`. Acceptance is proven hourly per pending row (invitation gone from a fully read sent list AND first-degree, or a chat exists); the send goes through the paced `li_send_message` write path once. If they already wrote, or the thread holds an outbound message, nothing is sent and the row becomes `needs_review`. Not accepted within 30 days: `expired`. |
+| `sd_invitation_followup_create` | `provider_id`, `text` required; `invitation_id` optional; `confirm` optional | Register a follow-up for an invitation that was already sent. Preview proves a pending sent invitation to this exact person; after approval repeat the identical call with `confirm:true`. One pending follow-up per person. |
+| `sd_invitation_followup_cancel` | `id` required UUID; `confirm:true` required | Cancel one exact follow-up while it is still `pending`. It cannot stop or unsend one being sent or sent. |
 | `sd_followup_create` | `channel`, exact `thread_id`, task `context`, and offset-qualified `due_at` required; optional completion condition, auto-close choice, recipient label, origin, source message, and baseline | Record one independent task inside a LinkedIn, WhatsApp, email, or Slack conversation. Multiple different tasks may remain active in the same thread. Monitoring only: this never sends. |
 | `sd_followups` | optional `status`, `channel`, and `overdue` filters | Reconcile and list task-level expectations. A reply either completes an explicitly auto-close task or moves it to `needs_review`; it never clears unrelated tasks in the same thread. |
 | `sd_followup_cancel` | `id` required UUID; `confirm:true` required | Cancel one exact active task without deleting communication history or sending anything. |