fix(model): drop non-string tags from modelSearch response

[danmrichards]

Numeric IDs appear in the tags array when a server-side join fails. These are internal artefacts — silently skip them rather than failing to unmarshal the response.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. To trigger a review, include coderabbit-review in the PR description. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b661778b-b36d-4c48-b85d-c35dcbb3edf0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch fix/model-search-non-string-tag

---

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

[Copilot]

Pull request overview

This PR aims to make modelSearch response decoding resilient to server-side data issues where the tags array may contain non-string elements (e.g., numeric IDs), by dropping those elements instead of failing JSON unmarshalling.

Changes:

• Introduces a ModelTags helper type with custom JSON unmarshalling that filters out non-string values.
• Updates ModelResult.Tags to use the new decoding behavior (currently via a type change).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Ryank90]

lgtm