social-autoposter 1.6.149 → 1.6.151

package/mcp/dist/index.js

@@ -1037,9 +1037,9 @@ tool("engagement_mode", {
         "toggle.",
     inputSchema: {
         action: z
-            .enum(["get", "set"])
+            .enum(["get", "set", "toggle"])
             .optional()
-            .describe("get = read current mode + persona status. set = record the user's chosen mode."),
+            .describe("get = read current mode + persona status. set = record the user's chosen mode (provisions the persona). toggle = lightweight flip promotion<->personal_brand (mode.json only, no persona work) — the dashboard/menu-bar quick toggle."),
         mode: z
             .enum(["personal_brand", "promotion"])
             .optional()
@@ -1070,6 +1070,20 @@ tool("engagement_mode", {
         const persona = findPersonaProject();
         return jsonContent({ mode, persona: persona ? persona.name : null });
     }
+    // Lightweight flip (the dashboard/menu-bar quick toggle): just rewrite
+    // mode.json via saps_mode.py — NO persona provisioning. Mirrors the menu
+    // bar's pure-local _toggle_mode so flipping from either surface is cheap.
+    if (action === "toggle") {
+        const cur = await runPython("scripts/saps_mode.py", ["get"], { timeoutMs: 15_000 });
+        const now = (cur.stdout || "").trim() || "promotion";
+        const next = now === "personal_brand" ? "promotion" : "personal_brand";
+        const res = await runPython("scripts/saps_mode.py", ["set", next], { timeoutMs: 15_000 });
+        if (res.code !== 0) {
+            const tail = (res.stderr || res.stdout).trim().split("\n").slice(-1)[0] || "unknown error";
+            return textContent(`Could not switch mode: ${tail}`);
+        }
+        return jsonContent({ mode: next });
+    }
     const mode = args.mode;
     if (mode !== "personal_brand" && mode !== "promotion") {
         return textContent("Ask the user which they want, then call again with mode:'personal_brand' (organic brand " +
@@ -1435,6 +1449,7 @@ tool("project_config", {
             mcp_version: ver.installed,
             latest_version: ver.latest,
             update_available: ver.update_available,
+            mode: currentMode(),
             update_hint: ver.update_available
                 ? `A newer version (${ver.latest}) is available — you're on ${ver.installed}. ` +
                     `Tell the user and offer to run the \`runtime\` tool with action:'update' ` +
@@ -2062,7 +2077,7 @@ async function autopilotLoaded() {
 // fires every minute, claims ONE job, runs the pipeline's own prompt as its
 // Claude turn, writes the result back, and stops.
 // ===========================================================================
-const QUEUE_WORKER_PROMPT_VERSION = 5; // v5: drop the per-run draft cap (v3/v4). The ~90s kills were NOT a drafting-time limit; they were unattended permission-prompt stalls on un-auto-approved Bash calls. Real fix = blanket Bash allow in queueWorkerAllowedTools so no prompt is ever emitted. Worker drafts the FULL set again.
+const QUEUE_WORKER_PROMPT_VERSION = 6; // v6: the ~90s kill is a host INACTIVITY watchdog (resets on each tool call), not a fixed cap. The worker was drafting all candidates in ONE silent turn (its HARD RULES even forbade log_draft.py), starving the clock -> killed mid-draft. v6 requires incremental draft-then-log per candidate and allows the log_draft.py persist commands, so per-candidate tool calls keep the session alive and the full set drains.
 const QUEUE_WORKER_PROMPT_MARKER = "saps_queue_worker_prompt_version";
 // One spec per worker task. queueType MUST match scripts/claude_job.py TAG_TO_TYPE.
 const QUEUE_WORKERS = [
@@ -2165,6 +2180,13 @@ function queueWorkerBody(spec) {
     const job = path.join(repoDir(), "scripts", "claude_job.py");
     const sd = sapsStateDir();
     const outDir = queueDir();
+    // The Phase-2b "twitter-prep" worker drafts replies for several candidates. The
+    // host kills an unattended scheduled session ~90s after its LAST tool call (an
+    // inactivity watchdog). Drafting everything in one silent turn starves that clock
+    // and the session is killed mid-draft having submitted nothing. So it MUST work
+    // incrementally — draft + run log_draft.py per candidate — which persists drafts
+    // (the pipeline already wants this) AND keeps the activity clock alive.
+    const isDraft = spec.queueType === "twitter-prep";
     return [
         `You are the S4L "${spec.human}" queue worker. Run ONE iteration, then STOP.`,
         ``,
@@ -2174,6 +2196,23 @@ function queueWorkerBody(spec) {
             `You do this with Bash and Write, and NOTHING else. This run is unattended — ` +
             `reaching for any other tool, or trying to "investigate", STALLS it forever.`,
         ``,
+        ...(isDraft
+            ? [
+                `PACING — CRITICAL: this unattended session is terminated ~90 seconds after ` +
+                    `your LAST tool call (a host inactivity timeout). The prompt below asks ` +
+                    `you to draft replies for SEVERAL candidates. Do NOT draft them all ` +
+                    `silently in one turn — that emits no tool calls, the clock expires, and ` +
+                    `you are KILLED mid-draft having submitted NOTHING. Work ONE candidate at ` +
+                    `a time: draft its reply, then IMMEDIATELY run that candidate's ` +
+                    `log_draft.py command exactly as the prompt's persist step (3a) specifies ` +
+                    `(a quick Bash call), THEN move to the next. Those per-candidate Bash ` +
+                    `calls are what keep the session alive. Begin the first candidate ` +
+                    `promptly — do NOT spend a long silent stretch analysing before your ` +
+                    `first tool call. Only after EVERY candidate is drafted and logged do you ` +
+                    `do step 3.`,
+                ``,
+            ]
+            : []),
         `Steps:`,
         `1. Claim the next job. Run this EXACT Bash command:`,
         `     ${py} ${job} next --type ${spec.queueType} --prompt-file --state-dir ${sd}`,
@@ -2196,11 +2235,18 @@ function queueWorkerBody(spec) {
         `4. Report in ONE short line what you did, then STOP. Do NOT claim another job, ` +
             `do NOT loop, do NOT read other files, do NOT call any other tool.`,
         ``,
-        `HARD RULES: ONLY the Bash tool (to run claude_job.py), the Read tool (to read ` +
-            `the prompt/schema sidecar files), and the Write tool (to write the result ` +
-            `file). NEVER run any other shell command. NEVER edit, post, or touch anything ` +
-            `else. An empty queue is the NORMAL, expected case most minutes — it is success, ` +
-            `not a problem to debug.`,
+        isDraft
+            ? `HARD RULES: use ONLY the Bash tool (to run claude_job.py AND the per-candidate ` +
+                `log_draft.py persist commands the prompt tells you to run), the Read tool (the ` +
+                `prompt/schema sidecar + the SKILL/config files the prompt names), and the Write ` +
+                `tool (the result file). NEVER post, reply, edit a draft, open a browser, or run ` +
+                `any command the prompt does not explicitly give you. An empty queue is the ` +
+                `NORMAL, expected case most minutes — it is success, not a problem to debug.`
+            : `HARD RULES: ONLY the Bash tool (to run claude_job.py), the Read tool (to read ` +
+                `the prompt/schema sidecar files), and the Write tool (to write the result ` +
+                `file). NEVER run any other shell command. NEVER edit, post, or touch anything ` +
+                `else. An empty queue is the NORMAL, expected case most minutes — it is success, ` +
+                `not a problem to debug.`,
     ].join("\n");
 }
 // Full canonical SKILL.md (frontmatter + body + version marker) the MCP writes
@@ -2753,6 +2799,8 @@ async function buildSnapshot() {
         runtime_ready: rtReady,
         runtime_provisioning: isProvisioning(),
         setup_complete: setupComplete,
+        // Engagement mode for display in BOTH surfaces (single source: mode.json).
+        mode: currentMode(),
         onboarding: onboardingLive,
     };
     // Persist this snapshot so the menu bar can answer "set up?" the SAME way when
@@ -2915,6 +2963,18 @@ function modeChosen() {
         return false;
     }
 }
+// The current engagement mode ('promotion' | 'personal_brand'), surfaced in the
+// snapshot so the dashboard AND menu bar read it from ONE place (mode.json, the
+// same file saps_mode.py writes). Defaults to promotion when unset.
+function currentMode() {
+    try {
+        const m = (JSON.parse(fs.readFileSync(path.join(sapsStateDir(), "mode.json"), "utf-8")).mode || "").trim();
+        return m === "personal_brand" ? "personal_brand" : "promotion";
+    }
+    catch {
+        return "promotion";
+    }
+}
 // ---- Cross-instance "posting active" flag ----------------------------------
 // posting-active.json in the shared state dir is the CROSS-MCP-INSTANCE version
 // of the in-process `postingActive` flag. The autopilot scan and the post