🧹 Refactor tests in cargo_linker to use Result instead of unwrap

[undivisible]

🎯 What:
Replaced unwrap() calls on std I/O operations (fs::create_dir_all, fs::write) with the ? operator in the tests test_compile_cargo_dependencies_finds_and_compiles and test_compile_cargo_dependencies_invalid_cargo_toml within in-cli/src/cargo_linker.rs.

💡 Why:
Using unwrap() can cause tests to hard crash when dealing with standard library I/O, giving less helpful stack traces or abrupt exits. By correctly setting the test signatures to return std::io::Result<()> and using ?, failures are properly bubbled up natively via the test framework, making it safer, more readable, and idiomatically aligned with standard Rust testing practices.

✅ Verification:
Ran local module tests via cargo test cargo_linker and full test suite via IN_TEST_SKIP_SWIFT=1 ./install.sh && ~/.local/bin/in test. Verified no new warnings/errors with cargo clippy. Formatting is verified with cargo fmt.

✨ Result:
Test functions now safely handle errors natively without unsafe unwrap calls.

---

PR created automatically by Jules for task 9621440658014606791 started by @undivisible

---

Note

Low Risk
Test-only refactor with no production or runtime behavior changes.

Overview
Refactors two cargo_linker unit tests so setup I/O uses std::io::Result<()> and ? instead of unwrap() on fs::create_dir_all and fs::write.

test_compile_cargo_dependencies_finds_and_compiles and test_compile_cargo_dependencies_invalid_cargo_toml now end with Ok(()); behavior under test is unchanged. test_compile_cargo_dependencies_no_cargo_toml is untouched.

This is test-only cleanup—no production code changes.

^{Reviewed by Cursor Bugbot for commit 9d61e9b. Configure here.}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_336a43d4-dec5-4b41-b8a6-6186369f8f2a)

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request