test(git): cover commit range rename provenance

[nia-sg-bot]

Summary

• add a deterministic commit-range fixture for a renamed-and-modified file
• verify the resolver retains both paths, both modes, and immutable old/new blob IDs

Validation

• python3 -m pytest -q (146 passed)
• git diff --check origin/main...HEAD

Part of #21

Summary by CodeRabbit

• Tests
  • Added coverage for commit ranges involving renamed and modified files.
  • Verified that file paths, permissions, and content identities are preserved correctly.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1b41c5cf-2de7-4347-a3c0-f8f08ddb2188

📥 Commits

Reviewing files that changed from the base of the PR and between 21699a6 and a20547f.

📒 Files selected for processing (1)

• tests/test_git_snapshot.py

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

---

Walkthrough

The change adds a commit-range test for a file that is renamed and then modified. The test checks paths, modes, rename status, blob IDs, and content identity.

Changes

Git snapshot validation

Layer / File(s)	Summary
Rename and modification assertions tests/test_git_snapshot.py	The test verifies rename status, old and new paths, file modes, immutable endpoint blob IDs, and different old and new content identities.

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

Merge Risk: ⚪ Minimal · up to a2054

This change adds deterministic coverage for renamed-file provenance without changing production behavior; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 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 added Git commit-range test for rename provenance. It matches the main change.
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.

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch nia/issue-21-range-rename-provenance

---

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.