docs: reorganize documentation structure with 7-item folder limits

- Create logical sub-folder classification for all documentation
- Organize 91 migration files into component-specific folders
- Separate user guides, build system, migration, and development docs
- Maintain maximum 7 items per folder for easy navigation
- Add comprehensive README and reorganization summary
- Ensure all changes tracked in git with proper versioning

Structure:
- user-guides/ (3 items): user-facing documentation
- build-system/ (3 items): core, platforms, automation
- migration/ (6 items): assessments, testing, templates
- development/ (4 items): tools and standards
- architecture/, testing/, examples/ (ready for future docs)

Total: 24 folders created, all within 7-item limits

docs/migration/migration-testing/audits/ENTITYSELECTIONSTEP_PRE_MIGRATION_AUDIT.md

@@ -0,0 +1,85 @@
+# EntitySelectionStep.vue Migration Audit
+
+## Component Overview
+- **File**: `src/components/EntitySelectionStep.vue`
+- **Size**: 280 lines (Medium Complexity)
+- **Purpose**: Entity selection step component for giver/recipient selection with dynamic labeling
+- **Migration Target**: Enhanced Triple Migration Pattern
+
+## Migration Status: ⏳ READY FOR MIGRATION
+
+### Pre-Migration Analysis
+- **Database Operations**: ✅ No databaseUtil imports found (pure UI component)
+- **SQL Queries**: ✅ No raw SQL queries found
+- **Notification Usage**: ✅ Uses prop-based notification system (modern pattern)
+- **Template Complexity**: ⏳ Needs Phase 4 (Template Streamlining)
+
+### Migration Requirements
+- ✅ **Phase 1**: Database Migration - NOT NEEDED (no database operations)
+- ✅ **Phase 2**: SQL Abstraction - NOT NEEDED (no raw SQL)
+- ✅ **Phase 3**: Notification Migration - NOT NEEDED (already modern)
+- ⏳ **Phase 4**: Template Streamlining - NEEDED (long CSS classes)
+
+### Component Features to Migrate
+- **Dynamic Step Labeling**: Context-based step labels for giver/recipient
+- **EntityGrid Integration**: Unified entity display with grid layout
+- **Conflict Detection**: Integration with conflict checking system
+- **Special Entity Handling**: "You" entity with conditional display
+- **Show All Navigation**: Context preservation in navigation
+- **Cancel Functionality**: Cancel button with event emission
+- **Event Delegation**: Entity selection event handling
+- **Query Parameter Management**: Complex query parameter building
+
+### Technical Analysis
+- **Database Operations**: None (pure UI component)
+- **Notification System**: Uses prop-based `notify` function (modern pattern)
+- **Template Classes**: 1 long CSS class that can be extracted
+- **Methods**: 3 methods with good documentation
+- **Computed Properties**: 8 computed properties (well-structured)
+- **Props**: 15 props with proper TypeScript typing
+
+### Migration Complexity Assessment
+- **Database Migration**: Low (no database operations)
+- **SQL Abstraction**: Low (no raw SQL)
+- **Notification Migration**: Low (already modern)
+- **Template Streamlining**: Low (1 long class to extract)
+- **Overall Complexity**: Low
+
+### Estimated Migration Time
+- **Conservative Estimate**: 4-6 minutes
+- **Optimistic Estimate**: 2-3 minutes
+- **Based on**: Simple template streamlining, good existing structure
+
+### Risk Assessment
+- **Risk Level**: Low
+- **Potential Issues**: None identified
+- **Dependencies**: EntityGrid, Contact interface, PlanData interface
+- **Testing Requirements**: Step labeling, entity selection, navigation, cancel functionality
+
+### Migration Strategy
+1. **Phase 4 Focus**: Extract long CSS class to computed property
+2. **Documentation**: Enhance existing documentation
+3. **Template Cleanup**: Improve template readability
+4. **Validation**: Ensure step functionality remains intact
+
+### Success Criteria
+- ✅ All long CSS classes extracted to computed properties
+- ✅ Template complexity reduced
+- ✅ Step labeling functionality preserved
+- ✅ Entity selection preserved
+- ✅ Navigation functionality maintained
+- ✅ Cancel functionality maintained
+- ✅ Lint validation passes
+
+### Next Steps
+- ⏳ Begin Phase 4 (Template Streamlining)
+- ⏳ Extract CSS class to computed property
+- ⏳ Update documentation
+- ⏳ Validate functionality
+- ⏳ Create migration completion document
+
+## Migration Notes
+- Component is well-structured with good separation of concerns
+- Template streamlining will improve maintainability
+- No functional changes required
+- Component is ready for migration