social-autoposter 1.6.61 → 1.6.63

package/bin/cli.js

@@ -705,6 +705,22 @@ function generatePlists() {
       stdoutLog: `${DEST}/skill/logs/launchd-self-update-stdout.log`,
       stderrLog: `${DEST}/skill/logs/launchd-self-update-stderr.log`,
     },
+    {
+      // On-screen overlay watcher supervisor. The overlay (harness status banner
+      // + interactive draft sidebar) only renders WHILE harness_overlay.py watch
+      // runs. The supervisor is idempotent (pgrep guard), so a 60s StartInterval
+      // is a no-op while the watcher is up and re-spawns it within a minute if it
+      // ever dies. RunAtLoad starts it right after install. This is what makes the
+      // overlay appear on headless / remote installs (Lane A); the MCP covers the
+      // pure-.mcpb lane by calling the same script on draft_cycle / autopilot.
+      file: 'com.m13v.social-overlay-watch.plist',
+      label: 'com.m13v.social-overlay-watch',
+      script: `${DEST}/skill/run-overlay-watch.sh`,
+      interval: 60,
+      runAtLoad: true,
+      stdoutLog: `${DEST}/skill/logs/launchd-overlay-watch-stdout.log`,
+      stderrLog: `${DEST}/skill/logs/launchd-overlay-watch-stderr.log`,
+    },
   ];
 
   const driver = scheduler.driverFor();

package/mcp/dist/index.js

@@ -222,6 +222,32 @@ function cycleProgressMessage(line) {
         return `Cycle stopped (${m[1]}).`;
     return null;
 }
+// Start the twitter-harness on-screen overlay watcher if it isn't already up.
+// The overlay (status banner + interactive draft sidebar) only renders WHILE
+// `harness_overlay.py watch` runs. The supervisor script is idempotent (pgrep
+// guard), so calling this on every draft_cycle / autopilot-enable / show-browser
+// is safe: it spawns at most one detached watcher and is a fast no-op otherwise.
+//
+// We thread SAPS_PYTHON (the owned uv runtime, so the watcher resolves a
+// playwright-capable interpreter on Lane B / .mcpb installs that have no system
+// python) and SAPS_LOG_DIR (the materialized repo's skill/logs, so the watcher
+// reads the SAME cycle logs this run writes to decide busy/idle). Fire-and-forget:
+// a failure here must never break the cycle it's decorating.
+async function ensureOverlayWatch() {
+    try {
+        await run("bash", ["skill/run-overlay-watch.sh"], {
+            timeoutMs: 20_000,
+            env: {
+                SAPS_PYTHON: resolvePython(),
+                SAPS_LOG_DIR: path.join(repoDir(), "skill", "logs"),
+                TWITTER_CDP_URL: process.env.TWITTER_CDP_URL || "http://127.0.0.1:9555",
+            },
+        });
+    }
+    catch {
+        /* best-effort: the overlay is a nicety, never a blocker */
+    }
+}
 async function produceDrafts(project, onProgress) {
     // Run the real pipeline in DRAFT_ONLY mode: scan -> score -> draft -> link-gen,
     // then STOP before posting. The script prints `DRAFT_ONLY_PLAN=<path>` and
@@ -240,6 +266,9 @@ async function produceDrafts(project, onProgress) {
     };
     if (project)
         env.SAPS_FORCE_PROJECT = project;
+    // Bring the on-screen overlay up alongside the live harness window so the user
+    // watching the scan/scrape sees status + queued drafts. Idempotent + detached.
+    await ensureOverlayWatch();
     let step = 0;
     let lastMsg = "";
     // ONE predictable, host-independent place to watch a draft_cycle run, so any
@@ -427,6 +456,30 @@ server.registerPrompt("getting-started", {
         },
     ],
 }));
