🧪 [testing improvement] Add missing tests for ClaimEvidence::validate

[undivisible]

🎯 What: Added tests for the ClaimEvidence::validate method in src/model.rs, ensuring coverage for validation logic regarding empty text fields and invalid confidence values.

📊 Coverage: Covered the following scenarios:

• Happy path (valid ClaimEvidence)
• Confidence value exceeding the maximum allowed (10_001 > 10_000)
• Empty text fields for tenant_id, person_id, claim_id, and evidence_id using various spacing (e.g., "", " ", " ").

✨ Result: Improved test coverage and reliability for ClaimEvidence validation logic, ensuring robust handling of empty string fields and correct validation boundary limits.

---

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

---

Note

Low Risk
Test-only change with no production code modifications.

Overview
Adds unit tests for ClaimEvidence::validate in src/model.rs.

Covers the happy path, confidence above the 10_000 basis-point limit, and empty/whitespace IDs for tenant, person, claim, and evidence.

^{Reviewed by Cursor Bugbot for commit b263740. 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_a4ef2dd5-0143-4a28-9fbc-8af12dad907a)

[undivisible]

Superseded by the reviewed and merged integration in #22.

[google-labs-jules]

Superseded by the reviewed and merged integration in #22.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.