chore: remove unused uuid dependency

[pnodet]

Removes the uuid dependency from Cargo.toml — nothing in the codebase references it (src/main.rs is the only source file and has no uuid usage). Cargo.lock updated accordingly.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@pnodet, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8a19f185-0937-4f7a-86d4-177b0d77a1c3

📥 Commits

Reviewing files that changed from the base of the PR and between e20b82b and 8f0f49d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• Cargo.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/remove-unused-uuid

---

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.}

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[pnodet]

Thermo-Nuclear Code Quality Review

Verdict: Approve. This is exactly what the PR title says and nothing else — a pure dead-dependency removal. No findings.

What was verified

• Diff scope: touches only Cargo.toml (removes the uuid = { version = "1.9.1", features = ["v4"] } line) and Cargo.lock. No source changes snuck in.
• No remaining references: grep -ri uuid src/ Cargo.toml comes back empty. The only uuid left in the tree is the Cargo.lock stanza, which is correct — it is a transitive dependency of the las crate and must stay.
• Build: cargo build passes cleanly, and the lockfile is stable after the build (no drift).

Lockfile notes (all benign, no action needed)

• With the direct uuid dependency (and its v4 feature) gone, getrandom and wasi correctly drop out of the lock graph — las uses uuid without the v4 feature.
• The las-cleanup lock entry moves 0.0.1 → 0.0.2. That is a fix, not noise: main's lockfile was stale relative to Cargo.toml (already at 0.0.2 since a24fbd9), and regenerating the lockfile synced it.
• Lockfile format bumps version = 3 → version = 4 from regenerating with a current cargo toolchain. Harmless; just means contributors need a reasonably recent cargo, which the repo's CI toolchain already satisfies.

Removing a dependency is the best kind of change this skill can hope for: it deletes complexity outright. Ship it.