+// Instruction (NOT a script) the agent follows to research the product website
+// after the profile scan. The agent uses ITS OWN browser/fetch tools — the MCP
+// ships no scraper. The goal is to fill the PRODUCT half of the config (what it
+// does, how it's different, who it's for, the CTA link, claims to avoid) from the
+// site itself, written in the user's voice captured by the profile scan.
+const WEBSITE_RESEARCH_INSTRUCTIONS = "PRODUCT RESEARCH (do this before saving the product fields):\n" +
+    "1. Ask the user for the URL of the product/website they want to market on X.\n" +
+    "2. Visit it with your OWN browser/fetch tools (no scraper is provided) and read " +
+    "AT LEAST 5 pages if the site has them — follow the internal nav/footer links. " +
+    "Prioritize: homepage, pricing, features/product, about, docs or changelog or blog, " +
+    "FAQ, customers/testimonials/case-studies. Read as many as you can find (5+ is the " +
+    "floor, not the cap) to learn the product deeply.\n" +
+    "3. From what you actually read, extract the PRODUCT fields: `description` (what it " +
+    "does, concretely), `differentiator` (how it's genuinely different from alternatives), " +
+    "`icp` (who it's for — cross-check against who the user engages with on X), " +
+    "`get_started_link` (the primary signup/CTA URL), and `content_guardrails` (claims, " +
+    "competitors, or wording the site avoids — never overclaim beyond the site).\n" +
+    "4. WRITE these fields in the USER'S voice from the profile scan (their phrasing, " +
+    "register, vibe) while keeping every product CLAIM factual to the site. Don't invent " +
+    "features, metrics, or guarantees the site doesn't state.\n" +
+    "5. Show the user your draft of the product fields for confirmation, then call setup " +
+    "with name + the product fields (plus the voice/search_topics from the profile scan) " +
+    "to save. If the site is thin or unreachable, tell the user and ask them to fill the " +
+    "gaps rather than guessing.";
 // ---- setup: per-project config (the "brain": project, website, voice) -----
 // Run this FIRST. The action tools refuse until at least one project is ready.
 // You can set up MULTIPLE products and fill each project's fields INCREMENTALLY
