TypeScript LSP Navigation and Safe Refactoring

TYPESCRIPT LSP REFERENCE MAP

QUERY: Find all references to User type

DIRECT IMPORTS (13 files):
1. services/AuthService.ts
   Line 4: import { User } from '../models/User'
   Usage: parseJwt(): User → returns typed object
   Calls: 2 functions (loginUser, refreshSession)

2. components/UserProfile.tsx
   Line 2: import type { User } from '../models/User'
   Usage: React.FC<{ user: User }> → props type
   Calls: 8 prop references

3. api/users/route.ts
   Line 1: import { User } from '../models/User'
   Usage: POST handler returns Promise<User>
   Cross-reference: calls AuthService.loginUser (cycle detection: false)

INDIRECT REFERENCES (5 files):
4. types/ApiResponse.ts (imports UserDTO, which extends User)
   Line 12: type ApiResponse = { data: UserDTO }
   Inheritance chain detected: User ← UserDTO ← ApiResponse

5. hooks/useAuth.ts (returns User via custom hook)
   Line 8: const user: User = JSON.parse(localStorage.getItem('auth'))
   Consumer: 23 files import useAuth (therefore use User indirectly)

CIRCULAR DEPENDENCY ALERT:
   User.ts imports UserRole (enum)
   UserRole.ts imports User type in comment (safe, just docs)
   Status: No cycle

BREAKING CHANGE RISK:
If you delete 'User.name' field:
   - 7 files directly break (prop expects name)
   - 11 files indirectly break (components render user.name)
   - Estimated refactor time: 4 hours

REFACTOR SAFE PATH:
1. Add User.displayName (optional, default to name)
2. Update all consumers to use displayName first, fallback to name
3. Deprecate name field (1 release)
4. Remove name field (next major)

No file reads required; LSP traced all 18 references instantly.