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/GIFTDETAILSSTEP_PRE_MIGRATION_AUDIT.md

@@ -0,0 +1,87 @@
+# GiftDetailsStep.vue Migration Audit
+
+## Component Overview
+- **File**: `src/components/GiftDetailsStep.vue`
+- **Size**: 424 lines (Medium Complexity)
+- **Purpose**: Gift details step component for step 2 of gift flow with entity summaries and validation
+- **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**: ✅ No notification system usage found
+- **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 (no notifications)
+- ⏳ **Phase 4**: Template Streamlining - NEEDED (long CSS classes)
+
+### Component Features to Migrate
+- **Entity Summary Display**: Giver and recipient summary buttons with edit capability
+- **Gift Description Input**: Text input with placeholder support
+- **Amount Input**: AmountInput component integration with increment/decrement
+- **Unit Code Selection**: Dropdown for currency/unit selection (HUR, USD, BTC, etc.)
+- **Photo & More Options**: Navigation link to additional options
+- **Conflict Detection**: Warning display for same person as giver/recipient
+- **Form Validation**: Submit button with conflict-based styling
+- **Event Handling**: Multiple emit events for form interactions
+- **Reactive Data**: Local state management with prop watching
+
+### Technical Analysis
+- **Database Operations**: None (pure UI component)
+- **Notification System**: None (no notifications used)
+- **Template Classes**: 2 long CSS classes that can be extracted
+- **Methods**: 8 methods with good documentation
+- **Computed Properties**: 6 computed properties (well-structured)
+- **Props**: 12 props with proper TypeScript typing
+- **Watchers**: 3 watchers for prop synchronization
+
+### Migration Complexity Assessment
+- **Database Migration**: Low (no database operations)
+- **SQL Abstraction**: Low (no raw SQL)
+- **Notification Migration**: Low (no notifications)
+- **Template Streamlining**: Medium (2 long classes to extract)
+- **Overall Complexity**: Medium
+
+### Estimated Migration Time
+- **Conservative Estimate**: 5-7 minutes
+- **Optimistic Estimate**: 3-4 minutes
+- **Based on**: Medium template streamlining, good existing structure
+
+### Risk Assessment
+- **Risk Level**: Low
+- **Potential Issues**: None identified
+- **Dependencies**: EntitySummaryButton, AmountInput, logger utility
+- **Testing Requirements**: Form validation, entity editing, conflict detection, navigation
+
+### Migration Strategy
+1. **Phase 4 Focus**: Extract long CSS classes to computed properties
+2. **Documentation**: Enhance existing documentation
+3. **Template Cleanup**: Improve template readability
+4. **Validation**: Ensure form functionality remains intact
+
+### Success Criteria
+- ✅ All long CSS classes extracted to computed properties
+- ✅ Template complexity reduced
+- ✅ Form validation preserved
+- ✅ Entity editing preserved
+- ✅ Conflict detection preserved
+- ✅ Navigation functionality maintained
+- ✅ Lint validation passes
+
+### Next Steps
+- ⏳ Begin Phase 4 (Template Streamlining)
+- ⏳ Extract CSS classes to computed properties
+- ⏳ 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