[BUG] [ENHANCEMENT] saveProfiles() persists unsanitized settings to disk

[Kirtan-pc]

Description

settingsStore.saveProfiles() writes the full visualizerSettings object to themeProfiles.json without calling sanitizeSettings() first. While the data originated from sanitized sources, any in-memory corruption or mutation (e.g., via a memory-mutation bug or extension) gets persisted permanently. In contrast, duplicateThemeProfile does sanitize before saving.

Steps to Reproduce

1. Open settingsStore.js and locate the saveProfiles() function.
2. Compare it with duplicateThemeProfile() in main.js.
3. Observe that saveProfiles() writes raw settings, while duplicateThemeProfile() sanitizes first.

Expected Behaviour

saveProfiles() should call sanitizeSettings() on the profile data before writing to disk.

Actual Behaviour

Settings are written as-is without re-sanitization.

[github-actions]

Thanks for opening this issue and contributing to Paraline 🌌

The maintainers will review it soon.
If applicable, please make sure to include:

• clear reproduction/details
• screenshots or recordings
• implementation ideas (optional but appreciated)

Thanks again for helping improve the project 👍

[Kirtan-pc]

Hi @SamXop123 ,

I would like to work on this issue under GSSoC 2026.

Could you please assign this issue to me?

Thank you!