@m13v/s4l 1.7.10-rc.2 → 1.7.10-rc.4

package/mcp/dist/version.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.7.10-rc.2",
-  "installedAt": "2026-08-12T17:53:56.745Z"
+  "version": "1.7.10-rc.4",
+  "installedAt": "2026-08-12T18:35:58.320Z"
 }

package/mcp/manifest.json

@@ -2,7 +2,7 @@
   "dxt_version": "0.1",
   "name": "social-autoposter",
   "display_name": "S4L",
-  "version": "1.7.10-rc.2",
+  "version": "1.7.10-rc.4",
   "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": {
@@ -19,8 +19,10 @@
     "type": "node",
     "entry_point": "dist/index.js",
     "mcp_config": {
-      "command": "${__dirname}/launch.js",
-      "args": [],
+      "command": "${__dirname}/vendor/node-darwin-arm64/bin/node",
+      "args": [
+        "${__dirname}/dist/index.js"
+      ],
       "env": {
         "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
       }

package/mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m13v/s4l-mcp",
-  "version": "1.7.10-rc.2",
+  "version": "1.7.10-rc.4",
   "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.10-rc.2",
+  "version": "1.7.10-rc.4",
   "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/scripts/release-mcpb.sh

@@ -387,7 +387,9 @@ console.log('  manifest tools ('+tools.length+'): '+tools.map(t=>t.name).join(',
 # points at this vendored binary's absolute path, so every session type — main
 # chat, agent-mode, any future session type — spawns the SAME real binary.
 # Both macOS arches since 1.7.9: arm64 (every deployed box) AND x64 (Intel Macs
-# still on Tahoe). mcp/launch.js picks the arch-matched binary at spawn time.
+# still on Tahoe). Since the 2026-08-12 launch.js removal the manifest points
+# straight at the arm64 binary, so x64 rides along in the bundle but is NOT
+# spawnable via the manifest (no deployed Intel boxes today).
 NODE_RUNTIME_VERSION="v24.18.0"
 NODE_RUNTIME_PLATFORMS="darwin-arm64 darwin-x64"
 NODE_CACHE_DIR="$REPO_ROOT/.cache/node-runtime"
@@ -491,7 +493,7 @@ for sub in mcp/dist/version.json mcp/package.json; do
   echo "  pipeline.tgz $sub: $SUBV ok"
 done
 
-REQUIRED_FILES="dist/index.js dist/runtime.js manifest.json launch.js"
+REQUIRED_FILES="dist/index.js dist/runtime.js manifest.json"
 for p in $NODE_RUNTIME_PLATFORMS; do
   REQUIRED_FILES="$REQUIRED_FILES vendor/node-$p/bin/node"
 done
@@ -501,25 +503,26 @@ for f in $REQUIRED_FILES; do
   n=$(printf '%s\n' "$LISTING" | grep -c "[0-9:]   $f\$" || true)
   [[ "$n" -ge 1 ]] || die "bundle missing $f"
 done
-echo "  runtime + server + manifest + launcher + vendored node (both arches): ok"
+echo "  runtime + server + manifest + vendored node (both arches): ok"
 
 # The compat gate inside Claude Desktop only recognizes a node-type extension
 # when mcp_config.command is the bare string "node" or a path ending in .js
 # (its fo() command-recognizer). Pointing at the vendored node BINARY shipped
 # "this extension is incompatible" to every Mac without a system Node.js
-# (first hit: new-user install, 2026-08-10). Guard the manifest shape so a
-# future edit cannot silently regress it.
+# (first hit: new-user install, 2026-08-10). The launch.js shim that satisfied
+# the gate was itself broken by Desktop 1.28929.0 (stdio-inherit re-exec lost
+# the MCP transport), so per user decision 2026-08-12 the binary-path command
+# is shipped again and this check is a WARNING, not a blocker.
 MANIFEST_CMD=$(unzip -p "$BUNDLE" manifest.json 2>/dev/null | node -p "JSON.parse(require('fs').readFileSync(0,'utf8')).server.mcp_config.command" 2>/dev/null || echo "?")
 case "$MANIFEST_CMD" in
   node|node.exe|*.js) echo "  manifest command Desktop-recognizable ($MANIFEST_CMD): ok" ;;
-  *) die "manifest mcp_config.command '$MANIFEST_CMD' is not recognizable by Claude Desktop's node compat gate (must be 'node' or end in .js); Macs without system Node.js will see 'incompatible' at install" ;;
+  *) echo "  WARNING: manifest mcp_config.command '$MANIFEST_CMD' is not recognizable by Claude Desktop's node compat gate (must be 'node' or end in .js); Macs without system Node.js may see 'incompatible' at install" >&2 ;;
 esac
 
-# The vendored binaries and the launcher must survive the zip round-trip with
+# The vendored binaries must survive the zip round-trip with
 # their executable bits intact (extract to a temp dir and run --version where
 # the host arch allows; a permissions regression here would silently produce a
-# Node that Desktop can spawn but that refuses to execute, or a launch.js that
-# agent-mode cannot exec).
+# Node that Desktop can spawn but that refuses to execute).
 VENDOR_CHECK_DIR="$(mktemp -d)"
 for p in $NODE_RUNTIME_PLATFORMS; do
   unzip -q -o "$BUNDLE" "vendor/node-$p/bin/node" -d "$VENDOR_CHECK_DIR"
@@ -533,13 +536,7 @@ for p in $NODE_RUNTIME_PLATFORMS; do
     echo "  vendored node ($p) survives bundle round-trip with exec bit intact; --version run skipped (host $HOST_OS-$HOST_ARCH cannot exec $p)"
   fi
 done
-unzip -q -o "$BUNDLE" "launch.js" -d "$VENDOR_CHECK_DIR"
-LAUNCH_CHECK="$VENDOR_CHECK_DIR/launch.js"
-[[ -x "$LAUNCH_CHECK" ]] || die "launch.js in bundle lost its executable bit (agent-mode literal spawn would fail)"
-head -c 9 "$LAUNCH_CHECK" | grep -q '^#!/bin/sh' || die "launch.js in bundle is missing its #!/bin/sh shebang"
-node --check "$LAUNCH_CHECK" || die "launch.js in bundle is not valid JavaScript (Desktop built-in-node spawn would fail)"
 rm -rf "$VENDOR_CHECK_DIR"
-echo "  launch.js: exec bit + shebang + JS syntax ok"
 
 if [[ "$DO_RELEASE" == "0" ]]; then
   say "Done (--no-release). Bundle ready at: $BUNDLE"