# Specification: Test Suite Curation and Organization

## Overview
The current test suite for **Manual Slop** and the **Conductor** framework has grown incrementally and lacks a formal organization. This track aims to curate, categorize, and organize existing tests, specifically blacklisting Conductor-specific (MMA) tests from manual_slop's test runs. We will use a central manifest for test management and perform an exhaustive review of all tests to eliminate redundancy.

## Functional Requirements
-   **Test Categorization:** Tests will be categorized into:
    -   Manual Slop Core/GUI
    -   Conductor/MMA
    -   MCP/Integrations
    -   Simulation/Workflows
-   **Central Manifest:** Implement a `tests.toml` (or similar) manifest file to define test categories and blacklist specific tests from the default `manual_slop` test run.
-   **Blacklisting:** Ensure that Conductor-only tests (e.g., MMA related) do not execute when running tests for the `manual_slop` application itself.
-   **Exhaustive Curation:** Review all existing tests in `tests/` to:
    -   Fix failing tests.
    -   Identify and merge redundant tests.
    -   Remove obsolete tests.
    -   Ensure consistent naming conventions.

## Non-Functional Requirements
-   **Clarity:** The `tests.toml` manifest should be easy to understand and maintain.
-   **Reliability:** The curation must result in a stable, passing test suite for each category.

## Acceptance Criteria
-   A central manifest (`tests.toml`) is created and used to manage test execution.
-   Running `manual_slop` tests successfully ignores all blacklisted Conductor/MMA tests.
-   All failing tests are either fixed or removed (if redundant).
-   Each test file is assigned to at least one category in the manifest.
-   Redundant test logic is consolidated.

## Out of Scope
-   Writing new feature tests (unless required to consolidate redundancy).
-   Major refactoring of the test framework itself (beyond the manifest).