@m13v/s4l 1.7.1-rc.5 → 1.7.1-rc.7

package/mcp/dist/onboarding.js

@@ -10,19 +10,11 @@ import { createRequire } from "node:module";
 import { repoDir, run } from "./repo.js";
 import { resolvePython } from "./runtime.js";
 const require = createRequire(import.meta.url);
-export const ONBOARDING_MILESTONES = [
-    "environment_checked",
-    "runtime_ready",
-    "x_connected",
-    "x_verified",
-    "profile_scanned",
-    "mode_chosen",
-    "project_ready",
-    "topics_seeded",
-    "tasks_scheduled",
-];
 const ledgerApi = require("../shared/onboarding-ledger.cjs");
 const doctorApi = require("../shared/doctor.cjs");
+// Re-export of the ONE runtime array (see the comment above the imports): this
+// is not a second list, just a typed alias for ledgerApi.MILESTONES.
+export const ONBOARDING_MILESTONES = ledgerApi.MILESTONES;
 export function onboardingSnapshot() {
     return ledgerApi.publicSnapshot();
 }

package/mcp/dist/version.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.7.1-rc.5",
-  "installedAt": "2026-07-07T21:16:12.514Z"
+  "version": "1.7.1-rc.7",
+  "installedAt": "2026-07-07T23:08:38.967Z"
 }

package/mcp/manifest.json

@@ -2,7 +2,7 @@
   "dxt_version": "0.1",
   "name": "social-autoposter",
   "display_name": "S4L",
-  "version": "1.7.1-rc.5",
+  "version": "1.7.1-rc.7",
   "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.5",
+  "version": "1.7.1-rc.7",
   "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/mcp/shared/onboarding-ledger.cjs

