@m13v/s4l 1.7.4-rc.34 → 1.7.4-rc.35

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,4 +1,4 @@
1
1
  {
2
- "version": "1.7.4-rc.34",
3
- "installedAt": "2026-07-13T22:53:49.281Z"
2
+ "version": "1.7.4-rc.35",
3
+ "installedAt": "2026-07-14T00:14:09.998Z"
4
4
  }
package/mcp/manifest.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "dxt_version": "0.1",
3
3
  "name": "social-autoposter",
4
4
  "display_name": "S4L",
5
- "version": "1.7.4-rc.34",
5
+ "version": "1.7.4-rc.35",
6
6
  "description": "Draft, review, approve, and autopilot X/Twitter posts.",
7
7
  "long_description": "## **⚠️ The disclaimer above is generic Claude boilerplate.** Anthropic shows the same warning on every plugin regardless of what it does; any plugin has the same level of access as any app you download from the internet.\n\nS4L is an open source product developed by Mediar.ai Incorporated, a VC-backed San Francisco-based startup.\n\nTo get started:\n\n1\\. Copy this prompt: **Set me up on S4L plugin end to end**\n\n2\\. Quit with CMD+Q, reopen Claude, paste into a new chat.\n\nWhat happens next:\n\n* About every 5 minutes S4L scans X for posts that match your topics and drafts replies in your voice.\n* Drafts show up as review cards, usually the first within a few minutes. Nothing is posted automatically; you approve each one.\n* Posting autopilot stays off until you explicitly turn it on.",
8
8
  "author": {
package/mcp/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@m13v/s4l-mcp",
3
- "version": "1.7.4-rc.34",
3
+ "version": "1.7.4-rc.35",
4
4
  "private": true,
5
5
  "description": "Desktop MCP client for social-autoposter (X/Twitter rail): manual draft/review/approve loop, autopilot control, and stats. Thin wrapper over the existing pipeline scripts.",
6
6
  "license": "MIT",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@m13v/s4l",
3
- "version": "1.7.4-rc.34",
3
+ "version": "1.7.4-rc.35",
4
4
  "description": "Automated social posting pipeline for Reddit, X/Twitter, LinkedIn, and Moltbook. Install as a Claude Code agent skill.",
5
5
  "bin": {
6
6
  "social-autoposter": "bin/cli.js",
@@ -232,22 +232,47 @@ ensure_twitter_browser_for_backend() {
232
232
  echo "[$(date -u +%Y-%m-%dT%H:%M:%SZ)] Harness Chrome down on port 9555, launching..." >&2
233
233
  else
234
234
  local _ready_verdict
235
+ # TWO-STRIKE gate (2026-07-13): one failed handshake is NOT proof of a
236
+ # wedge. Under heavy system load (observed at loadavg ~18) a perfectly
237
+ # healthy Chrome blows the 8s Playwright attach budget, and a
238
+ # single-failure kill produced 3 false wedge-kills in one day on the
239
+ # operator Mac — each one a relaunch flash plus an "Aw, Snap" corpse
240
+ # tab from the SIGKILLed renderer. First failure: stamp a strike file
241
+ # and proceed WITHOUT killing (a truly wedged Chrome makes the cycle's
242
+ # own pre-flight fail loudly right after, so nothing silently hangs).
243
+ # Second consecutive failure within 30 minutes: genuinely wedged, kill
244
+ # + relaunch. A passing check clears any stale strike.
245
+ local _strike="/tmp/s4l_cdp_wedge_strike_9555"
235
246
  if ! _ready_verdict=$(_bh_cdp_ready "$_BH_DEFAULT_URL"); then
236
- _need_launch=1; _launch_reason="cdp_wedge"
237
- echo "[$(date -u +%Y-%m-%dT%H:%M:%SZ)] Harness Chrome WEDGED on port 9555 (/json/version answers but the CDP handshake never completes: ${_ready_verdict:-no verdict}); killing and relaunching..." >&2
238
- # Machine-greppable marker (same stderr-marker convention as
239
- # twitter_access_gate; bin/server.js parses these).
240
- echo "twitter_cdp_wedge: detected url=$_BH_DEFAULT_URL action=restart" >&2
241
- _bh_record_cdp_health wedge_restart "$_ready_verdict"
242
- local _wedge_pids
243
- _wedge_pids=$(pgrep -f -- "--user-data-dir=$_bh_prof_dir " 2>/dev/null || true)
244
- if [ -n "$_wedge_pids" ]; then
245
- kill $_wedge_pids 2>/dev/null || true
246
- sleep 2
247
+ if [ -z "$(find "$_strike" -mmin -30 2>/dev/null)" ]; then
248
+ touch "$_strike"
249
+ echo "[$(date -u +%Y-%m-%dT%H:%M:%SZ)] Harness Chrome failed the CDP handshake check (${_ready_verdict:-no verdict}); first strike — NOT killing (loaded-machine tolerance). Second consecutive failure within 30m triggers the wedge heal." >&2
250
+ echo "twitter_cdp_wedge: detected url=$_BH_DEFAULT_URL action=first_strike" >&2
251
+ _bh_record_cdp_health wedge_first_strike "$_ready_verdict"
252
+ # Fall through WITHOUT killing: session restore + tab cleanup
253
+ # below still run.
254
+ else
255
+ rm -f "$_strike" 2>/dev/null || true
256
+ _need_launch=1; _launch_reason="cdp_wedge"
257
+ echo "[$(date -u +%Y-%m-%dT%H:%M:%SZ)] Harness Chrome WEDGED on port 9555 (second consecutive handshake failure: ${_ready_verdict:-no verdict}); killing and relaunching..." >&2
258
+ # Machine-greppable marker (same stderr-marker convention as
259
+ # twitter_access_gate; bin/server.js parses these).
260
+ echo "twitter_cdp_wedge: detected url=$_BH_DEFAULT_URL action=restart" >&2
261
+ _bh_record_cdp_health wedge_restart "$_ready_verdict"
262
+ local _wedge_pids
247
263
  _wedge_pids=$(pgrep -f -- "--user-data-dir=$_bh_prof_dir " 2>/dev/null || true)
248
- [ -n "$_wedge_pids" ] && { kill -9 $_wedge_pids 2>/dev/null || true; sleep 1; }
249
- rm -f "$_bh_prof_dir/SingletonLock" "$_bh_prof_dir/SingletonSocket" "$_bh_prof_dir/SingletonCookie" 2>/dev/null || true
264
+ if [ -n "$_wedge_pids" ]; then
265
+ kill $_wedge_pids 2>/dev/null || true
266
+ sleep 2
267
+ _wedge_pids=$(pgrep -f -- "--user-data-dir=$_bh_prof_dir " 2>/dev/null || true)
268
+ [ -n "$_wedge_pids" ] && { kill -9 $_wedge_pids 2>/dev/null || true; sleep 1; }
269
+ rm -f "$_bh_prof_dir/SingletonLock" "$_bh_prof_dir/SingletonSocket" "$_bh_prof_dir/SingletonCookie" 2>/dev/null || true
270
+ fi
250
271
  fi
272
+ else
273
+ # Healthy handshake — clear any earlier strike so isolated blips
274
+ # never accumulate into a kill.
275
+ rm -f "$_strike" 2>/dev/null || true
251
276
  fi
252
277
  fi
253
278
  if [ "$_need_launch" = 1 ]; then