@m13v/s4l 1.6.197-rc.7

package/skill/run-linkedin-launchd.sh

@@ -0,0 +1,81 @@
+#!/bin/bash
+# run-linkedin-launchd.sh — detach wrapper invoked by launchd.
+#
+# Why this exists:
+#   launchd's StartInterval silently SUPPRESSES a scheduled fire when the prior
+#   invocation of the same Label is still alive. Before 2026-05-01 the
+#   linkedin pipeline held the linkedin-browser lock for the full 25-45min
+#   run, so wrapping it would just queue blocked-on-lock processes with no
+#   throughput gain. On 2026-05-01 run-linkedin.sh was refactored to acquire
+#   linkedin-browser only around its two Claude phases (~5min each), freeing
+#   the lock during DB ingest / candidate pick / Phase B prep windows.
+#   With that change the wrapper becomes useful: parallel cycles can run
+#   their non-browser phases concurrently, and the lock + lock.sh's FIFO
+#   ticket queue serialize the brief browser windows fairly.
+#
+# How it works:
+#   Python double-fork daemon idiom — first fork gives launchd a parent that
+#   exits immediately (so the job is marked complete in milliseconds), setsid
+#   detaches the session, second fork prevents reacquiring a controlling
+#   terminal, then we exec the real pipeline. macOS lacks `setsid(1)` and
+#   `nohup ... & disown` is not enough because launchd reaps the wrapper's
+#   pgid, taking the nohup child with it.
+#
+# LinkedIn-specific risk:
+#   Per CLAUDE.md memory feedback_linkedin_session_fingerprint, anti-bot can
+#   fire on sequential agent re-auths even when the lock prevents parallel
+#   Chromes. Pre-wrapper steady state was ~2 cycles/hr × 2 fresh Chrome
+#   sessions/cycle = 4 sessions/hr. Post-wrapper it can rise to ~4 cycles/hr
+#   × 2 = 8 sessions/hr (peak). If LinkedIn restrictions return, REVERT this
+#   wrapper first (point the plist back at run-linkedin.sh directly) before
+#   touching the OAuth API or browser profile.
+
+REPO_DIR="$HOME/social-autoposter"
+LOG_DIR="$REPO_DIR/skill/logs"
+mkdir -p "$LOG_DIR"
+
+# LinkedIn killswitch (2026-05-27): refuse to even fork the daemon if a
+# prior fire detected session compromise (http_999, authwall, throttle,
+# li_at cleared). Cheaper than letting the inner script discover it.
+# State: ~/.claude/social-autoposter/linkedin.killswitch
+# Clear: python3 ~/social-autoposter/scripts/linkedin_killswitch.py clear
+if [ -f "$HOME/.claude/social-autoposter/linkedin.killswitch" ]; then
+    echo "[$(date +%H:%M:%S)] LINKEDIN_KILLSWITCH active. Skipping run-linkedin." \
+        >> "$LOG_DIR/launchd-linkedin-stderr.log"
+    exit 0
+fi
+
+SCRIPT="$REPO_DIR/skill/run-linkedin.sh"
+OUT="$LOG_DIR/launchd-linkedin-stdout.log"
+ERR="$LOG_DIR/launchd-linkedin-stderr.log"
+
+# Preflight (added 2026-05-02): skip cleanly if Claude is blocked on a
+# quota cap, or if the system is under memory pressure. See
+# scripts/preflight.sh for full design.
+SA_PREFLIGHT_SCRIPT="run-linkedin"
+source "$REPO_DIR/scripts/preflight.sh"
+preflight_skip_if_claude_blocked
+preflight_skip_if_jetsam_pressure
+
+exec /usr/bin/python3 -c "
+import os, sys
+script  = '$SCRIPT'
+out_log = '$OUT'
+err_log = '$ERR'
+
+if os.fork() != 0:
+    os._exit(0)
+os.setsid()
+
+if os.fork() != 0:
+    os._exit(0)
+
+os.chdir('/')
+out_fd = os.open(out_log, os.O_WRONLY | os.O_CREAT | os.O_APPEND, 0o644)
+err_fd = os.open(err_log, os.O_WRONLY | os.O_CREAT | os.O_APPEND, 0o644)
+nul_fd = os.open('/dev/null', os.O_RDONLY)
+os.dup2(nul_fd, 0)
+os.dup2(out_fd, 1)
+os.dup2(err_fd, 2)
+os.execv(script, [script])
+"

