Enable auto-sync scripts for cross-machine parity
Auto-sync scripts enabled
Decision
Enable auto-sync for three surfaces:
- MEMORY.md — Stop hook push, SessionStart hook pull (per
memory-cross-machine-sync-2026-07-03). - globals-derived — SessionStart hook checks workspace-vs-globals drift, fires grill-me on non-trivial diff.
- Mirror hosts — GH Actions cron pushes to 6 mirrors weekly (per
mirror-all-hosts-setup— already scheduled, verify).
Reverses 2026-06-29 stance ("don't sync automatically anyway anything for now i will do it individually") because cross-machine sync now in scope.
Why revoke manual-only
- Cross-machine sync locked — MEMORY between corp + personal laptops requires auto-push/pull to work at all. Manual runs = forgotten runs = stale memory.
- Grill-on-drift preserved — auto doesn't mean silent. Non-trivial drift still surfaces MCQ.
- Zero-friction failover — dropped Sonnet fleet means if CC breaks on corp, personal laptop must be ready in <5 minutes. Auto-sync makes that real.
Confidence: medium
- New hook surface — bugs likely.
- Grill-on-drift depends on
claudeCLI being available in hook context. Fallback = interactive PowerShell prompt. - Watch for: hook execution time bloating session start; conflicts between corp + personal + laptop offline; sops key not decrypting on new machine.
Rollback
- Revert this decision by re-locking manual-only.
- Remove hooks from
~/.claude/settings.jsontemplate. - Delete auto-push/pull scripts.
Anti-patterns
- ❌ Auto-sync without grill-on-drift — silent overwrites.
- ❌ Push on every tool call — Stop-hook only (once per session).
- ❌ Auto-run on machines without sops key — fails gracefully, doesn't corrupt.