chore(conductor): Add new tracks for 'Session Context Snapshots' and 'Discussion Takes'

conductor/tracks/session_context_snapshots_20260311/index.md

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

conductor/tracks/session_context_snapshots_20260311/metadata.json

@@ -0,0 +1,8 @@
+{
+  "track_id": "session_context_snapshots_20260311",
+  "type": "feature",
+  "status": "new",
+  "created_at": "2026-03-11T19:30:00Z",
+  "updated_at": "2026-03-11T19:30:00Z",
+  "description": "Session Context Snapshots & Visibility: Tying files/screenshots to active session, saving Context Presets, MMA assignment, and agent-focused session filtering."
+}

conductor/tracks/session_context_snapshots_20260311/plan.md

@@ -0,0 +1,24 @@
+# Implementation Plan: Session Context Snapshots & Visibility
+
+## Phase 1: Backend Support for Context Presets
+- [ ] Task: Write failing tests for saving, loading, and listing Context Presets in the project configuration.
+- [ ] Task: Implement Context Preset storage logic (e.g., updating TOML schemas in `project_manager.py`) to manage file/screenshot lists.
+- [ ] Task: Conductor - User Manual Verification 'Phase 1: Backend Support for Context Presets' (Protocol in workflow.md)
+
+## Phase 2: GUI Integration & Persona Assignment
+- [ ] Task: Write tests for the Context Hub UI components handling preset saving and loading.
+- [ ] Task: Implement the UI controls in the Context Hub to save current selections as a preset and load existing presets.
+- [ ] Task: Update the Persona configuration UI (`personas.py` / `gui_2.py`) to allow assigning a named Context Preset to an agent persona.
+- [ ] Task: Conductor - User Manual Verification 'Phase 2: GUI Integration & Persona Assignment' (Protocol in workflow.md)
+
+## Phase 3: Transparent Context Visibility
+- [ ] Task: Write tests to ensure the initial aggregate markdown, resolved system prompt, and file injection timestamps are accurately recorded in the session state.
+- [ ] Task: Implement UI elements in the Session Hub to expose the aggregated markdown and the active system prompt.
+- [ ] Task: Enhance the discussion timeline rendering in `gui_2.py` to visually indicate exactly when files and screenshots were injected into the context.
+- [ ] Task: Conductor - User Manual Verification 'Phase 3: Transparent Context Visibility' (Protocol in workflow.md)
+
+## Phase 4: Agent-Focused Session Filtering
+- [ ] Task: Write tests for the GUI state filtering logic when focusing on a specific agent's session.
+- [ ] Task: Relocate the 'Focus Agent' feature from the Operations Hub to the MMA Dashboard.
+- [ ] Task: Implement the action to filter the Session and Discussion hubs based on the selected agent's context.
+- [ ] Task: Conductor - User Manual Verification 'Phase 4: Agent-Focused Session Filtering' (Protocol in workflow.md)

conductor/tracks/session_context_snapshots_20260311/spec.md

@@ -0,0 +1,28 @@
+# Specification: Session Context Snapshots & Visibility
+
+## 1. Overview
+This track focuses on transitioning from global context management to explicit session-scoped context. It introduces transparent visibility into the exact context (system prompts, aggregated markdown, files, and screenshots) used in a session, allows saving context selections as reusable presets, and adds MMA dashboard integration for filtering session hubs by specific agents.
+
+## 2. Functional Requirements
+
+### 2.1 Context Presets & Assignment
+- **Context Snapshots:** Users can save the current selection of files and screenshots as a named "Context Preset".
+- **Preset Swapping:** Users can easily load a Context Preset into an active session.
+- **MMA Assignment:** Allow assigning specific Context Presets to individual MMA agent personas, preventing all agents from having access to all files by default.
+
+### 2.2 Transparent Context Visibility
+- **No Hidden Context:** The Session Hub must expose the exact context provided to the model.
+- **Initial Payload Visibility:** The aggregated markdown content generated at the start of the discussion must be viewable in the UI.
+- **System Prompt State:** Display the fully resolved system prompt that was active for the session.
+- **Injection Timeline:** The UI must display *when* specific files or screenshots were injected or included during the progression of the discussion.
+
+### 2.3 Agent-Focused Session Filtering
+- **Dashboard Integration:** Move the "Focus Agent" feature from the Operations Hub to the MMA Dashboard.
+- **Agent Context Filtering:** Add a button on any live agent's panel in the MMA Dashboard that automatically filters the other hubs (Session/Discussion) to show only information related to that specific agent's session.
+
+## 3. Acceptance Criteria
+- [ ] Context selections (files/screenshots) can be saved and loaded as Presets.
+- [ ] MMA Agent Personas can be configured to use specific Context Presets.
+- [ ] The Session Hub displays the generated aggregate markdown and resolved system prompt.
+- [ ] The discussion timeline clearly shows when files/screenshots were injected.
+- [ ] The MMA Dashboard allows focusing the UI on a specific agent's session data.