fix(tests): unblock 14 pre-existing failures in ai-models test suite

[KrasimirKralev]

Summary

14 tests had been red on beta since the Gemma / provider-switch work in PRs #82/#83 landed. CI was useless as a signal — every PR inherited 14 failures regardless of actual correctness. This PR is test-only — no production code changes — and gets CI back to green so real regressions stop hiding in the noise.

Root causes (three independent)

1. Mock drift from configure route's real imports. The route now calls applyModelOverrideToAllAgentSessions and parseFullyQualifiedModel (added in fix(ai-provider): sweep sessions + show switch progress + green banner #83 for session sweeping), plus four getters from @/lib/llamacpp and one from @/lib/local-ai-runtime. The test mocked none of these. First request-time call threw, outer catch returned 500, every test asserting 200 cascaded red. Added the missing mocks with real-shape implementations.

2. vitest-under-bun clears mock implementations along with call history. Factory defaults set inside vi.mock(...) survive vi.resetModules but not vi.clearAllMocks(). Tests passed in isolation, failed in sequence. Re-apply the implementations in beforeEach.

3. ai-models-step.test.tsx relied on llamaCppIsActive defaulting true. The panel only sets it true when currentProviderId === "llamacpp". Added the prop.

Simplifier findings applied

• Mirror real parseFullyQualifiedModel byte-for-byte (idx <= 0 || idx === fq.length - 1) so trailing-slash inputs reject as expected. Fixed the same drift in chat-model.test.ts.
• Extract shared proxy-URL constant via vi.hoisted to avoid duplicating a magic string across two mock factories.

Result

Before: 14 failed / 1055 passed (93 files, 2 red)
After: 1069 passed (93 files, all green)

Test plan

• bun run test — 1069/1069 pass locally
• CI should now show test: SUCCESS for the first time in weeks

[coderabbitai]

Warning

Rate limit exceeded

@KrasimirKralev has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 4 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 26 minutes and 4 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e98976c1-9d7a-43e5-8321-aa1f56eb6e18

📥 Commits

Reviewing files that changed from the base of the PR and between 08259bb and 036a343.

📒 Files selected for processing (3)

• src/tests/components/ai-models-step.test.tsx
• src/tests/routes/ai-models/configure.test.ts
• src/tests/routes/chat-model.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[KrasimirKralev]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.