LVT-51: Specific state in team lookup for when there's no data or a team doesn't exist

[jackattack-4]

responds with { "TEAM_DOES_NOT_EXIST" } or { "NO_DATA_FOR_TEAM" }

[Copilot]

Pull request overview

This PR adds explicit error handling for team lookup endpoints to distinguish between non-existent teams and teams with no data. When a team doesn't exist in the database, the handlers return "TEAM_DOES_NOT_EXIST", and when a team exists but has no associated data, they return "NO_DATA_FOR_TEAM" (note: the actual response is the error string, not an object containing it, due to how the analysisHandler processes error responses).

Key Changes:

• Added team existence validation using Prisma's findUnique query before processing data
• Added no-data detection logic that checks if any relevant data exists for the team
• Applied changes consistently across three team lookup handlers

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/handler/analysis/teamLookUp/getNotes.ts	Added team existence check and empty notes validation; includes an unused import that should be removed
src/handler/analysis/teamLookUp/categoryMetrics.ts	Added team existence check and validates whether any metric has data; contains potential issue with treating 0 values as "no data"
src/handler/analysis/teamLookUp/breakdownMetrics.ts	Added team existence check and validates whether any breakdown metric has valid data

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.