MCC deploy: protect remote linkedin-feed.json harvest output from rsync clobber (TK-10504)

189b7f71b7d9f67e79f56673f474581288c08639 · 2026-08-12 14:30:54 -0700 · Steve Abrams

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Files touched

M .deploy.conf

Diff

commit 189b7f71b7d9f67e79f56673f474581288c08639
Author: Steve Abrams <steve@designerwallcoverings.com>
Date:   Wed Aug 12 14:30:54 2026 -0700

    MCC deploy: protect remote linkedin-feed.json harvest output from rsync clobber (TK-10504)
    
    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .deploy.conf | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/.deploy.conf b/.deploy.conf
index 7a7ad78..30ce8de 100644
--- a/.deploy.conf
+++ b/.deploy.conf
@@ -21,4 +21,6 @@ HEALTH_URL=http://127.0.0.1:9662/api/health
 # stale local copy would clobber live status — protect them like the channels-*
 # files. (engine-queue.json is also git-tracked, a latent trap; excluding here is
 # the deploy-side guard regardless.)
-RSYNC_EXTRA_EXCLUDES="follow-counts-history.json follow-counts-accounts.json follow-counts-snapshot.out follow-counts-snapshot.err clients-notes.json channels-outbox.json channels-tokens.json meta-pages.json assets.json assets-catalog.cache.json engine-queue.json engine-config.json"
+# linkedin-feed.json is the openclaw harvest output (TK-10504) — generated on the
+# remote by the running MCC; a stale/absent local copy must never clobber it.
+RSYNC_EXTRA_EXCLUDES="follow-counts-history.json follow-counts-accounts.json follow-counts-snapshot.out follow-counts-snapshot.err clients-notes.json channels-outbox.json channels-tokens.json meta-pages.json assets.json assets-catalog.cache.json engine-queue.json engine-config.json linkedin-feed.json"

← 46e18c8 MCC LinkedIn: Network Feed — openclaw harvest of own feed + · back to Marketing Command Center · auto-data-snapshot: 2026-08-12T14:30:58 (20 data files) — pa 7c9bd03 →