Skip to content

fix: stop ignored local files from churning vault history - #68

Merged
AksharP5 merged 1 commit into
mainfrom
fix/ignored-file-hash-churn
Sep 10, 2026
Merged

fix: stop ignored local files from churning vault history#68
AksharP5 merged 1 commit into
mainfrom
fix/ignored-file-hash-churn

Conversation

@AksharP5

Copy link
Copy Markdown
Owner

What changed

A Git-ignored transcript made Arch and Mac overwrite the same skill hash every sync, producing hundreds of registry-only commits. Registry generation and validation now exclude untracked files ignored by Git. Fixes #67.

Why

The previous hash included local files that Git never sent to other devices. Git supplies the ignored paths once per registry build or validation; tracked files remain included even when an ignore rule matches.

Safety and compatibility

  • Existing vault migration: the next sync corrects affected hashes once, with no schema change.
  • Local-file behavior: ignored files stay in place; copy overwrite protection still checks all deployed files.
  • Destructive behavior: no file removal or history rewrite.
  • Cross-device behavior: upgrade devices to prevent older versions restoring local-only hashes.

Validation

  • npm test: 112 tests pass, including two-clone hash stability, tracked ignored files, deletion, repeated imports, and copy drift protection.
  • npm pack --dry-run
  • git diff --check
  • Patched hashing on the actual Arch skill matches the Mac's hash. macOS/Linux CI runs on this PR.

@AksharP5
AksharP5 merged commit e6619d3 into main Sep 10, 2026
6 checks passed
@AksharP5 AksharP5 mentioned this pull request Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Registry hashes churn when a skill contains Git-ignored local files

1 participant