Global modes not imported from roo-code-settings.json export

[KJ7LNW]

Issue

Custom global modes are not properly imported into custom_modes.json from roo-code-settings.json during state reset/import.

Version

v3.11.3

What Happened

When importing settings with custom global modes:

• custom_modes.json exists but is empty after import from roo-code-settings.json
• Preview System Instructions still shows the old mode and its system instructions
• However, custom modes are not persistent after import:
  1. Mode is not selectable from the pulldown menu
  2. Mode is not listed in configure dialog as available
  3. If switched to another mode, cannot switch back to the imported mode

Expected Behavior

Custom modes should be properly imported into custom_modes.json from roo-code-settings.json export, appearing in:

1. The mode selection pulldown menu
2. The configure dialog's available modes list
3. Remain accessible after switching between modes

Steps to Reproduce

1. Create a custom global mode
2. Export all settings to roo-code-settings.json
3. Click the 'Reset State' button
4. Import all settings from roo-code-settings.json
5. Check mode pulldown menu and configure dialog
6. Observe custom_modes.json exists but is empty
7. Click 'Preview System Instructions' - shows old mode and system instructions still exist
8. Try switching to another mode
9. Attempt to switch back to imported mode - fails

Additional Context

While the system retains knowledge of the custom mode and its system instructions (visible in Preview System Instructions), the modes are not being properly imported into custom_modes.json from roo-code-settings.json. This suggests a potential issue with the mode data transfer between these files during the import process.

[julionav]

I'll take a look @hannesrudolph 👀