test(verify): assert NotificationSettings user interaction and badge outputs

[google-labs-jules]

Generated by: .github/nightly-prompts/02-verification.md

Reasoning:

[Coverage Gap]: The modernized @features/settings component NotificationSettings.vue had untested interaction pathways (toggles for background sync, quiet mode, and sound control) and dynamic badge previews under specific threshold values (50 vs 75).
[Scenarios Added]: Added 5 unit tests verifying background sync, quiet mode, and sound toggle clicks, and confirming that correct badge preview text is rendered for thresholds 50 and 75.
[Rationale]: This target is in the high-priority queue because NotificationSettings.vue was recently modified in the current daily run cycles by preceding stages (Stage 12 and Stage 6).

Changes:

• [Component/File]: Updated NotificationSettings.spec.ts with 5 new unit tests.
• [Component/File]: Cleaned up unused import flushPromises.

Verification:

• [Automated]: Confirmed pnpm test passes against the target spec file with 13/13 tests passed successfully.
• [Automated/Audit]: Confirmed the entire workspace test suite passes cleanly with 1413 passed tests.

Log Updates:

• Updated .github/nightly-logs/02-verification-coverage.log
• Updated .github/nightly-logs/00-pr-history.md
• Updated .github/nightly-logs/00-pipeline-intelligence.md

---

PR created automatically by Jules for task 6353706562740997682 started by @AlbiDR

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

[supabase]

This pull request has been ignored for the connected project hucktamloykszinwbtuh because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.