…omponent

The DEFAULT_PERMISSIONS constant in Permissions.svelte was missing the new import/export permission fields (models_import, models_export, prompts_import, prompts_export, tools_import, tools_export). This caused the reactive fillMissingProperties function to not properly initialize these fields, preventing the toggles from saving correctly.

When a user toggled these switches, the values weren't properly tracked because the DEFAULT_PERMISSIONS object used in the reactive merge didn't include them.

The WorkspacePermissions Pydantic model was missing the new import/export permission fields, causing the backend to silently strip them out during validation when saving group permissions. This was the root cause of toggles not persisting.

Added missing fields to WorkspacePermissions:
- models_import
- models_export
- prompts_import
- prompts_export
- tools_import
- tools_export

These fields are used by both /users/default/permissions endpoint and group permissions storage. Without them in the Pydantic schema, any values sent from the frontend were being dropped during model validation.

The config.py was missing the environment variable constants and DEFAULT_USER_PERMISSIONS entries for the new import/export permissions:

Added constants:
- USER_PERMISSIONS_WORKSPACE_MODELS_IMPORT
- USER_PERMISSIONS_WORKSPACE_MODELS_EXPORT
- USER_PERMISSIONS_WORKSPACE_PROMPTS_IMPORT
- USER_PERMISSIONS_WORKSPACE_PROMPTS_EXPORT
- USER_PERMISSIONS_WORKSPACE_TOOLS_IMPORT
- USER_PERMISSIONS_WORKSPACE_TOOLS_EXPORT

Added to DEFAULT_USER_PERMISSIONS["workspace"]:
- models_import
- models_export
- prompts_import
- prompts_export
- tools_import
- tools_export

Without these, the config system couldn't properly load or save the new permission fields, causing them to be lost even if the Pydantic models accepted them.