package/skill/run-linkedin-unipile.sh

@@ -0,0 +1,130 @@
+#!/usr/bin/env bash
+# run-linkedin-unipile.sh: LinkedIn "post comments" pipeline via the UniPile API
+# (search posts, then post a comment). This is the UniPile-backed counterpart to
+# the browser-driven run-linkedin.sh. It talks ONLY to the UniPile REST API
+# through scripts/linkedin_unipile.py: no browser, no linkedin-agent, no browser
+# lock, no killswitch gate (there is no browser session to compromise here).
+#
+# "post comments" means searching for posts and commenting on them (outbound).
+# This is NOT the "engage" pipeline (engage-linkedin.sh, which replies to replies
+# left on our own comments).
+#
+# Default behavior is DRY RUN: it probes credentials, searches, and prints the
+# comment it *would* post. A posted comment is visible to real people, so it only
+# publishes when you pass --post AND --text.
+#
+# Usage:
+#   ./run-linkedin-unipile.sh --keywords "ai agents" --date-posted past_week --limit 5
+#   ./run-linkedin-unipile.sh --keywords "..." --text "nice breakdown" --post
+#   ./run-linkedin-unipile.sh --social-id "urn:li:activity:NNN" --text "..." --post
+#
+# Creds: the live UniPile account is under matt@mediar.ai (keychain entries scoped
+# to that account; DSN api45.unipile.com:17570, account_id wHDpysUnRbm7Q0lvyv9pQQ).
+# An older i@m13v.com trial shares the same service names but is dead.
+# linkedin_unipile.py reads the mediar-scoped entry; we also pin UNIPILE_DSN here
+# as a default (override by exporting it).
+
+set -euo pipefail
+
+: "${UNIPILE_DSN:=api45.unipile.com:17570}"
+export UNIPILE_DSN
+
+REPO_DIR="$HOME/social-autoposter"
+PY="$REPO_DIR/scripts/linkedin_unipile.py"
+LOG_DIR="$REPO_DIR/skill/logs"
+mkdir -p "$LOG_DIR"
+LOG_FILE="$LOG_DIR/engage-linkedin-unipile-$(date +%Y-%m-%d_%H%M%S).log"
+
+KEYWORDS=""
+SEARCH_URL=""
+DATE_POSTED="past_week"
+SORT_BY="date"
+LIMIT=5
+TEXT=""
+SOCIAL_ID=""
+REPLY_TO=""
+DO_POST=0
+
+log() { echo "[$(date +%H:%M:%S)] $*" | tee -a "$LOG_FILE"; }
+
+while [ $# -gt 0 ]; do
+    case "$1" in
+        --keywords)     KEYWORDS="$2"; shift 2 ;;
+        --url)          SEARCH_URL="$2"; shift 2 ;;
+        --date-posted)  DATE_POSTED="$2"; shift 2 ;;
+        --sort-by)      SORT_BY="$2"; shift 2 ;;
+        --limit)        LIMIT="$2"; shift 2 ;;
+        --text)         TEXT="$2"; shift 2 ;;
+        --social-id)    SOCIAL_ID="$2"; shift 2 ;;
+        --reply-to)     REPLY_TO="$2"; shift 2 ;;
+        --post)         DO_POST=1; shift ;;
+        -h|--help)
+            grep '^#' "$0" | sed 's/^# \{0,1\}//'; exit 0 ;;
+        *) echo "unknown arg: $1" >&2; exit 2 ;;
+    esac
+done
+
+log "=== UniPile LinkedIn post comments (search, then comment) ==="
+log "DSN=$UNIPILE_DSN  dry_run=$([ "$DO_POST" -eq 1 ] && echo no || echo YES)"
+
+# ── Step 1: validate credentials ──────────────────────────────────────────
+log "Step 1: probing credentials (/accounts)..."
+if ! python3 "$PY" probe 2>>"$LOG_FILE" | tee -a "$LOG_FILE"; then
+    log "CREDENTIAL PROBE FAILED. UniPile rejected the API key (see above)."
+    log "Fix: the live account is matt@mediar.ai (the i@m13v.com trial is dead). Refresh the"
+    log "     subscription if needed, then store the key under the mediar-scoped entry:"
+    log "     security add-generic-password -U -s unipile-api-key -a matt@mediar.ai -w '<KEY>'"
+    log "     and DSN:   security add-generic-password -U -s unipile-dsn -a matt@mediar.ai -w 'apiNN.unipile.com:PORT'"
+    exit 1
+fi
+
+# ── Step 2: resolve a target post ─────────────────────────────────────────
+# Either the caller named a --social-id directly, or we search and take the top
+# result. We always print the search results so the run is auditable.
+if [ -z "$SOCIAL_ID" ]; then
+    if [ -z "$KEYWORDS" ] && [ -z "$SEARCH_URL" ]; then
+        log "Nothing to do: pass --keywords/--url to search, or --social-id to target a post."
+        exit 2
+    fi
+    log "Step 2: searching posts (keywords='${KEYWORDS}' url='${SEARCH_URL}' date=$DATE_POSTED limit=$LIMIT)..."
+    SEARCH_ARGS=(search --limit "$LIMIT" --sort-by "$SORT_BY")
+    [ -n "$KEYWORDS" ]    && SEARCH_ARGS+=(--keywords "$KEYWORDS" --date-posted "$DATE_POSTED")
+    [ -n "$SEARCH_URL" ]  && SEARCH_ARGS+=(--url "$SEARCH_URL")
+    SEARCH_JSON=$(python3 "$PY" "${SEARCH_ARGS[@]}" 2>>"$LOG_FILE") || {
+        log "SEARCH FAILED (see log)."; exit 1; }
+    echo "$SEARCH_JSON" | tee -a "$LOG_FILE"
+    SOCIAL_ID=$(echo "$SEARCH_JSON" | python3 -c "import json,sys; items=json.load(sys.stdin).get('items',[]); print(items[0]['social_id'] if items and items[0].get('social_id') else '')")
+    if [ -z "$SOCIAL_ID" ]; then
+        log "No usable post (no social_id in top result). Stopping before comment."
+        exit 0
+    fi
+    log "Top result social_id: $SOCIAL_ID"
+else
+    log "Step 2: skipping search, using provided --social-id $SOCIAL_ID"
+fi
+
+# ── Step 3: comment (or dry-run) ──────────────────────────────────────────
+if [ -z "$TEXT" ]; then
+    log "No --text provided; nothing to post. Target post: https://www.linkedin.com/feed/update/$SOCIAL_ID/"
+    log "Done (search-only)."
+    exit 0
+fi
+
+if [ "$DO_POST" -ne 1 ]; then
+    log "DRY RUN — would comment on $SOCIAL_ID:"
+    log "  \"$TEXT\""
+    log "Re-run with --post to actually publish. (No API write performed.)"
+    exit 0
+fi
+
+log "Step 3: posting comment on $SOCIAL_ID ..."
+COMMENT_ARGS=(comment --social-id "$SOCIAL_ID" --text "$TEXT")
+[ -n "$REPLY_TO" ] && COMMENT_ARGS+=(--reply-to "$REPLY_TO")
+if python3 "$PY" "${COMMENT_ARGS[@]}" 2>>"$LOG_FILE" | tee -a "$LOG_FILE"; then
+    log "Comment posted. Watch the m13v LinkedIn account for any flag/challenge over the next 24-48h."
+else
+    log "COMMENT FAILED (see log)."
+    exit 1
+fi
+
+log "=== Done ==="