Track Cargo.lock (workspace builds an executable)

[gilesknap]

What this does

Starts tracking Cargo.lock. It was git-ignored, but this workspace builds an executable (the eyes2 binary; eyes2-lib is an unpublished path dependency, not a published library), so per Cargo's guidance the lock file should be committed for reproducible builds. The .gitignore even carried the standard reminder ("Remove Cargo.lock from gitignore if creating an executable").

Changes

• Remove the Cargo.lock entry from .gitignore (replaced with a note explaining why it's now tracked).
• Commit Cargo.lock, generated from the current main manifests.

Notes

• Independent of the feature stack (Add evolving RISC genome as the giles creature controller #5 → Parallelise the simulation across all cores (parallel think / serial resolve) #10 → Add giles assembler, disassembler and a TUI inspector #8); it touches only .gitignore and adds Cargo.lock, so it can merge to main on its own with no conflicts.
• The lock reflects main's dependencies, so it does not yet contain rayon (added by Parallelise the simulation across all cores (parallel think / serial resolve) #10). Once Parallelise the simulation across all cores (parallel think / serial resolve) #10 lands, the next build updates the lock to include it; happy to refresh it then if you'd like the entries in before that.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Qb4gora6fHgAR5y1WQS6C1

---

Generated by Claude Code

Summary by CodeRabbit

• Chores
  • Updated repository configuration to include lock file in version control.

[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: f0e8f80b-e346-495c-b8fc-801c4bf2af07

📥 Commits

Reviewing files that changed from the base of the PR and between 59d441d and 44075d3.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• .gitignore

---

📝 Walkthrough

Walkthrough

The .gitignore file removes the rule that excluded Cargo.lock from version control and replaces it with comments explaining that Cargo.lock should be committed because this workspace builds an executable.

Changes

Cargo.lock Tracking

Layer / File(s)	Summary
Remove Cargo.lock ignore rule .gitignore	Replaces the Cargo.lock ignore entry with a comment stating the file should be committed for this executable workspace.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 Hop hop, no more hiding that lock,
The Cargo.lock stays right on the dock!
An executable needs its roots true,
Committed forever in version control's view.
✨ The bunny cheers — now nothing's amiss!

🚥 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 accurately and specifically describes the main change: tracking Cargo.lock with the rationale that the workspace builds an executable.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ 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/track-cargo-lock

---

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