@m13v/s4l 1.7.1-rc.13 → 1.7.1-rc.14

package/mcp/dist/version.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.7.1-rc.13",
-  "installedAt": "2026-07-08T02:42:52.128Z"
+  "version": "1.7.1-rc.14",
+  "installedAt": "2026-07-08T02:57:56.346Z"
 }

package/mcp/manifest.json

@@ -2,7 +2,7 @@
   "dxt_version": "0.1",
   "name": "social-autoposter",
   "display_name": "S4L",
-  "version": "1.7.1-rc.13",
+  "version": "1.7.1-rc.14",
   "description": "Draft, review, approve, and autopilot X/Twitter posts.",
   "long_description": "## **⚠️ The disclaimer above is generic Claude boilerplate.** Anthropic shows the same warning on every plugin regardless of what it does; any plugin has the same level of access as any app you download from the internet.\n\nS4L is an open source product developed by Mediar.ai Incorporated, a VC-backed San Francisco-based startup.\n\nTo get started:\n\n1\\. Copy this prompt: **Set me up on S4L plugin end to end**\n\n2\\. Quit with CMD+Q, reopen Claude, paste into a new chat.\n\nWhat happens next:\n\n* About every 5 minutes S4L scans X for posts that match your topics and drafts replies in your voice.\n* Drafts show up as review cards, usually the first within a few minutes. Nothing is posted automatically; you approve each one.\n* Posting autopilot stays off until you explicitly turn it on.",
   "author": {

package/mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m13v/s4l-mcp",
-  "version": "1.7.1-rc.13",
+  "version": "1.7.1-rc.14",
   "private": true,
   "description": "Desktop MCP client for social-autoposter (X/Twitter rail): manual draft/review/approve loop, autopilot control, and stats. Thin wrapper over the existing pipeline scripts.",
   "license": "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m13v/s4l",
-  "version": "1.7.1-rc.13",
+  "version": "1.7.1-rc.14",
   "description": "Automated social posting pipeline for Reddit, X/Twitter, LinkedIn, and Moltbook. Install as a Claude Code agent skill.",
   "bin": {
     "social-autoposter": "bin/cli.js",

package/skill/dm-outreach-twitter.sh

@@ -146,6 +146,25 @@ For each DM row, BEFORE you compose or send, do this in order:
    - Navigate to https://x.com/THEIR_AUTHOR (strip any leading @).
    - Snapshot the page. Extract: display name, handle, bio text, follower count, pinned/top-of-feed recent tweet topic summary.
    - If the profile is suspended, protected, or empty, capture what you can and note "profile_limited" or "profile_inaccessible".
+   - MANDATORY BLOCK CHECK (do this on every profile visit, not just when a
+     send later fails): read the page text (snapshot or DOM query) and check
+     for the literal string "has blocked you" (case-insensitive). This is the
+     ONLY sufficient evidence for concluding we're blocked -- never infer it
+     from a missing Message button, a screenshot, or a send failure alone
+     (a missing Message button just as often means "DMs closed", which is
+     chat_disabled below, not a block).
+     If that exact text IS present:
+       a. Skip this DM: python3 $REPO_DIR/scripts/dm_conversation.py mark-skipped \\
+            --dm-id DM_ID --reason "blocked_by_user"
+       b. Hard-block the author so future items from them are never drafted
+          (shared universal blocklist, same mechanism engage-twitter uses):
+            python3 $REPO_DIR/scripts/reply_db.py blocklist add x THEIR_AUTHOR \\
+              --reason "X reported this author has blocked our account (dm-outreach-twitter, profile check)" \\
+              --classification blocked_by_author \\
+              --added-by block_probe
+       c. Move on to the next DM row; do not attempt to send.
+     If that text is NOT present, proceed normally -- do not skip or block
+     based on any other signal from this step.
 
 3. Persist the profile fields:
    \`\`\`bash

package/skill/engage-twitter.sh

@@ -356,6 +356,33 @@ MANDATORY reply flow for every item:
           a) Re-snapshot the page to refresh element state.
           b) Find the reply textbox: role="textbox" with name like "Post your reply"
              or "Post text". Click it.
+             If the textbox is NOT found, do NOT assume a technical glitch or
+             conclude "blocked" from a screenshot alone -- X removes the
+             composer but still renders the tweet normally when the author has
+             blocked us, so a missing textbox is genuinely ambiguous by itself.
+             Determine which deterministically:
+               i.   Click the article's reply icon (data-testid="reply" on the
+                    target article, NOT the submit button).
+               ii.  Wait ~2s, then read the page text (snapshot or DOM query).
+               iii. If the text contains "has blocked you" (case-insensitive):
+                    this is a confirmed, permanent block. Do NOT retry. Skip
+                    this reply: python3 $REPO_DIR/scripts/reply_db.py skipped ID "author_blocked_us"
+                    Then hard-block the author so future items from them are
+                    never drafted (same mechanism as the escape hatch above):
+                      python3 $REPO_DIR/scripts/reply_db.py blocklist add x HANDLE \\
+                        --reason "X reported this author has blocked our account (live reply attempt, engage-twitter)" \\
+                        --classification blocked_by_author \\
+                        --added-by block_probe \\
+                        --source-reply-id REPLY_ID
+                    Move on to the next assigned reply.
+               iv.  If that text is NOT present: this was a transient render
+                    miss, not a block. The click in (i) may have opened the
+                    composer -- re-snapshot; if the textbox is now present,
+                    continue with it below. If still absent, retry this whole
+                    step once more before treating it as a failed technical
+                    attempt.
+             NEVER conclude "blocked" from a screenshot alone -- only the
+             literal "has blocked you" text match above is sufficient evidence.
           c) Type YOUR_REPLY_TEXT (post-Step-3b short-link-wrapped form, post-Step-3a
              suffix) into that textbox. Do NOT auto-submit; we click the Reply
              button explicitly in step e.