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

@@ -0,0 +1,95 @@
+# api.ts Pre-Migration Audit
+
+## Service Overview
+- **File**: `src/services/api.ts`
+- **Purpose**: API error handling utilities with platform-specific logging
+- **Complexity**: Low (61 lines)
+- **Migration Priority**: High (Services category)
+
+## Current State Analysis
+
+### Phase 1: Database Migration Assessment
+- **Status**: ✅ NOT NEEDED
+- **Evidence**: No database operations found, only API error handling
+- **Actions Required**: None
+
+### Phase 2: SQL Abstraction Assessment
+- **Status**: ✅ NOT NEEDED
+- **Evidence**: No raw SQL queries found
+- **Actions Required**: None
+
+### Phase 3: Notification Migration Assessment
+- **Status**: ✅ NOT NEEDED
+- **Evidence**: No notification system usage found
+- **Actions Required**: None
+
+### Phase 4: Template Streamlining Assessment
+- **Status**: ✅ NOT NEEDED
+- **Evidence**: No template code found (service file)
+- **Actions Required**: None
+
+## Technical Analysis
+
+### Database Operations
+```typescript
+// No database operations found
+// Service only handles API error processing
+```
+
+### Notification Operations
+```typescript
+// No notification operations found
+// Service only logs errors, doesn't show user notifications
+```
+
+### Code Complexity
+- **Lines**: 61 lines
+- **Functions**: 1 main function (`handleApiError`)
+- **Imports**: 2 imports (AxiosError, logger utilities)
+- **Platform Detection**: Uses `process.env.VITE_PLATFORM`
+
+### Error Handling
+- **Rate Limit Detection**: Handles 400 status codes
+- **Platform Logging**: Enhanced logging for Capacitor platform
+- **Error Propagation**: Throws errors for non-rate-limit cases
+- **Detailed Logging**: Includes request config, response data, status
+
+## Migration Plan
+
+### No Migration Required
+This service is already well-structured and follows modern patterns:
+- ✅ No database operations to migrate
+- ✅ No notification system to modernize
+- ✅ No template code to streamline
+- ✅ Documentation is comprehensive
+- ✅ Error handling is appropriate
+- ✅ Platform-specific logic is well-implemented
+
+## Estimated Migration Time
+- **No Migration Required**: 0 minutes
+- **Total Time**: 0 minutes
+
+## Risk Assessment
+- **No Risk**: Service is already modern and well-structured
+- **No Breaking Changes**: No changes needed
+- **No Performance Impact**: No changes needed
+
+## Success Criteria
+- [ ] Service is already fully compliant
+- [ ] No migration actions required
+- [ ] Documentation is complete
+- [ ] Error handling is appropriate
+- [ ] Platform-specific logic works correctly
+
+## Migration Notes
+- Service is already well-structured and follows modern patterns
+- No migration actions are required
+- Service serves as a good example of clean, modern TypeScript service design
+- Documentation and error handling are comprehensive
+- Platform-specific logging is well-implemented
+
+---
+
+**Audit Date**: 2024-12-19
+**Auditor**: Migration System
+**Status**: No migration required - service is already modern