social-autoposter 1.6.28 → 1.6.30

package/bin/cli.js

@@ -549,23 +549,28 @@ function installBrowserHarness() {
       spawnSync(harnessBin, ['--reload'], { stdio: 'inherit' });
     }
 
-    // Contract check: server.py invokes `browser-harness -c <script>`. If an
-    // offline/rate-limited fetch left a stale checkout that predates the `-c`
-    // interface, the CLI still "installs" fine but every bh_run returns the
-    // usage banner and CDP looks "not connected". Verify the installed binary
-    // actually speaks `-c` (its no-arg usage string mentions it) and fail
-    // LOUDLY here instead of shipping a silently-broken twitter-harness.
+    // Contract check: server.py pipes the script to browser-harness via stdin.
+    // Upstream supports two banner shapes — older builds advertise `-c <script>`
+    // and newer builds advertise the `<<'PY' ... PY` heredoc form. Either is
+    // fine for our use case (we pass the script via stdin, which both accept).
+    // Fail loudly if the installed binary advertises NEITHER, which usually
+    // means an offline/partial clone left a broken CLI that will silently make
+    // every bh_run look like "CDP not connected".
     if (fs.existsSync(harnessBin)) {
       const probe = spawnSync(harnessBin, [], { stdio: 'pipe', encoding: 'utf8', timeout: 15000 });
       const usage = `${probe.stdout || ''}${probe.stderr || ''}`;
-      if (!/\b-c\b/.test(usage)) {
-        console.error('    ERROR: installed browser-harness CLI does not accept `-c` (stale clone).');
-        console.error('    The twitter-harness MCP will return a usage banner / "CDP not connected".');
+      const supportsDashC = /\b-c\b/.test(usage);
+      const supportsStdin = /<<'PY'|<<"PY"|<<PY\b/.test(usage);
+      if (!supportsDashC && !supportsStdin) {
+        console.error('    ERROR: installed browser-harness CLI advertises neither `-c` nor a stdin heredoc.');
+        console.error('    This usually means a partial/corrupted install. The twitter-harness MCP will');
+        console.error('    return a usage banner / "CDP not connected" on every call.');
         console.error(`    Fix: rm -rf ${harnessDir} && re-run \`social-autoposter init\` while online,`);
         console.error('    or manually: git clone https://github.com/browser-use/browser-harness ' + harnessDir +
           ' && ' + uvBin + ' tool install --force -e ' + harnessDir);
       } else {
-        console.log('    browser-harness CLI verified (accepts -c).');
+        const shape = supportsStdin ? 'stdin heredoc' : '-c flag';
+        console.log(`    browser-harness CLI verified (${shape}).`);
       }
     }
   }

package/mcp/package.json

@@ -8,18 +8,23 @@
     "social-autoposter-mcp": "dist/index.js"
   },
   "scripts": {
-    "build": "tsc",
+    "build": "vite build && tsc",
+    "build:panel": "vite build",
+    "build:server": "tsc",
     "start": "node dist/index.js",
     "dev": "tsc --watch",
     "install-clients": "node install.mjs",
     "uninstall-clients": "node install.mjs --uninstall"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.12.0",
+    "@modelcontextprotocol/ext-apps": "^1.7.3",
+    "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^3.23.8"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
-    "typescript": "^5.5.0"
+    "typescript": "^5.5.0",
+    "vite": "^6.0.0",
+    "vite-plugin-singlefile": "^2.0.0"
   }
 }

package/mcp-servers/browser-harness/server.py

@@ -407,9 +407,14 @@ def _run_harness(script: str, timeout: int = EXEC_TIMEOUT_SEC) -> dict:
     # Make sure ~/.local/bin is on PATH (uv tools live there).
     env["PATH"] = f"{Path.home()}/.local/bin:" + env.get("PATH", "")
 
