Complete ADR-008 Phase 1: API Versioning Strategy

Implement URI-based API versioning with /api/v1 prefix across all routes.
This establishes a foundation for future API evolution and breaking changes.

Changes:
- server.ts: All routes mounted under /api/v1/ (15 route handlers)
- apiClient.ts: Base URL updated to /api/v1
- swagger.ts: OpenAPI server URL changed to /api/v1
- Redirect middleware: Added backwards compatibility for /api/* → /api/v1/*
- Tests: Updated 72 test files with versioned path assertions
- ADR documentation: Marked Phase 1 as complete (Accepted status)

Test fixes:
- apiClient.test.ts: 27 tests updated for /api/v1 paths
- user.routes.ts: 36 log messages updated to reflect versioned paths
- swagger.test.ts: 1 test updated for new server URL
- All integration/E2E tests updated for versioned endpoints

All Phase 1 acceptance criteria met:
✓ Routes use /api/v1/ prefix
✓ Frontend requests /api/v1/
✓ OpenAPI docs reflect /api/v1/
✓ Backwards compatibility via redirect middleware
✓ Tests pass with versioned paths

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

src/services/apiClient.ts

@@ -15,10 +15,11 @@ try {
 
 // This constant should point to your backend API.
 // It's often a good practice to store this in an environment variable.
-// Using a relative path '/api' is the most robust method for production.
+// Using a relative path '/api/v1' is the most robust method for production.
 // It makes API calls to the same host that served the frontend files,
 // which is then handled by the Nginx reverse proxy.
-const API_BASE_URL = import.meta.env.VITE_API_BASE_URL || '/api';
+// ADR-008: API Versioning Strategy - Phase 1 migrates all routes to /api/v1.
+const API_BASE_URL = import.meta.env.VITE_API_BASE_URL || '/api/v1';
 
 export interface ApiOptions {
   tokenOverride?: string;