refactor: Add tree-style execution flow diagrams to all workflow commands

Added tree-style execution process diagrams using ASCII art (├─, └─, │) to 34 workflow command files across three directories for improved readability and execution flow clarity.

## Changes by Directory

### workflow/ root (17 files)
- lite-plan.md, lite-execute.md, lite-fix.md
- plan.md, execute.md, replan.md
- status.md, review.md, review-fix.md
- review-session-cycle.md, review-module-cycle.md
- session commands (start, complete, resume, list)
- tdd-plan.md, tdd-verify.md, test-cycle-execute.md, test-gen.md, test-fix-gen.md

### workflow/ui-design/ (10 files)
- layout-extract.md, animation-extract.md, style-extract.md
- generate.md, import-from-code.md, codify-style.md
- imitate-auto.md, explore-auto.md
- reference-page-generator.md, design-sync.md

### workflow/tools/ (8 files)
- conflict-resolution.md, task-generate-agent.md, context-gather.md
- tdd-coverage-analysis.md, task-generate-tdd.md
- test-task-generate.md, test-concept-enhanced.md, test-context-gather.md

## Diagram Features
- Input parsing with flag enumeration
- Decision branching with conditional paths
- Phase/step hierarchy with clear nesting
- Mode detection and validation flows

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/commands/workflow/tools/context-gather.md

@@ -24,6 +24,38 @@ Orchestrator command that invokes `context-search-agent` to gather comprehensive
 - **Plan Mode**: Full comprehensive analysis (vs lightweight brainstorm mode)
 - **Standardized Output**: Generate `.workflow/active/{session}/.process/context-package.json`
 
+## Execution Process
+
+```
+Input Parsing:
+   ├─ Parse flags: --session
+   └─ Parse: task_description (required)
+
+Step 1: Context-Package Detection
+   └─ Decision (existing package):
+      ├─ Valid package exists → Return existing (skip execution)
+      └─ No valid package → Continue to Step 2
+
+Step 2: Invoke Context-Search Agent
+   ├─ Phase 1: Initialization & Pre-Analysis
+   │  ├─ Load project.json as primary context
+   │  ├─ Initialize code-index
+   │  └─ Classify complexity
+   ├─ Phase 2: Multi-Source Discovery
+   │  ├─ Track 1: Historical archive analysis
+   │  ├─ Track 2: Reference documentation
+   │  ├─ Track 3: Web examples (Exa MCP)
+   │  └─ Track 4: Codebase analysis (5-layer)
+   └─ Phase 3: Synthesis & Packaging
+      ├─ Apply relevance scoring
+      ├─ Integrate brainstorm artifacts
+      ├─ Perform conflict detection
+      └─ Generate context-package.json
+
+Step 3: Output Verification
+   └─ Verify context-package.json created
+```
+
 ## Execution Flow
 
 ### Step 1: Context-Package Detection