@@ -10,6 +10,7 @@ const MILESTONES = [
   "environment_checked",
   "runtime_ready",
   "x_connected",
+  "x_verified",
   "profile_scanned",
   "mode_chosen",
   "project_ready",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m13v/s4l",
-  "version": "1.7.1-rc.5",
+  "version": "1.7.1-rc.7",
   "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/reset-test-machine.sh

@@ -17,9 +17,12 @@
 #              disturbing the rest of the environment.
 #   --deep     FULL NUKE — the plugin reset above PLUS the shared layer it touches:
 #              per-agent Chrome profiles + cookies (reddit/linkedin/twitter), the
-#              browser-harness backend, and the packaged toolchain (uv binary, uv
-#              cache, Chromium ~1.7G). Other tools that rely on uv/Chromium
-#              re-provision afterward. Use to reproduce a true bare-metal box.
+#              browser-harness backend, the packaged toolchain (uv binary + uv
+#              data/cache, Chromium ~1.7G), the uv PATH shim in your shell rc, the
+#              real Google Chrome.app the provisioner installs, and Google's
+#              Keystone updater. Reproduces a genuinely bare-metal box (as if S4L
+#              had never run). Other tools that rely on uv/Chrome/Chromium
+#              re-provision afterward — intended for DEDICATED test machines.
 #
 # Usage:
 #   scripts/reset-test-machine.sh            # dry run: print what the plugin reset WOULD remove
@@ -205,6 +208,27 @@ echo "[1] MCP state dir (uv-owned python, venv, materialized repo, runtime.json,
 rm_path "$HOME_DIR/.social-autoposter-mcp" "state"
 echo
 
+# ---- 1a. compat symlink ~/social-autoposter -> materialized repo -----------
+# The .mcpb provisioner plants ~/social-autoposter as a symlink INTO the state
+# dir (so the pipeline's hardcoded $HOME/social-autoposter paths resolve). The
+# state-dir wipe in [1] leaves it DANGLING. Remove it — but ONLY when it is a
+# symlink resolving into .social-autoposter-mcp, so a developer's real clone (or
+# their own ~/social-autoposter symlink to a working tree) is never touched.
+echo "[1a] compat symlink ~/social-autoposter (plugin-planted)"
+SA_LINK="$HOME_DIR/social-autoposter"
+if [ -L "$SA_LINK" ]; then
+  SA_TARGET="$(readlink "$SA_LINK" 2>/dev/null || true)"
+  case "$SA_TARGET" in
+    *.social-autoposter-mcp/*|*.social-autoposter-mcp) rm_path "$SA_LINK" "compat-symlink" ;;
+    *) echo "  (leaving $SA_LINK -> $SA_TARGET — not a plugin-planted symlink)" ;;
+  esac
+elif [ -e "$SA_LINK" ]; then
+  echo "  (leaving $SA_LINK — a real directory/clone, not a plugin-planted symlink)"
+else
+  echo "  (no ~/social-autoposter symlink)"
+fi
+echo
+
 # ---- 1b. Claude Desktop .mcpb extension -----------------------------------
 # A .mcpb (Desktop) install scatters THREE artifacts under ~/Library/Application
 # Support/Claude/, NONE of which live in the state dir removed in [1]: the
@@ -532,6 +556,23 @@ if [ "$DEEP" -eq 1 ]; then
   rm_path "$HOME_DIR/.local/bin/uv"                "uv-bin"
   rm_path "$HOME_DIR/.local/bin/uvx"               "uvx-bin"
   rm_path "$HOME_DIR/.cache/uv"                    "uv-cache"
+  # uv's DATA dir (installed standalone Pythons + tool venvs) and its PATH shim
+  # survive the bin removal — a bare box has neither. The uv installer also
+  # appends `. "$HOME/.local/bin/env"` to the shell rc files; strip that exact
+  # line so no uv PATH shim lingers.
+  rm_path "$HOME_DIR/.local/share/uv"             "uv-data"
+  rm_path "$HOME_DIR/.local/bin/env"              "uv-env-script"
+  for rc in "$HOME_DIR/.zshrc" "$HOME_DIR/.zprofile" "$HOME_DIR/.profile" \
+            "$HOME_DIR/.bash_profile" "$HOME_DIR/.bashrc"; do
+    [ -f "$rc" ] || continue
+    if grep -q '\.local/bin/env' "$rc" 2>/dev/null; then
+      echo "  edit    strip uv env-shim line from $rc"
+      if [ "$DRY" -eq 0 ]; then
+        cp "$rc" "$rc.bak" 2>/dev/null || true
+        grep -v '\.local/bin/env' "$rc" > "$rc.tmp" 2>/dev/null && mv "$rc.tmp" "$rc"
+      fi
+    fi
+  done
   echo "  WARN    --deep removed uv + ms-playwright; other tools on this machine that rely on them will re-provision."
 else
   echo "  (left uv + ~/Library/Caches/ms-playwright + ~/.cache/uv in place)"
@@ -539,6 +580,47 @@ fi
 fi
 echo
 
+# ---- 6b. DEEP: packaged Google Chrome + its Keystone updater ----------------
+# The provisioner installs a REAL Google Chrome.app (runtime.ts Step 7) — the
+# browser the scanner drives over CDP — that NO other reset step removes, plus
+# installing it drops Google's Keystone auto-updater (LaunchAgents + support
+# dirs). A bare box had none of this. --deep removes all of it so the Chrome
+# install step is exercised fresh. NOTE: this touches the machine's Google Chrome
+# globally, not just S4L — hence --deep / test-box only.
+if [ "$PLUGIN_ONLY" -eq 1 ]; then
+  echo "[6b] packaged Google Chrome + Keystone updater — skipped (plugin reset; pass --deep to remove)"
+else
+  echo "[6b] packaged Google Chrome + Keystone updater — $([ "$DEEP" -eq 1 ] && echo ENABLED || echo 'skipped (pass --deep)')"
+  if [ "$DEEP" -eq 1 ]; then
+    # Stop Chrome + unload the Keystone/updater agents before deleting their plists.
+    if [ "$DRY" -eq 0 ]; then
+      pkill -f 'Google Chrome' 2>/dev/null || true
+      for lbl in com.google.keystone.agent com.google.keystone.xpcservice com.google.GoogleUpdater.wake; do
+        launchctl bootout "gui/$(id -u)/$lbl" 2>/dev/null || true
+      done
+    fi
+    rm_path "/Applications/Google Chrome.app"            "google-chrome"
+    rm_path "$HOME_DIR/Applications/Google Chrome.app"   "google-chrome-user"
+    for p in \
+      "$HOME_DIR/Library/Application Support/Google" \
+      "$HOME_DIR/Library/Google" \
+      "$HOME_DIR/Library/Caches/Google" \
+      "$HOME_DIR/Library/Caches/com.google.Chrome" \
+      "$HOME_DIR/Library/Caches/com.google.Keystone" \
+      "$HOME_DIR/Library/LaunchAgents/com.google.keystone.agent.plist" \
+      "$HOME_DIR/Library/LaunchAgents/com.google.keystone.xpcservice.plist" \
+      "$HOME_DIR/Library/LaunchAgents/com.google.GoogleUpdater.wake.plist" \
+      "$HOME_DIR/Library/LaunchAgents/com.google.GoogleUpdater.plist"; do
+      rm_path "$p" "google"
+    done
+    for f in "$HOME_DIR"/Library/Preferences/com.google.Chrome*.plist; do
+      [ -e "$f" ] && rm_path "$f" "google-pref"
+    done
+    echo "  WARN    --deep removed Google Chrome + Keystone updater machine-wide."
+  fi
+fi
+echo
+
 # ---- 7. settle & verify (defeat Claude auto-relaunch resurrection) ---------
 # Claude Desktop can RELAUNCH after step [0] — on auto-update (ShipIt), a macOS
 # re-open, or a login item — and a relaunched host re-materializes a skeleton