social-autoposter 1.6.44 → 1.6.46

package/mcp/dist/index.js

@@ -16,7 +16,7 @@ import { z } from "zod";
 import os from "node:os";
 import path from "node:path";
 import fs from "node:fs";
-import { REPO_DIR, runPython, run, readPlan, writePlan, planPath, latestBatchId, } from "./repo.js";
+import { REPO_DIR, runPython, run, readPlan, writePlan, planPath, } from "./repo.js";
 import { applySetup, resolveProject, hasReadyProject, listManagedProjectStatus, REQUIRED_FIELDS, RECOMMENDED_FIELDS, CONFIG_PATH, } from "./setup.js";
 import { xStatus, xConnect, summarizeXAuth } from "./twitterAuth.js";
 import { VERSION, versionStatus, latestPublishedVersion } from "./version.js";
@@ -180,7 +180,8 @@ function cycleProgressMessage(line) {
     let m;
     if (/=== Twitter Cycle \(batch=/.test(l))
         return "Starting draft cycle…";
-    if ((m = /^Selected projects?:\s*(.+)$/.exec(l)))
+    // NB: lines carry a `[HH:MM:SS] ` timestamp prefix, so don't anchor on ^.
+    if ((m = /Selected projects?:\s*(.+)$/.exec(l)))
         return `Selected project: ${m[1]}`;
     if (/phase=phase1\b/.test(l) || /Phase 1: drafting queries/.test(l))
         return "Searching X for fresh threads…";
@@ -206,28 +207,67 @@ async function produceDrafts(project, onProgress) {
     const env = {
         DRAFT_ONLY: "1",
         TWITTER_PAGE_GEN_RATE: "0",
+        // Interactive draft_cycle: launch the harness Chrome ON-SCREEN so the user
+        // can watch the scan/scrape happen live. Cron/autopilot do NOT set these, so
+        // background runs keep the off-screen default in twitter-backend.sh and don't
+        // hijack the screen. (Only affects a fresh Chrome launch; an already-running
+        // harness window keeps its current position.)
+        BH_WINDOW_POS: "60,60",
+        BH_WINDOW_SIZE: "1280,900",
     };
     if (project)
         env.SAPS_FORCE_PROJECT = project;
     let step = 0;
+    let lastMsg = "";
+    // ONE predictable, host-independent place to watch a draft_cycle run, so any
+    // agent (or human) debugging "the cycle looks stuck" has an obvious path:
+    //   ~/social-autoposter/skill/logs/draft_cycle-mcp.log
+    // It lives right next to the cycle's own twitter-cycle-*.log. We append the
+    // full live cycle output here (not just milestones) plus a clear run banner.
+    // Best-effort: a logging failure must never break the cycle.
+    const mcpLog = path.join(REPO_DIR, "skill", "logs", "draft_cycle-mcp.log");
+    const appendLog = (s) => {
+        try {
+            fs.appendFileSync(mcpLog, s);
+        }
+        catch {
+            /* ignore — never fail the cycle over a log write */
+        }
+    };
+    try {
+        fs.mkdirSync(path.dirname(mcpLog), { recursive: true });
+    }
+    catch {
+        /* ignore */
+    }
+    appendLog(`\n===== draft_cycle start ${new Date().toISOString()} ` +
+        `project=${project ?? "(default)"} =====\n`);
     const res = await run("bash", ["skill/run-twitter-cycle.sh"], {
         env,
         timeoutMs: 900_000, // scan+draft can take several minutes
-        // Mirror the cycle's own log lines to THIS server's stderr (so they land
-        // in the host's mcp-server-social-autoposter.log, which used to show only
-        // the JSON-RPC handshake) AND forward milestone lines to the live progress
-        // sink so the chat spinner stops looking frozen.
+        // Fan every cycle line out to THREE sinks so progress is never a black box:
+        //   1. draft_cycle-mcp.log  — the stable, documented, host-independent file.
+        //   2. this server's stderr — lands in the host's MCP server log
+        //      (mcp-server-social-autoposter.log on Desktop), which used to show
+        //      only the JSON-RPC handshake.
+        //   3. the live progress sink — milestone messages under the chat spinner.
         onLine: (line) => {
             const t = line.replace(/\s+$/, "");
-            if (t.trim())
+            if (t.trim()) {
+                appendLog(`${t}\n`);
                 console.error(`[draft_cycle] ${t}`);
+            }
             if (!onProgress)
                 return;
             const msg = cycleProgressMessage(t);
-            if (msg)
+            // Skip consecutive duplicates (a phase can log a couple matching lines).
+            if (msg && msg !== lastMsg) {
+                lastMsg = msg;
                 onProgress(msg, ++step);
+            }
         },
     });
+    appendLog(`===== draft_cycle end ${new Date().toISOString()} exit=${res.code} =====\n`);
     // Prefer the explicit marker; fall back to the newest plan file on disk.
     const marker = /DRAFT_ONLY_PLAN=\/tmp\/twitter_cycle_plan_(.+)\.json/.exec(res.stdout + "\n" + res.stderr);
     if (marker && marker[1])
@@ -239,13 +279,17 @@ async function produceDrafts(project, onProgress) {
     if (blockedMarker && blockedMarker[1]) {
         return { batchId: null, blocked: blockedReasonMessage(blockedMarker[1]) };
     }
-    const existing = latestBatchId();
-    if (existing)
-        return { batchId: existing };
+    // No `DRAFT_ONLY_PLAN=` marker from THIS run => this run produced no drafts.
+    // We MUST NOT fall back to the newest plan file on disk (`latestBatchId()`):
+    // that's a *previous* run's batch, so a 5-second empty cycle would echo an old
+    // 7-draft batch and report phantom success. Report 0 drafts honestly, with the
+    // pipeline's own reason (e.g. cold-start project with no seeded queries).
     return {
         batchId: null,
-        blocked: `Draft cycle produced no plan (exit ${res.code}). This usually means scan ` +
-            `found no fresh candidates, or the pipeline errored. Tail:\n` +
+        blocked: `This run produced no drafts (exit ${res.code}). The scan found no fresh ` +
+            `candidates for the selected project — usually a cold-start project with ` +
+            `no seeded search queries/topics, or a pipeline error. This is NOT a ` +
+            `previous batch. Tail:\n` +
             res.stderr.split("\n").slice(-12).join("\n"),
     };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "social-autoposter",
-  "version": "1.6.44",
+  "version": "1.6.46",
   "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"