chore(conductor): Archive old track and initialize 4 new Phase 2 MMA tracks

conductor/tracks/tiered_context_scoping_hitl_approval/plan.md

@@ -0,0 +1,15 @@
+# Implementation Plan: Tiered Context Scoping & HITL Approval
+
+## Phase 1: Context Subsetting
+- [ ] Task: Refactor `aggregate.py` to support targeted context builds (e.g., `build_tier1_context`, `build_tier3_context`).
+- [ ] Task: Integrate AST skeleton extraction into the standard Tier 3 context build.
+- [ ] Task: Update the project state to track which files are assigned to which tier.
+
+## Phase 2: The Spawn Interceptor
+- [ ] Task: Create a signaling mechanism in `multi_agent_conductor.py` to emit a "Worker Spawn Requested" event.
+- [ ] Task: Implement the interception logic that pauses the async dispatcher until a signal is received from the GUI.
+
+## Phase 3: Approval UX Modal
+- [ ] Task: Design the "Approve Worker Spawn" modal in DearPyGui.
+- [ ] Task: Populate the modal with the target role, the exact prompt, and a read-only view of the specific file context.
+- [ ] Task: Wire the "Approve", "Modify", and "Reject" buttons to resume or cancel the intercepted spawn.

conductor/tracks/tiered_context_scoping_hitl_approval/spec.md

@@ -0,0 +1,13 @@
+# Track Specification: Tiered Context Scoping & HITL Approval
+
+## Overview
+Provide the user with absolute visual control over what the AI sees at every level of the hierarchy. Currently, the system builds a single massive context blob. This track introduces context subsetting based on the target tier and implements a Human-in-the-Loop (HITL) approval gate before any Tier 3/4 worker is spawned.
+
+## Goals
+1.  **Context Subsetting:** Modify the aggregation logic so that Tier 1, Tier 2, and Tier 3/4 receive distinct, optimized context packages.
+2.  **Spawn Interceptor:** Implement a `BeforeSpawn` hook mechanism within the application to pause execution right before a sub-agent is launched.
+3.  **Approval UX:** Design and implement a GUI modal that displays the exact prompt and context intended for the worker, allowing the user to Approve, Modify, or Reject the spawn.
+
+## Constraints
+-   Must adhere to the project's security and transparency mandates.
+-   The interceptor must be reliable and not cause the main event loop to hang indefinitely.