helix-backup-vs-live-audit-method

To audit helix GitHub backup vs live /root/.claude/skills/: clone repo to /tmp/helix-backup, run diff -rq for file-path identity verification, byte-level comparison per file for content, then run fusion-invariants-lint.py. Clean up /tmp/helix-backup immediately at audit close. 107 identical + 14 enhanced + editorial compression is the expected healthy distribution.

Related

• helix-skills-live-outside-aj-workspace-git
• three-source-model-for-skills-creates-drift-risk
• three-way-file-duplicity-creates-unacceptable-drift-risk
• helix-skill-deployed-vs-backup-path-distinction
• ephemeral-tmp-pattern-for-zero-drift-github-sync
• helix-backup-audit-methodology-via-temp-clone
• helix-backup-audit-byte-level-diff-methodology
• helix-backup-audit-methodology-diff-plus-byte-plus-lint