manual_slop/conductor/archive/history_segregation_20260224/spec.md

Specification: Discussion History Segregation and Blacklisting

Overview

Currently, manual_slop.toml stores both project configuration and the entire discussion history. This leads to redundancy and potential context bloat if the AI agent reads the raw TOML file via its tools. This track will move the discussion history to a dedicated sibling TOML file (history.toml) and strictly blacklist it from the AI agent's file tools to ensure it only interacts with the curated context provided in the prompt.

Functional Requirements

1. File Segregation:
   • Create a dedicated history file (e.g., manual_slop_history.toml) in the same directory as the main project configuration.
   • The main manual_slop.toml will henceforth only store project settings, tracked files, and system prompts.
2. Automatic Migration:
   • On application startup or project load, detect if the discussion key exists in manual_slop.toml.
   • If found, automatically migrate all discussion entries to the new history sibling file and remove the key from the original file.
3. Strict Blacklisting:
   • Hardcode the exclusion of the history TOML file in mcp_client.py and aggregate.py.
   • The AI agent must be prevented from reading this file using the read_file or search_files tools.
4. Backend Integration:
   • Update ProjectManager in project_manager.py to manage two distinct TOML files per project.
   • Ensure the GUI correctly loads history from the new file while maintaining existing functionality.

Non-Functional Requirements

• Data Integrity: Ensure no history is lost during the migration process.
• Performance: Minimize I/O overhead when saving history entries after each AI turn.

Acceptance Criteria

• manual_slop.toml no longer contains the discussion array.
• A sibling history.toml (or similar) contains all historical and new discussion entries.
• The AI agent cannot access the history TOML file via its file tools (verification via tool call test).
• Discussion history remains visible in the GUI and is correctly included in the AI prompt context.

Out of Scope

• Customizable blacklist via the UI.
• Support for cloud-based history storage.