docs(conductor): Initialize Phase 6 GenCpp UX Validation tracks

conductor/tracks/granular_ast_control_20260510/index.md

@@ -0,0 +1,4 @@
+# Track: Granular AST Control
+
+- [Specification](./spec.md)
+- [Plan](./plan.md)

conductor/tracks/granular_ast_control_20260510/metadata.json

@@ -0,0 +1,5 @@
+{
+  "id": "granular_ast_control_20260510",
+  "title": "Granular AST Control (Signatures vs. Definitions)",
+  "status": "planned"
+}

conductor/tracks/granular_ast_control_20260510/plan.md

@@ -0,0 +1,9 @@
+# Implementation Plan: Granular AST Control
+
+## Phase 1: Models & UI State
+- [ ] Update `FileItem` model in `src/models.py` to support the new AST states.
+- [ ] Update `src/gui_2.py` Context Panel to render toggle buttons/dropdowns for the new states.
+
+## Phase 2: Aggregation Logic
+- [ ] Modify `src/aggregate.py` to intercept files with these states and call the appropriate `tree-sitter` MCP tools.
+- [ ] Ensure caching works for the new AST extraction states.

conductor/tracks/granular_ast_control_20260510/spec.md

@@ -0,0 +1,9 @@
+# Specification: Granular AST Control (Signatures vs. Definitions)
+
+## Overview
+Introduce 'AST Signatures' and 'AST Definitions' states in the Context Panel for C/C++ files to allow granular control over context exposure without blowing up token limits.
+
+## Acceptance Criteria
+- [ ] Context panel file items support two new states: `AST Signatures` and `AST Definitions`.
+- [ ] `aggregate.py` respects these states by invoking the `ts_c_get_skeleton` / `ts_cpp_get_skeleton` tools accordingly.
+- [ ] Visual indicators in the UI clearly show the current aggregation state of each file.