Goal#

Add tests for the remaining uncovered API routes across operational domains:

Crew & Activities#

• app/api/crew/route.ts — crew member listing
• app/api/crew-memory/route.ts — crew memory operations
• app/api/agent-activities/route.ts — agent activity tracking

Logs & Monitoring#

• app/api/logs/route.ts — system log querying
• app/api/logs/snapshot/route.ts — log snapshots
• app/api/health/route.ts — health check endpoint
• app/api/failures/route.ts — failure tracking API
• app/api/metrics/route.ts — metrics endpoint

Model Usage & Quotas#

• app/api/model-usage/route.ts — usage tracking
• app/api/model-usage/daily/route.ts — daily breakdown
• app/api/model-usage/summary/route.ts — usage summary
• app/api/model-usage/budget/route.ts — budget management
• app/api/model-usage/check/route.ts — check if model can be used
• app/api/model-usage/fallbacks/route.ts — fallback tracking
• app/api/models/consumption/route.ts — consumption tracking
• app/api/models/quota/route.ts — quota management
• app/api/models/recommendations/route.ts — model recommendations
• app/api/models/routing-history/route.ts — routing history
• app/api/rate-limits/route.ts — rate limit endpoint

Runs#

• app/api/runs/active/route.ts — active runs listing
• app/api/runs/active/live/route.ts — live run stream
• app/api/runs/completed/route.ts — completed runs
• app/api/runs/[runId]/route.ts — individual run
• app/api/runs/[runId]/log/route.ts — run log
• app/api/runs/[runId]/ping/route.ts — run keepalive

Screenshots & UI tools#

• app/api/screenshots/route.ts — screenshot management
• app/api/screenshots/analyze/route.ts — analyze screenshot
• app/api/screenshots/analyze-all/route.ts — bulk analyze
• app/api/screenshots/[...path]/route.ts — screenshot serving

Other#

• app/api/situation/route.ts — crew situation endpoint
• app/api/session-status/route.ts — session status
• app/api/session-messages/route.ts — session messages
• app/api/stream/route.ts — stream endpoint
• app/api/team/route.ts — team endpoint
• app/api/tests/e2e-run/route.ts — E2E run trigger
• app/api/tests/playwright-report/route.ts — report serving
• app/api/tests/playwright-report/[...path]/route.ts — report path handler
• app/api/tests/trace-viewer/route.ts — trace viewer
• app/api/retro-notes/route.ts — retro notes
• app/api/nav-config/route.ts — navigation config
• app/api/fallback-state/route.ts — fallback state
• app/api/bridge-data/route.ts — bridge data
• app/api/doc-content/route.ts — doc content
• app/api/projects/route.ts — projects
• app/api/reviews/[id]/route.ts — review detail
• app/api/reviews/[id]/findings/route.ts — review findings
• app/api/memory-search/route.ts — memory search
• app/api/model-health/route.ts — model health endpoint
• app/api/ci/route.ts — CI status
• app/api/ci/artifacts/route.ts — CI artifacts
• app/api/coverage-inventory/route.ts — test coverage inventory
• app/api/chat/route.ts — chat messages
• app/api/chat/clear/route.ts — clear chat
• app/api/images/log/route.ts — image gen log
• app/api/tasks/audit/route.ts — task audit
• app/api/tasks/heal/route.ts — task healing
• app/api/screenshot/route.ts — take screenshot

This is a large batch. Focus on the most impactful routes: model-usage, logs, runs. Each route gets a test file named __tests__/<path-name>.test.ts with handler-level testing (mock lib deps, test NextRequest handling).

Acceptance#

• At minimum: logs, model-usage (all sub-routes), runs (all sub-routes), health, failures, situation, crew routes covered
• Priority level: high → model-usage > runs > logs > screenshots > crew > everything else
• @area annotation per route: "API Routes"
• No regression

Tags#

[api-route, coverage, bulk]