test(themes): add comprehensive Vitest coverage — hex validity, theme count, structure, and AUTO_THEME integrity

[ChetanSenta]

Description

Fixes #4181

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

No visual change — pure test additions.

What this PR does

lib/svg/themes.test.ts previously had only 3 tests covering 2 specific
themes. This PR adds 45 new tests covering 4 critical gaps:

Gap	Tests Added
Hex validity — all 20 themes × 3 properties	60 values checked via it.each
Theme count matches THEMES.md (20 themes)	2 tests
Every theme has exactly bg/text/accent keys	it.each per theme
AUTO_THEME_LIGHT and AUTO_THEME_DARK integrity	11 tests
Known palette regression guards	4 tests

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally.
• I have run npm run format and npm run lint locally and resolved all errors.
• My commits follow the Conventional Commits format.
• I have updated README.md if I added a new theme or URL parameter.
• I have starred the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse premium quality aesthetic standard.
• (Recommended) I joined the CommitPulse Discord server.

[github-actions]

🚨 Hey @ChetanSenta, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[Aamod-Dev]

Thanks for putting this together. The code looks clean and solves the issue effectively.

I am adding the quality:exceptional label because the implementation not only solves the core issue but goes beyond by effectively handling edge cases, tests, or reducing technical debt. Great work going above and beyond!

Looks solid. I'll go ahead and approve.

[Aamod-Dev]

Thanks for the contribution. I went through the changes and the overall approach looks good, but there are a few issues that should be addressed before this can be merged. Most of the concerns are related to correctness and maintainability.

• There are merge conflicts with the base branch. Please resolve them to ensure existing functionality isn't broken.

Once these issues are addressed, I'll be happy to take another look. Thanks again for the contribution.

[Aamod-Dev]

Thanks for the contribution. The overall approach looks good, but the CI pipeline is currently failing. Please run the checks (like npm run format, npm run lint, and npm run test) locally to identify and fix the issues. Let me know once it's green!

[ChetanSenta]

Thanks for the contribution. The overall approach looks good, but the CI pipeline is currently failing. Please run the checks (like npm run format, npm run lint, and npm run test) locally to identify and fix the issues. Let me know once it's green!

done ✔️

[Aamod-Dev]

Thanks for fixing the CI pipeline! Approving.

[github-actions]

🎉 Congratulations @ChetanSenta! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