Provider: Import/Export Config + Persona/System-Prompt Customization (M2 #18)

[ddroid]

What to build

Import/export provider config: Allow users to export their provider configuration (base URLs, model selections, non-secret settings) to a file and import it on another machine. Secrets (API keys) must be excluded from exports.

Persona/system-prompt customization: Allow users to customize the system prompt sent to the model. The built-in Ronin capability-boundary prompt remains the default, but users can add their own persona instructions. The UI must clearly show what system prompt will be sent to the model — no hidden instructions.

Design decisions needed (HITL):

• Where does the system-prompt editor live? (Settings page? Per-thread? Global + per-thread override?)
• How are multiple personas managed? (Simple text field vs. named persona profiles?)
• Should the export format be TOML to match config.toml?

Acceptance criteria

• User can export provider config to a file (TOML or chosen format)
• Exported config excludes all secrets (API keys, tokens)
• User can import a provider config file to restore settings
• Import validates the config and reports errors clearly
• User can view and edit the system prompt that will be sent to the model
• Built-in Ronin system prompt is shown as the default and is clearly labeled
• Custom persona text is appended to or replaces the default (user's choice)
• Current effective system prompt is visible/inspectable before sending
• System prompt customization persists across sessions
• No hidden instructions are sent beyond what the user can see

Blocked by

None - can start immediately