chore(conductor): Add new track 'Saved System Prompt Presets'

conductor/tracks.md

@@ -125,6 +125,10 @@ This file tracks all major tracks for the project. Each track has its own detail
     *Link: [./tracks/gui_path_config_20260308/](./tracks/gui_path_config_20260308/)*
     *Goal: Add path configuration UI to Context Hub. Allow users to view and edit configurable paths directly from the GUI.*
 
+29. [ ] **Track: Saved System Prompt Presets**
+    *Link: [./tracks/saved_presets_20260308/](./tracks/saved_presets_20260308/)*
+    *Goal: Ability to have saved presets for global and project system prompts. Includes full AI profiles with temperature and top_p settings, managed via a dedicated GUI modal.*
+
 ---
 
 ## Completed / Archived

conductor/tracks/saved_presets_20260308/index.md

@@ -0,0 +1,5 @@
+# Track saved_presets_20260308 Context
+
+- [Specification](./spec.md)
+- [Implementation Plan](./plan.md)
+- [Metadata](./metadata.json)

conductor/tracks/saved_presets_20260308/metadata.json

@@ -0,0 +1,8 @@
+{
+  "track_id": "saved_presets_20260308",
+  "type": "feature",
+  "status": "new",
+  "created_at": "2026-03-08T12:35:00Z",
+  "updated_at": "2026-03-08T12:35:00Z",
+  "description": "Ability to have saved presets for global and project system prompts."
+}

conductor/tracks/saved_presets_20260308/plan.md

@@ -0,0 +1,46 @@
+# Implementation Plan: Saved System Prompt Presets
+
+## Phase 1: Foundation & Data Model
+- [ ] Task: Define the `Preset` data model and storage logic.
+    - [ ] Create `src/models.py` (if not existing) or update it with a `Preset` dataclass/Pydantic model.
+    - [ ] Implement `PresetManager` in a new file `src/presets.py` to handle loading/saving to `presets.toml` and `project_presets.toml`.
+    - [ ] Implement the inheritance logic where project presets override global ones.
+- [ ] Task: Write unit tests for `PresetManager`.
+    - [ ] Test loading global presets.
+    - [ ] Test loading project presets.
+    - [ ] Test the override logic (same name).
+    - [ ] Test saving/updating presets.
+- [ ] Task: Conductor - User Manual Verification 'Phase 1: Foundation & Data Model' (Protocol in workflow.md)
+
+## Phase 2: UI: Settings Integration
+- [ ] Task: Add Preset Dropdown to Global AI Settings.
+    - [ ] Modify `gui_2.py` to include a dropdown in the "AI Settings" panel.
+    - [ ] Populated the dropdown with available global presets.
+- [ ] Task: Add Preset Dropdown to Project Settings.
+    - [ ] Modify `gui_2.py` to include a dropdown in the "Project Settings" panel.
+    - [ ] Populated the dropdown with available project-specific presets (including overridden globals).
+- [ ] Task: Implement "Auto-Load" logic.
+    - [ ] When a preset is selected, update the active system prompt and model settings in `gui_2.py`.
+- [ ] Task: Write integration tests for settings integration using `live_gui`.
+    - [ ] Verify global dropdown shows global presets.
+    - [ ] Verify project dropdown shows project + global presets.
+    - [ ] Verify selecting a preset updates the UI fields (prompt, temperature).
+- [ ] Task: Conductor - User Manual Verification 'Phase 2: UI: Settings Integration' (Protocol in workflow.md)
+
+## Phase 3: UI: Preset Manager Modal
+- [ ] Task: Create the `PresetManagerModal` in `gui_2.py` (or a separate module).
+    - [ ] Implement a list view of all presets (global and project).
+    - [ ] Implement "Add", "Edit", and "Delete" functionality.
+    - [ ] Ensure validation for unique names.
+- [ ] Task: Add a button to open the manager modal from the settings panels.
+- [ ] Task: Write integration tests for the Preset Manager using `live_gui`.
+    - [ ] Verify creating a new preset adds it to the list and dropdown.
+    - [ ] Verify editing an existing preset updates it correctly.
+    - [ ] Verify deleting a preset removes it from the list and dropdown.
+- [ ] Task: Conductor - User Manual Verification 'Phase 3: UI: Preset Manager Modal' (Protocol in workflow.md)
+
+## Phase 4: Final Integration & Polish
+- [ ] Task: Ensure robust error handling for missing or malformed `.toml` files.
+- [ ] Task: Final UI polish (spacing, icons, tooltips).
+- [ ] Task: Run full suite of relevant tests.
+- [ ] Task: Conductor - User Manual Verification 'Phase 4: Final Integration & Polish' (Protocol in workflow.md)

conductor/tracks/saved_presets_20260308/spec.md

@@ -0,0 +1,39 @@
+# Specification: Saved System Prompt Presets
+
+## Overview
+This feature introduces the ability to save, manage, and switch between system prompt presets for both global (application-wide) and project-specific contexts. Presets will include not only the system prompt text but also model-specific parameters like temperature and top_p, effectively allowing for "AI Profiles."
+
+## Functional Requirements
+- **Dedicated Storage:**
+    - Global presets: Stored in a global `presets.toml` file (located in the application configuration directory).
+    - Project presets: Stored in a `project_presets.toml` file within the project's root directory.
+- **Preset Content:**
+    - `name`: A unique identifier for the preset.
+    - `system_prompt`: The text of the system prompt.
+    - `temperature`: (Optional) Model temperature setting.
+    - `top_p`: (Optional) Model top_p setting.
+    - `max_output_tokens`: (Optional) Maximum output tokens.
+- **Inheritance & Overriding:**
+    - The UI will display a unified list of global and project-specific presets.
+    - If a project-specific preset has the same name as a global one, the project-specific version will override it.
+- **GUI Interactions:**
+    - **Settings Dropdown:** A dropdown menu in the "AI Settings" (global) and "Project Settings" (per-project) panels for quick switching between presets.
+    - **Preset Manager Modal:** A dedicated modal accessible from the settings panels to create, edit, and delete presets.
+    - **Auto-Loading:** Switching a preset in the dropdown will immediately update the active system prompt and associated model parameters in the AI client configuration.
+
+## Non-Functional Requirements
+- **Persistence:** All changes made in the Preset Manager must be immediately persisted to the corresponding `.toml` file.
+- **Validation:** Ensure preset names are unique within their scope (global or project).
+- **Concurrency:** Ensure safe file access if multiple windows or instances are open (though Manual Slop is primarily single-instance).
+
+## Acceptance Criteria
+- [ ] Users can create a new global preset and see it in the dropdown across all projects.
+- [ ] Users can create a project-specific preset that is only visible when that project is active.
+- [ ] Overriding a global preset with a project-specific one (same name) correctly loads the project version.
+- [ ] Changing a preset via the dropdown updates the active AI configuration (prompt, temperature, etc.).
+- [ ] The Preset Manager modal allows for full CRUD (Create, Read, Update, Delete) operations on presets.
+
+## Out of Scope
+- Support for other file formats (e.g., JSON, YAML) for presets.
+- Presets for specific files or folders (scoped only to global or project level).
+- Cloud syncing of presets.