Chaim
80a5daa3e3
The writer, learning panels, and legal_mcp tools run from the HOST tree (Paperclip agents claude -p with cwd=~/legal-ai; pm2 services import from mcp-server/src) — not the container. A merge + Coolify deploy only refreshes the FastAPI container; host-side code stayed on the last manual `git pull`. On 2026-06-28 the host was 16 commits behind, so a day of learning-loop fixes sat dormant until pulled by hand. host_sync.sh (run every minute via cron, like the existing data/training pull) fast-forwards the host tree to origin/main when it falls behind. Fast-forward ONLY — never forces, so the perpetually-dirty .taskmaster/tasks/tasks.json is never clobbered (clean ff leaves it; an upstream conflict logs + bails for manual handling). Agent runs spawn fresh and pick up new code with no restart; only the long-running pm2 services that import app code (chat_service, court_fetch_service, reaper) are restarted, and only when their own files changed (precise, minimal churn). Logs to data/logs/host_sync.log. Cron entry (added on the host, flock-guarded): * * * * * flock -n /tmp/host_sync.lock bash ~/legal-ai/scripts/host_sync.sh SCRIPTS.md updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>