docs: presentation layer reorganization - complete 5-step engineering process

Complete systematic engineering process for refactoring src/presentation/:

**Step 1 - Research** (docs/research/):
- presentation-layer-organization-in-cli-apps.md
- Survey of CLI patterns: Cargo, Rustup, ripgrep, clap examples
- Four-layer architecture analysis (Input → Dispatch → Controllers → Views)

**Step 2 - Analysis** (docs/analysis/presentation-layer/):
- current-structure.md - Identified 8 structural issues
- Mixed responsibilities, unclear terminology, orphaned modules

**Step 3 - Design** (docs/analysis/presentation-layer/):
- design-proposal.md - Four-layer architecture specification
- Clear separation: parsing → routing → handling → formatting

**Step 4 - Refactor Plan** (docs/refactors/plans/):
- presentation-layer-reorganization.md (central hub)
- 6 progressive, independently mergeable proposals
- Process tracking and decision documentation
- Updated docs/refactors/active-refactorings.md

**Step 5 - GitHub Issues** (docs/issues/):
- 154-epic-presentation-layer-reorganization.md (EPIC)
- 155-proposal-1-create-input-layer.md (2-3h, 5 phases)
- 156-proposal-2-create-dispatch-layer.md (2-3h, 6 phases)

Issues created on GitHub:
- #154: #154
- #155: #155
- #156: #156

This systematic approach was used due to the refactoring's large scope
(50+ files), architectural significance, and multiple implementation phases.

Author: josecelano

docs/analysis/presentation-layer/README.md

@@ -0,0 +1,61 @@
+# Presentation Layer Analysis
+
+This directory contains analysis documents for reorganizing the `src/presentation/` layer.
+
+## Documents
+
+### 1. Current Structure Analysis
+
+**File**: [`current-structure.md`](./current-structure.md)
+
+**Purpose**: Objective analysis of the current presentation layer organization.
+
+**Contents**:
+
+- **Part A**: Current Structure Description
+  - Directory layout and organization
+  - Data flow diagrams
+  - Sequence diagrams
+  - Dependency graphs
+- **Part B**: Problems Analysis
+  - Critical issues (3)
+  - Moderate issues (3)
+  - Minor issues (2)
+
+**Date**: November 6, 2025
+
+---
+
+### 2. Design Proposal
+
+**File**: [`design-proposal.md`](./design-proposal.md)
+
+**Purpose**: Proposes a new four-layer architecture for the presentation layer.
+
+**Contents**:
+
+- Design overview and visual architecture
+- Complete directory structure
+- Layer specifications (Input, Dispatch, Controllers, Views)
+- Data flow diagrams
+- Benefits and trade-offs
+- Comparison to alternatives
+- Container integration (lazy-loading pattern)
+
+**Key Features**:
+
+- Four explicit layers: Input → Dispatch → Controllers → Views
+- Reuses existing `Container` from `bootstrap/` with lazy-loading
+- Standard web framework terminology (MVC/MVT alignment)
+- Integrates orphaned `progress.rs` into `views/progress/`
+
+**Date**: November 6, 2025
+
+---
+
+## Related Documentation
+
+- [Research: CLI Organization Patterns](../../research/presentation-layer-organization-in-cli-apps.md)
+- [Refactor Plan](../../refactors/plans/presentation-layer-reorganization.md) - Complete engineering process tracking
+- [DDD Layer Placement Guide](../../contributing/ddd-layer-placement.md)
+- [Module Organization Conventions](../../contributing/module-organization.md)