🧪 Add tests for CompileError type_error constructor

[undivisible]

🎯 What: Added missing unit tests for the CompileError::type_error constructor in in-cli/src/compile_error.rs.
📊 Coverage: The new tests cover both &str and String inputs (the impl Into<String> parameter), asserting that the resulting CompileError correctly sets the category to ErrorCategory::TypeError and correctly stores the provided message.
✨ Result: Improved test coverage for CompileError constructors, ensuring their properties are correctly initialized and protecting against future regressions.

---

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

---

Note

Low Risk
Test-only change with no runtime or behavioral impact on the compiler CLI.

Overview
Adds a dedicated unit test type_error_constructor in compile_error.rs that exercises CompileError::type_error with both &str and owned String inputs (via impl Into<String>).

The test asserts each error has ErrorCategory::TypeError and preserves the message text. No production code changes—test coverage only.

^{Reviewed by Cursor Bugbot for commit f998be3. 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_6aba22ce-a505-4e60-adbb-133f80b65174)

[mergify]

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

• Queue this pull request