test: close frontend production coverage gaps

[seonghobae]

Purpose

Use the exact-head coverage diagnostic from #152 to close the remaining currently-observed frontend production coverage gaps without weakening thresholds or excluding production modules.

Exact protected-main base at branch creation: 7a86b3dae0c941bc59edfde146c9d7498a0c75a0.

The #152 exact-head diagnostic at ca487aecd18a11e310f2c0b8fbe452cf9eeabbf9 reported only two frontend files with uncovered lines/branches: src/lib/cloudReviewQueue.ts and src/routes/+layout.ts. This PR adds focused behavior tests only; it does not change production code, coverage thresholds, workflow policy, or #152's coverage-control ownership.

Coverage closure

• exercise both comparison directions for bytes-desc, production-asc, and production-desc queue sorting;
• exercise deterministic relative-path/metadata tie-breaking;
• exercise empty, matching, and missing review-reason filters;
• import the actual SvelteKit layout contract and assert Tauri SPA SSR remains disabled.

Evidence discipline

The #152 diagnostic is RED evidence, not success evidence. This PR must pass its own exact-head Test/Release/security/SAST checks first. After integration, #152 must be refreshed/rebuilt from the new protected main and independently prove the expanded all-production frontend coverage gate; predecessor #152 evidence does not transfer across the new base.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 757b7d84-f47e-45df-b665-7ca3fd3f4281

📥 Commits

Reviewing files that changed from the base of the PR and between 7a86b3d and b60c2f0.

📒 Files selected for processing (2)

• src/lib/cloudReviewQueue.coverage.test.ts
• src/routes/layout.test.ts

---

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