Migrate Kira output pipelines to direct push; retire Mac Studio sync cron

VPS investigation complete. Key findings (Kira VPS fleet-agent-03): - ~/output/daily-briefs, news-log, co-op-pulse, deep-dives are all FROZEN since Apr 28-29. No writer currently produces them. - The old publish-daily-rss.sh was disabled in crontab 2026-04-28 (commented out). - The active podcast pipeline (generate-daily-episode.py, cron 0 10 * * 1-5) writes + pushes directly to kira-intel podcast-scripts/ via its own embedded clone ~/agents/news-intel/kira-intel/. Deep-dive queue is read from that clone, not ~/output/. - Scripts at ~/agents/news-intel/news-log/ are the NEW news scanner runtime logs (scan candidates, digests, seen-urls) — NOT content meant for kira-intel. Separate concept, same name. These should NOT be pushed anywhere. - No VPS writer produces daily-briefs, news-log (content), co-op-pulse content anymore. Strategy: Option B for all three — the writers were silently deprecated Apr 28-29 when the podcast pipeline refactor happened. Nothing needs migrating. Just retire the Mac Studio sync cron + the legacy ~/output/ staging dirs. NISC analysis (currently synced via the same Mac Studio cron) is a separate concern — it IS active and needs a new home or to continue pushing via a dedicated NISC sync path. Next: (1) document pipeline architecture on kira-intel, (2) replace the Mac Studio kira-output-sync cron with a NISC-only variant (or migrate NISC into its own push flow), (3) mark legacy sync script deprecated, (4) clean up stale ~/output/ dirs on VPS.