@@ -437,9 +490,11 @@ tool("setup", {
     title: "Set up a project",
     description: "Run this FIRST, before any drafting or autopilot. Two jobs:\n" +
         "1) Configure a project this install posts for: its website, what it does (description), who " +
-        "to target (icp), and brand voice. Set up MULTIPLE products (call once per product, identified " +
-        "by name); fill a project's fields INCREMENTALLY across several calls — pass whatever you have, " +
-        "it merges and tells you what's still missing.\n" +
+        "to target (icp), and brand voice. To fill the PRODUCT fields, get the product URL and visit " +
+        "it with your own browser/fetch tools — read 5+ pages (home, pricing, features, about, docs/" +
+        "blog, FAQ) to learn it deeply, rather than guessing from the name. Set up MULTIPLE products " +
+        "(call once per product, identified by name); fill a project's fields INCREMENTALLY across " +
+        "several calls — pass whatever you have, it merges and tells you what's still missing.\n" +
         "2) Connect X/Twitter (action:'connect_x'): the autoposter posts through its OWN managed Chrome, " +
         "which needs your logged-in x.com session. This imports x.com/twitter.com cookies from your " +
         "everyday browser (Chrome/Arc/Brave/Edge, auto-detected) into that browser — nothing else is " +
@@ -591,12 +646,17 @@ tool("setup", {
             posts: scan.posts,
             comments: scan.comments,
             grounding_instructions: scan.grounding_instructions,
-            next_step: "Read the bio, posts, and comments as GROUND TRUTH. Following grounding_instructions, " +
-                "extract: (1) their profession/identity, (2) their voice & vibe (tone, phrasing, casing, " +
-                "tics), (3) 2-4 verbatim golden-rule example replies, (4) a phrase bank + things they " +
-                "avoid, (5) their icp, (6) recurring themes -> search_topics. Show the user your read " +
-                "('here's the voice/topics I picked up, sound like you?'), then call setup with the " +
-                "confirmed name/voice/icp/differentiator/search_topics/content_guardrails to save.",
+            website_research_instructions: WEBSITE_RESEARCH_INSTRUCTIONS,
+            next_step: "TWO steps, in order. FIRST (voice, from this scan): read the bio, posts, and comments " +
+                "as GROUND TRUTH and, per grounding_instructions, extract their profession/identity, " +
+                "voice & vibe (tone, phrasing, casing, tics), 2-4 verbatim golden-rule example replies, " +
+                "a phrase bank + things they avoid, their icp, and recurring themes -> search_topics. " +
+                "SECOND (product, from their website): then follow website_research_instructions — ask " +
+                "the user for the product URL and read 5+ of its pages to fill description, " +
+                "differentiator, icp, get_started_link, and content_guardrails, written in the voice you " +
+                "just captured. Show the user your combined read ('here's the voice/topics from your " +
+                "profile and what I learned from your site — accurate?'), then call setup with the " +
+                "confirmed fields to save.",
         });
     }
     // Status / discovery mode: no project name supplied, or explicitly asked.
@@ -940,6 +1000,9 @@ tool("autopilot", {
         });
     }
     if (action === "enable") {
+        // Bring up the on-screen overlay watcher so background autopilot cycles
+        // still paint the harness status/sidebar. Idempotent + detached.
+        await ensureOverlayWatch();
         // 1) Cycle plist. Write one pointing at the self-update guard ONLY if no
         //    plist exists yet; never overwrite a hand-tuned/dev plist.
         const createdCycle = ensurePlist(TWITTER_AUTOPILOT_PLIST, plistXml({
@@ -1449,6 +1512,10 @@ tool("show_browser_to_user", {
         }
         return jsonContent({ ok: true, brought_to_front: true, port: res.port });
     }
+    // If the user is about to watch the live browser, make sure the on-screen
+    // overlay watcher is up too so the harness window carries status + drafts.
+    if (action === "start")
+        await ensureOverlayWatch();
     const ensured = await screencast.ensure(typeof args?.port === "number" ? args.port : undefined);
     if (!ensured.ok) {
         const message = ensured.error === "no_browser"

package/mcp/dist/version.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.6.60",
-  "installedAt": "2026-06-05T02:22:33.297Z"
+  "version": "1.6.63",
+  "installedAt": "2026-06-05T03:14:19.604Z"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "social-autoposter",
-  "version": "1.6.61",
+  "version": "1.6.63",
   "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/watchdog_hung_runs.py

@@ -30,7 +30,15 @@ PER_SCRIPT_CAP_SEC = {
     # 2026-04-27: extend 120 min cap to remaining stats / audit / link-edit jobs.
     # 45 min was killing audit-twitter mid-run and starving link-edit-* of time
     # to actually post replies + verify SEO deploys.
-    ("stats.sh", "twitter"): 120 * 60,
+    # 2026-06-04: raised 120 -> 180 min. stats_twitter's total fxtwitter
+    # working set (posts + thread_top_replies + twitter replies + parent
+    # threads, ~1600-1900 polls @ ~1 req/s) crept past 7200s (~7400-7500s)
+    # as the post corpus grew, so every 6h run was SIGKILLed at the cap
+    # before stamping the final lanes -> the unstamped tail stayed stale ->
+    # the next run re-polled the same backlog and died again (death spiral).
+    # The job completes cleanly in <2.1h when not killed; 180 min gives
+    # durable headroom and the cron fires every 6h so there is no overlap.
+    ("stats.sh", "twitter"): 180 * 60,
     ("stats.sh", "linkedin"): 120 * 60,
     ("stats.sh", "moltbook"): 120 * 60,
     ("audit.sh", None): 120 * 60,

package/skill/run-overlay-watch.sh

@@ -0,0 +1,79 @@
+#!/bin/bash
+# Idempotent supervisor for the twitter-harness on-screen overlay watcher.
+#
+# WHAT: keeps exactly ONE `harness_overlay.py watch` process alive. That watcher
+# injects the status overlay + interactive draft sidebar into the twitter-harness
+# Chrome window so a human watching the harness sees what the pipeline is doing
+# and can preview queued drafts.
+#
+# WHY a supervisor: the overlay only renders WHILE the watch process runs. It was
+# previously a manual, local-only process, so it never appeared on headless /
+# remote installs. This script makes it self-starting from BOTH install lanes:
+#   - Lane A (npm/cli): launchd job `com.m13v.social-overlay-watch` (StartInterval
+#     60 + RunAtLoad) re-invokes this script every minute; the pgrep guard makes
+#     re-invocation a no-op while the watcher is already up.
+#   - Lane B (.mcpb / pure MCP): the MCP calls this script on draft_cycle /
+#     autopilot-enable / show_browser_to_user, threading SAPS_PYTHON + SAPS_LOG_DIR.
+#
+# IDEMPOTENT: safe to call on a 60s timer. If a watcher is already running it
+# exits 0 immediately. Otherwise it spawns one detached (nohup, own session) and
+# returns; the spawned watcher then runs until the machine/MCP tears it down.
+#
+# This script is intentionally NOT locked: the overlay UX is expected to evolve.
+
+set -u
+
+# --- resolve the repo this script lives in (works from launchd + MCP cwd) -----
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+REPO_DIR="$(cd "${SCRIPT_DIR}/.." && pwd)"
+OVERLAY_PY="${REPO_DIR}/scripts/harness_overlay.py"
+
+if [ ! -f "${OVERLAY_PY}" ]; then
+  echo "[overlay-watch] harness_overlay.py not found at ${OVERLAY_PY}; nothing to do" >&2
+  exit 0
+fi
+
+# --- idempotency guard: at most one watcher, ever ----------------------------
+# Match the full `harness_overlay.py watch` invocation (NOT a bare `grep -r`, so
+# this never trips the BSD-grep-on-FIFO hang noted in the repo CLAUDE.md).
+if pgrep -f "harness_overlay.py watch" >/dev/null 2>&1; then
+  exit 0
+fi
+
+# --- resolve a python interpreter --------------------------------------------
+# harness_overlay.py self-heals to a playwright-capable interpreter on its own
+# (see _ensure_playwright_interpreter), so any python3 that exists is fine to
+# launch with. Prefer the MCP-threaded SAPS_PYTHON (owned uv runtime), then the
+# usual suspects.
+PYBIN=""
+for _cand in \
+  "${SAPS_PYTHON:-}" \
+  "/opt/homebrew/bin/python3.11" \
+  "/usr/bin/python3" \
+  "/opt/homebrew/bin/python3"
+do
+  if [ -n "${_cand}" ] && [ -x "${_cand}" ]; then PYBIN="${_cand}"; break; fi
+done
+if [ -z "${PYBIN}" ]; then
+  PYBIN="$(command -v python3 2>/dev/null || true)"
+fi
+if [ -z "${PYBIN}" ]; then
+  echo "[overlay-watch] no python3 found; cannot start overlay watcher" >&2
+  exit 0
+fi
+
+# --- env the watcher needs ---------------------------------------------------
+# SAPS_LOG_DIR: where harness_overlay.py reads cycle logs to decide busy/idle.
+# Default to this repo's skill/logs (MCP overrides it to the materialized repo).
+export SAPS_LOG_DIR="${SAPS_LOG_DIR:-${REPO_DIR}/skill/logs}"
+# CDP target for the twitter harness Chrome (honor BYO-Chrome installs).
+export TWITTER_CDP_URL="${TWITTER_CDP_URL:-http://127.0.0.1:9555}"
+mkdir -p "${SAPS_LOG_DIR}" 2>/dev/null || true
+WATCH_LOG="${SAPS_LOG_DIR}/overlay-watch.log"
+
+# --- spawn detached ----------------------------------------------------------
+cd "${REPO_DIR}" || exit 0
+echo "[overlay-watch] $(date '+%Y-%m-%d %H:%M:%S') starting watcher py=${PYBIN} cdp=${TWITTER_CDP_URL} log=${SAPS_LOG_DIR}" >>"${WATCH_LOG}" 2>&1
+nohup "${PYBIN}" "${OVERLAY_PY}" watch >>"${WATCH_LOG}" 2>&1 &
+disown 2>/dev/null || true
+exit 0