Fix config editor theme alignment and reduce perceived loading

[rabanspiegel]

Summary

• fix Monaco theme registration timing so project config editor reliably uses app theme on first paint
• make Monaco custom theme registration instance-safe across editor mounts
• align config/data file icon colors with explicit light/dark variants for better contrast
• add lightweight config preloading on user intent (hover/focus/click of Edit config) while keeping existing loading fallback

Validation

• npm run format
• npm run lint (passes with existing repo warnings)
• npm run type-check

---

Note

Low Risk
UI/UX-focused changes with small, guarded preload calls and no changes to persistence or auth logic; main risk is minor regressions in config modal loading/theme behavior.

Overview
Improves the Monaco-based project config editor by registering custom themes before editor creation (via beforeMount) so the correct app theme applies on first paint, and by making theme registration idempotent per Monaco instance (using a WeakSet).

Reduces perceived latency when opening the config editor by preloading the project config on user intent (hover/focus/click of Edit config) with a per-project guard and retry-on-failure behavior. Also tweaks File Explorer icon colors (notably .env/JSON/YAML/tooling configs) to use explicit light/dark Tailwind variants for better contrast.

^{Written by Cursor Bugbot for commit abe3113. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Feb 6, 2026 4:44am

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}