feat: Add global relationships management to GlobalSymbolIndex

- Introduced a new schema version (v2) with a global_relationships table.
- Implemented CRUD operations for file relationships, including update and delete functionalities.
- Added query capabilities for relationships by target and symbols.
- Created migration logic from v1 to v2 schema.
- Enhanced tests for global relationships, covering various scenarios including insertion, querying, and deletion.

docs: Add update-single command for generating module documentation

- Created a new command to generate manual-style documentation (CLAUDE.md) for a single module.
- Detailed execution process and implementation phases for the command.
- Included usage examples and error handling guidelines.

feat: Implement team command for CLI interface

- Added a new team command for logging and retrieving messages in a team message bus.
- Supported subcommands for logging, reading, listing, and checking status of messages.
- Included error handling and JSON output options.

test: Add comprehensive tests for global relationships

- Developed extensive tests for the global_relationships table in GlobalSymbolIndex.
- Covered schema creation, migration, CRUD operations, and performance benchmarks.
- Ensured project isolation and validated query functionalities for relationships.

.claude/agents/cli-execution-agent.md

@@ -68,14 +68,15 @@ const task = plan.tasks.find(t => t.id === taskId)
 const context = {
   // Base context
   scope: task.scope,
-  modification_points: task.modification_points,
+  files: task.files,                                 // File-level changes (each has .change)
   implementation: task.implementation,
 
-  // Medium/High complexity: WHY + HOW to verify
+  // Medium/High complexity: WHY + HOW to verify (PLANNING section)
+  reference: task.reference,                         // Reference patterns/files
   rationale: task.rationale?.chosen_approach,        // Why this approach
-  verification: task.verification?.success_metrics,  // How to verify success
+  success_metrics: task.test?.success_metrics,       // How to verify success
 
-  // High complexity: risks + code skeleton
+  // High complexity: risks + code skeleton (PLANNING section)
   risks: task.risks?.map(r => r.mitigation),         // Risk mitigations to follow
   code_skeleton: task.code_skeleton,                 // Interface/function signatures
 
@@ -165,8 +166,8 @@ TASK: {task.implementation.join('\n')}
   Key functions: {task.code_skeleton.key_functions.map(f => f.signature)}
 
 # Include verification in EXPECTED
-EXPECTED: {task.acceptance.join(', ')}
-  Success metrics: {task.verification.success_metrics.join(', ')}
+EXPECTED: {task.convergence.criteria.join(', ')}
+  Success metrics: {task.test.success_metrics.join(', ')}
 
 # Include risk mitigations in CONSTRAINTS (High)
 CONSTRAINTS: {constraints}
@@ -268,8 +269,8 @@ find .workflow/active/ -name 'WFS-*' -type d
 
 ## Phase 5: Log {path} | Summary {summary_path}
 [Medium/High] Verification Checklist:
-  - Unit Tests: {task.verification.unit_tests.join(', ')}
-  - Success Metrics: {task.verification.success_metrics.join(', ')}
+  - Unit Tests: {task.test.unit.join(', ')}
+  - Success Metrics: {task.test.success_metrics.join(', ')}
 
 ## Next Steps: {actions}
 ```