+    # Upstream browser-harness dropped the `-c <script>` flag and now reads the
+    # script from stdin only (heredoc style). Pass via stdin so we work against
+    # current upstream; the old `-c` form returns the usage banner and exits 1,
+    # which used to surface as "CDP not connected" on every fresh install.
     try:
         proc = subprocess.run(
-            [BROWSER_HARNESS_BIN, "-c", script],
+            [BROWSER_HARNESS_BIN],
+            input=script,
             env=env,
             capture_output=True,
             text=True,
@@ -677,12 +682,20 @@ def bh_screenshot(quality: int = 50) -> str:
 
     Returns JSON with the file path and basic page info. Use bh_run for any
     workflow that needs to keep state across multiple steps.
+
+    The `quality` parameter is accepted for back-compat but is ignored — the
+    current upstream `capture_screenshot()` signature is (path, full, max_dim)
+    and does not expose a JPEG-quality knob. Older callers (and the MCP tool
+    schema) still pass it; we just don't forward it.
     """
+    # Avoid the unused-variable lint and keep `quality` part of the MCP
+    # contract: a sanity-cap so a bad caller can't pass arbitrary types.
+    _ = int(quality)
     script = (
         "import json, time, os\n"
         "ensure_real_tab()\n"
         "info = page_info()\n"
-        f"path = capture_screenshot(quality={int(quality)})\n"
+        "path = capture_screenshot()\n"
         "print(json.dumps({\"screenshot\": str(path), \"page\": info}))\n"
     )
     result = _run_harness(script)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "social-autoposter",
-  "version": "1.6.28",
+  "version": "1.6.30",
   "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/backfill_twitter_attempts_topic.py

@@ -4,7 +4,12 @@
 Periodic UPDATE that fills `twitter_search_attempts.search_topic` from the
 adjacent `twitter_candidates` rows once a scoring cycle finishes writing them.
 
-Why this lives outside the cycle: `score_twitter_candidates.py` and the parent
+HTTP-only (no DATABASE_URL): the two backfill passes run server-side behind
+`POST /api/v1/twitter-search-attempts/backfill-topic`. This script is now a
+thin trigger that POSTs the window and prints the rows-updated counts. The
+published package carries no direct-DB dependency.
+
+Why this backfill exists at all: `score_twitter_candidates.py` and the parent
 `skill/run-twitter-cycle.sh` are both `chflags uchg` locked, and the canonical
 SCAN_SCHEMA in the shell does not yet carry `search_topic` on each entry of
 `queries_used` (so `log_twitter_search_attempts.py` cannot stamp it at INSERT
@@ -12,7 +17,7 @@ time). Until those locked files are extended, we backfill from the candidate
 side, which DOES know the topic (set by `pick_search_topic.py` -> stamped onto
 twitter_candidates.search_topic + search_attempt_id).
 
-Two passes, both safe to rerun:
+The endpoint runs two passes, both safe to rerun:
 
   A) Direct join via search_attempt_id (covers non-dud attempts that produced
      at least one candidate).
@@ -21,9 +26,8 @@ Two passes, both safe to rerun:
      in the same cycle DID return candidates and therefore know the topic.
      Skips ambiguous batches (more than one distinct topic) to avoid noise.
 
-Fully-dud cycles (every query for a project in the batch was a dud) stay NULL
-until the locked shell is extended; those are rare and surface in the
-dashboard as a single "(no topic)" bucket per project.
+Fully-dud cycles stay NULL until the locked shell is extended; rare, and they
+surface in the dashboard as a single "(no topic)" bucket per project.
 
 Run from cron (launchd `com.m13v.social-twitter-attempt-topic-backfill`,
 every 5 min) or directly:
@@ -38,79 +42,38 @@ import sys
 import time
 
 sys.path.insert(0, os.path.dirname(os.path.abspath(__file__)))
-import db  # noqa: E402
+from http_api import api_post, load_env  # noqa: E402
 
 
 def main():
     p = argparse.ArgumentParser()
     p.add_argument("--days", type=int, default=7,
                    help="Only backfill rows where ran_at >= NOW() - INTERVAL "
-                        "'N days' (default 7). Cron path uses 7; ad-hoc "
+                        "'N days' (default 7). Cron path uses 14; ad-hoc "
                         "operators can widen.")
     p.add_argument("--all", action="store_true",
                    help="Backfill the entire table; ignores --days.")
     args = p.parse_args()
 
-    conn = db.get_conn()
-    where_recent = (
-        ""
-        if args.all
-        else f"AND a.ran_at >= NOW() - INTERVAL '{int(args.days)} days'"
-    )
-
+    load_env()
     t0 = time.time()
 
-    # Pass A: candidate-join. Covers any attempt that produced >=1 scored tweet.
-    cur = conn.execute(f"""
-      UPDATE twitter_search_attempts a
-         SET search_topic = sub.topic
-        FROM (
-          SELECT search_attempt_id, MIN(search_topic) AS topic
-            FROM twitter_candidates
-           WHERE search_attempt_id IS NOT NULL
-             AND search_topic IS NOT NULL
-             AND search_topic <> ''
-           GROUP BY search_attempt_id
-        ) sub
-       WHERE a.id = sub.search_attempt_id
-         AND a.search_topic IS NULL
-         {where_recent}
-    """)
-    a_rows = cur.rowcount
-    conn.commit()
-
-    # Pass B: batch-fanout. Covers dud attempts whose sibling non-dud attempts
-    # agree on a single topic. Ambiguous batches stay NULL.
-    cur = conn.execute(f"""
-      UPDATE twitter_search_attempts a
-         SET search_topic = sub.topic
-        FROM (
-          SELECT batch_id, project_name,
-                 MIN(search_topic) AS topic,
-                 COUNT(DISTINCT search_topic) AS topic_n
-            FROM twitter_search_attempts
-           WHERE batch_id IS NOT NULL
-             AND project_name IS NOT NULL
-             AND search_topic IS NOT NULL
-           GROUP BY batch_id, project_name
-        ) sub
-       WHERE a.batch_id = sub.batch_id
-         AND a.project_name = sub.project_name
-         AND a.search_topic IS NULL
-         AND sub.topic_n = 1
-         {where_recent}
-    """)
-    b_rows = cur.rowcount
-    conn.commit()
+    resp = api_post(
+        "/api/v1/twitter-search-attempts/backfill-topic",
+        {"days": int(args.days), "all": bool(args.all)},
+    )
+    data = resp.get("data") or {}
+    a_rows = data.get("pass_a", 0)
+    b_rows = data.get("pass_b", 0)
+    window = data.get("window", "all" if args.all else f"{args.days}d")
 
     elapsed = time.time() - t0
     print(
         f"backfill_twitter_attempts_topic: "
-        f"pass_a={a_rows} pass_b={b_rows} window={'all' if args.all else f'{args.days}d'} "
+        f"pass_a={a_rows} pass_b={b_rows} window={window} "
         f"elapsed={elapsed:.2f}s",
         file=sys.stderr,
     )
-    conn.close()
     return 0
 
 

package/skill/lib/twitter-backend.sh

@@ -254,38 +254,14 @@ _sa_resolve_uv() {
     return 1
 }
 ensure_harness_c_support() {
-    # Run once per process even if several libs source this file.
-    [ -n "${_SA_HARNESS_C_CHECKED:-}" ] && return 0
-    export _SA_HARNESS_C_CHECKED=1
-
-    local src="$HOME/Developer/browser-harness"
-    local run_py="$src/src/browser_harness/run.py"
-    local bh="$HOME/.local/bin/browser-harness"
-
-    # Static capability probe — no daemon/Chrome needed. The CLI is an editable
-    # (`uv tool install -e`) install of $src, so its run.py is the source of
-    # truth for whether `-c` is recognized.
-    if [ -f "$run_py" ] && grep -q '"-c"' "$run_py"; then
-        return 0
-    fi
-
-    _sa_harness_log "[harness] browser-harness checkout missing/stale (no -c support) -> self-healing via git + uv..."
-    if [ -d "$src/.git" ]; then
-        git -C "$src" fetch --depth 1 origin HEAD >/dev/null 2>&1 \
-            && git -C "$src" reset --hard FETCH_HEAD >/dev/null 2>&1
-    fi
-    local uv; uv="$(_sa_resolve_uv || true)"
-    if [ -n "$uv" ] && [ -d "$src" ]; then
-        "$uv" tool install --force -e "$src" >/dev/null 2>&1 || true
-    fi
-    [ -x "$bh" ] && "$bh" --reload >/dev/null 2>&1 || true
-
-    if [ -f "$run_py" ] && grep -q '"-c"' "$run_py"; then
-        _sa_harness_log "[harness] self-heal OK -> browser-harness -c is supported now"
-        return 0
-    fi
-    _sa_harness_log "[harness] ERROR: browser-harness still lacks -c after self-heal."
-    _sa_harness_log "[harness] FIX: run 'social-autoposter update' (re-clones/refreshes $src + reinstalls the CLI). The -c flag is CORRECT; browser-harness has NO stdin mode, so do NOT rewrite the cycle to a stdin form."
-    return 1
+    # Retired 2026-06-02. Upstream browser-harness removed `-c` in favor of
+    # stdin-heredoc (commits after merge-base 0e679e2); our server.py wrapper
+    # now passes scripts via stdin (input=script) so the CLI shape doesn't
+    # need any pre-flight probing. The old gate grepped run.py for `"-c"`
+    # which always fails against current upstream, and its "self-heal" was a
+    # `git reset --hard FETCH_HEAD` on ~/Developer/browser-harness that
+    # would clobber local commits AND not actually re-add `-c`. Keep the
+    # name + no-op return so older sourced contexts that call it don't break.
+    return 0
 }
 ensure_harness_c_support || true