chore: stop ignoring Cargo.lock so dependency updates are tracked (#12)

[Liohtml]

Summary

Cargo.lock is actually already tracked in git (committed in the initial commit b4308ff), but .gitignore contradictorily told git to ignore it. The result: the lockfile never picks up dependency-graph updates in commits, defeating the point of committing it for a binary crate.

Removing the gitignore rule lets future cargo update / dependency changes flow through normally. The on-disk lockfile already matches HEAD, so no Cargo.lock change is needed in this commit.

Test plan

• cargo build clean (no Cargo.lock drift)
• git check-ignore -v Cargo.lock now returns nothing
• cargo test, cargo clippy --all-targets -- -D warnings, cargo fmt --check all green

Closes #12

---

Generated by Claude Code

Summary by CodeRabbit

• Chores
  • Updated repository configuration to improve build artifact handling in version control.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dc952c54-5498-454f-9417-58c5580bd420

📥 Commits

Reviewing files that changed from the base of the PR and between 805f55b and e5beb44.

📒 Files selected for processing (1)

• .gitignore

💤 Files with no reviewable changes (1)

• .gitignore

---

📝 Walkthrough

Walkthrough

Updated .gitignore to add ignores for common Rust build artifacts (/target, debug/, *.pdb) and removed the existing Cargo.lock ignore entry. Remaining IDE and OS patterns are unchanged.

Changes

.gitignore Build Configuration

Layer / File(s)	Summary
Build artifact ignores and Cargo.lock removal .gitignore	Added ignores for Rust build outputs /target, debug/, and *.pdb. Removed Cargo.lock from .gitignore to enable committed lockfile for reproducible binary builds.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A rabbit hops through cargo dust,
With lock files safe and build outputs thrust,
Into the ignore, debris swept away—
Reproducible builds shall surely stay! 🔒

🚥 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 PR title accurately and clearly summarizes the main change: removing Cargo.lock from .gitignore to enable tracking of dependency updates.
Linked Issues check	✅ Passed	The PR successfully addresses issue #12 by removing the Cargo.lock entry from .gitignore, enabling reproducible builds and dependency tracking as required.
Out of Scope Changes check	✅ Passed	All changes are directly related to the objective of removing Cargo.lock from .gitignore; no out-of-scope modifications are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/commit-cargo-lock

---

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

[coderabbitai]

Actionable comments posted: 0