helix-backup-audit-methodology-via-temp-clone

Verified pattern for auditing live skills against a GitHub backup: clone repo to a temp location (e.g. /tmp/helix-backup), run diff -rq per file, compare byte counts with du, then run fusion-invariants-lint.py against live. Clean up temp clone immediately after. This produces a reproducible, zero-ambiguity audit trail without polluting workspace state.

Related

• helix-backup-vs-live-audit-method
• ephemeral-tmp-pattern-for-zero-drift-github-sync
• three-source-model-for-skills-creates-drift-risk
• three-way-file-duplicity-creates-unacceptable-drift-risk
• helix-skills-live-outside-aj-workspace-git
• helix-backup-audit-byte-level-diff-methodology