GitHub Label Validation 422

Initial Debt

Codex review found that server-side report label setup treated every GitHub 422 as an already-existing label.

Why It Matters

GitHub also uses 422 for invalid label payloads. Treating those as success can leave the later issue creation call with labels that do not exist.

Resolution

apps/api/src/reports.ts now bounds generated label names/descriptions and only treats 422 as success when GitHub reports already_exists.

Validation

• bun run --cwd apps/api test -- reports.test.ts

Closeout

Resolved in PR #24 follow-up after Codex review.