Story 2.6: Test Backend Admin and Files Route Handlers

Sprint Key: 2-6-test-backend-admin-and-files-route-handlers Epic: 2 PRD: testing-framework

---

Story 2.6: Test Backend Admin and Files Route Handlers

Status: ready-for-dev

Story

As a developer, I want tests for admin route handlers with role-based access control, So that admin-only endpoints are validated against the API contract and unauthorized access is rejected.

Acceptance Criteria

1. AC1: Admin route auth guard — All /api/admin/* endpoints return 401 without valid token and 403 for non-admin users
2. AC2: System health endpoints — GET /api/admin/system-health, GET /api/admin/database/stats, GET /api/admin/user-stats return 200 with expected data shapes
3. AC3: Log management endpoints — GET /api/admin/logs, POST /api/admin/logs/rollover, GET /api/admin/logs/summary, GET /api/admin/logs/search, GET /api/admin/logs/debug-yesterday
4. AC4: Security endpoints — GET /api/admin/security-metrics, POST /api/admin/security-scan, GET /api/admin/security/last-scan
5. AC5: Diagnostic and database operations — POST /api/admin/diagnostics, POST /api/admin/database-operations/backup, POST /api/admin/database-operations/optimize
6. AC6: User search — GET /api/admin/users/search with pagination
7. AC7: Error handling — Both next(error) and direct res.status(500) patterns
8. AC8: Files routes out of scope — No file routes in gov-chat-backend; handled by document-repository (Epic 5)

Scope Note

Files routes do NOT exist in gov-chat-backend. This story covers admin routes only (15 endpoints). File route testing belongs to Epic 5.