test(git): cover binary commit-range provenance

[nia-sg-bot]

Summary

• add a deterministic commit-range fixture for binary add, modify, and delete changes
• assert immutable pre/post blob IDs are preserved without decoding binary content

Part of #21.

Validation

• python3 -m pytest tests/test_git_snapshot.py
• python3 -m pytest
• git diff --check

Remaining work

This verifies the binary-file acceptance slice. The parent issue still tracks the broader resolver contract and its remaining edge-case fixtures.

Summary by CodeRabbit

• Tests
  • Expanded validation of file-change history across commit ranges, including binary edits, additions, and deletions. Checks now verify that reported file versions match the selected revisions and that these scenarios produce no warnings.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 9b7ac695-d651-45c8-9458-7c5a5c361b0d

📥 Commits

Reviewing files that changed from the base of the PR and between 3519a32 and 47ff9a9.

📒 Files selected for processing (1)

• tests/test_git_snapshot.py

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The change adds a commit-range test for binary file edits, additions, and deletions. It checks blob IDs against the endpoint commits, verifies that all three paths appear in the result, and expects no warnings.

Changes

Binary blob provenance tests

Layer / File(s)	Summary
Commit-range blob provenance tests/test_git_snapshot.py	Adds checks for old and new blob IDs on edited, added, and deleted binary files. The test also checks result paths and expects no warnings.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 47ff9

This change only adds test coverage for binary file provenance in commit ranges. It does not alter runtime behavior and carries no identified merge risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the change: a test for binary commit-range provenance.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 1 files.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[nia-sg-bot]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.