ephemeral-tmp-pattern-for-zero-drift-github-sync
To sync live skills to a GitHub backup repo without creating persistent local duplicity: clone to /tmp/helix-sync, rsync from live skills path, commit, push, then rm -rf /tmp/helix-sync. The temp dir is cleaned immediately after push — zero persistent intermediate copy, zero drift surface. This is the correct one-shot sync pattern for milestone preservation without violating the two-source model.
Related
- three-way-file-duplicity-creates-unacceptable-drift-risk
- helix-skill-deployed-vs-backup-path-distinction
- docker
- 2026-04-04-oracle-001-self-architecture-analysis
- vault-mcp-repo-local-diverged-from-origin-bidirectionally
three-source-skill-duplicity-creates-drift-risk(archived)three-source-skill-duplicity-creates-unacceptable-drift-risk(archived)- three-source-model-for-skills-creates-drift-risk
- helix-skills-live-outside-aj-workspace-git
- helix-backup-vs-live-audit-method
- helix-backup-audit-methodology-via-temp-clone
- helix-backup-audit-byte-level-diff-methodology
- service-worker-network-caching-insufficient-for-push