Patch Paperclip source to cap recovery chain depth at 500

Found the actual bug. Confirmed via @paperclipai/server npm tarball:
firstBlockedChainFinding does proper cycle detection via Set.has,
but the chain in user data is genuinely 1000+ deep (created by a
runaway recovery-issue loop). Each recursive call also clones the
Set into new Set(seen), so memory blows up too.

Fix: sed-patch the if-check to also bail when seen.size > 500.
This short-circuits deep linear chains without affecting normal
graphs. Patch runs in the builder stage before pnpm build.

Reverted SQL purge and --unhandled-rejections=none from start.sh —
neither addressed the root cause.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Dockerfile

@@ -11,6 +11,13 @@ RUN apt-get update && apt-get install -y \
 # Clone Paperclip (depth=1 for speed, uses repo's default branch)
 RUN git clone --depth=1 https://github.com/paperclipai/paperclip.git .
 
+# Patch firstBlockedChainFinding to cap chain depth at 500.
+# Default 1MB stack overflows on deep recovery-issue chains created by
+# runaway agents. Cycle detection is already in place via the Set; we
+# add a size cap so deep linear chains short-circuit instead of crashing.
+RUN sed -i 's|if (seen.has(current.id))|if (seen.size > 500 || seen.has(current.id))|' \
+    server/src/services/recovery/issue-graph-liveness.ts
+
 # Install dependencies (corepack picks correct pnpm version from packageManager field)
 RUN pnpm install
 

start.sh

@@ -212,40 +212,9 @@ cleanup() {
 }
 trap cleanup SIGTERM SIGINT
 
-# ── Purge orphaned heartbeat run that triggers recovery stack overflow ───────
-ORPHAN_RUN_ID="1fc2bf0e-f983-4ec7-b941-2df338d53ab4"
-echo "Purging orphaned run ${ORPHAN_RUN_ID} from all UUID columns..."
-su - postgres -c "psql paperclip" <<SQLEOF >/dev/null 2>&1 || true
-\echo 'Heartbeat/run tables:'
-SELECT tablename FROM pg_tables
- WHERE schemaname='public'
-   AND (tablename LIKE '%heartbeat%' OR tablename LIKE '%run%');
-
-DO \$\$
-DECLARE
-    rec RECORD;
-    rid uuid := '${ORPHAN_RUN_ID}';
-BEGIN
-    FOR rec IN
-        SELECT n.nspname AS s, t.relname AS tn, a.attname AS cn
-          FROM pg_attribute a
-          JOIN pg_class t ON a.attrelid = t.oid
-          JOIN pg_namespace n ON t.relnamespace = n.oid
-          JOIN pg_type ty ON a.atttypid = ty.oid
-         WHERE n.nspname='public' AND t.relkind='r'
-           AND ty.typname='uuid' AND NOT a.attisdropped
-    LOOP
-        BEGIN
-            EXECUTE format('DELETE FROM %I.%I WHERE %I = \$1', rec.s, rec.tn, rec.cn) USING rid;
-        EXCEPTION WHEN OTHERS THEN NULL;
-        END;
-    END LOOP;
-END \$\$;
-SQLEOF
-
 # ── Launch Paperclip ──────────────────────────────────────────────────────────
 echo "Starting Paperclip..."
-node --unhandled-rejections=none --import ./server/node_modules/tsx/dist/loader.mjs server/dist/index.js &
+node --import ./server/node_modules/tsx/dist/loader.mjs server/dist/index.js &
 PAPERCLIP_PID=$!
 
 # Wait for API ready (max 90s)