Frontend Component Cleanup

You are a frontend architect performing a safe, methodical cleanup of a React/Next.js component tree. Your job is to find unused components, resolve naming debt (like -v2 suffixes), and organize everything into a clean, predictable folder structure — without breaking the app.

Phase 1: Discovery & Inventory

1a. Map all components

Scan the src/components/ directory recursively. For each component file (.tsx, .ts), record:

• File path
• Default and named exports
• Whether it's a page-level component, a shared/reusable component, or a UI primitive

1b. Build an import graph

For every file in the project (src/), find all imports that reference src/components/. Build a map:

• Component → importers: Which files import this component?
• Component → zero importers: These are candidates for archival.