fix(core): wire the computed theme into Vuetify so auto dark-mode works

[PierreBrisorgueil]

Summary

• What changed: app.vue now drives Vuetify's theme by calling theme.change(coreStore.theme) inside an { immediate: true } watch, replacing the old self-referential themeName computed that echoed Vuetify's own useTheme().name back into <v-app :theme> (a no-op). vuetify.js now seeds defaultTheme from the resolved config/OS preference so there's no light-theme flash before the watch fires on mount. The redundant :theme="themeName" prop is dropped from <v-app>.
• Why: config.vuetify.theme.dark: 'auto' was dead-wired. core.store.js's syncOsTheme() correctly computed coreStore.theme from isDark(config.vuetify.theme.dark) and main.js wired a real matchMedia listener to keep it live — but nothing read coreStore.theme back into Vuetify. The app stayed light regardless of config or OS setting.
• Related issues: Closes 🔧 Wire the computed theme into Vuetify #4462

Scope

• Modules impacted: app (app.vue), lib/plugins (vuetify.js)
• Cross-module impact: none
• Risk level: low

Validation

• npm run lint
• npm run test:unit
• npm run build
• Manual checks done (if applicable)

Tests note — app.vue.unit.tests.js adds a "theme wiring (#4462)" suite using the real (un-mocked) Pinia coreStore so coreStore.theme is genuinely reactive; assertions are state-based (wrapper.vm.theme.global.name.value) rather than mechanism-based, covering initial mount (immediate) and post-mount flips. Also updated the theme watch to call theme.change(v) instead of assigning theme.global.name.value directly — Vuetify 4.1.5's Proxy set trap deprecates the latter in favor of theme.change() (same synchronous effect, adds theme-name validation, no console noise); the test mock's change() mirrors the real API's effect on global.name.value so the existing state-based assertions still hold. Full suite: 2494 tests green, build green.

Guardrails check

• No secrets or credentials introduced (.env*, secrets/**, keys, tokens)
• No risky rename/move of core stack paths
• Changes remain merge-friendly for downstream projects
• Tests added or updated when behavior changed

Notes for reviewers

• Security considerations: none
• Mergeability considerations: none
• Follow-up tasks (optional): none

https://claude.ai/code/session_01WfNC8bt1TgL4AsiYgCEGup

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8c1d229a-8c21-4c86-a260-b9e5073ade88

📥 Commits

Reviewing files that changed from the base of the PR and between 9cb370d and 46b2dbe.

📒 Files selected for processing (3)

• src/lib/plugins/vuetify.js
• src/modules/app/app.vue
• src/modules/app/tests/app.vue.unit.tests.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/4462-wire-theme-to-vuetify

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.57%. Comparing base (9cb370d) to head (46b2dbe).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4466   +/-   ##
=======================================
  Coverage   99.57%   99.57%           
=======================================
  Files          35       35           
  Lines        1398     1398           
  Branches      439      439           
=======================================
  Hits         1392     1392           
  Misses          6        6           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.