A backend team migrated a Go HTTP service from net/http to the chi router framework. No functionality was intentionally changed — just the routing layer. They want a thorough regression scout across all risk areas before releasing. Write your complete findings to report.md.

=============== FILE: inputs/go-service.md ===============

HTTP Service Migration Overview

Change

• Routing layer migrated from stdlib net/http ServeMux to chi v5 router
• Files changed: main.go, router/router.go (CHANGED), middleware/logging.go (CHANGED)
• No handler logic was modified

Routes

• GET /health — health check (no auth)
• GET /api/v1/items — list items (requires auth)
• POST /api/v1/items — create item (requires auth + write permission)
• GET /api/v1/items/{id} — get item by ID (requires auth)
• DELETE /api/v1/items/{id} — delete item (requires auth + admin)
• GET /api/v1/users/me — current user profile (requires auth)

Middleware Stack (before change)

• CORS middleware (custom)
• Logging middleware
• Auth middleware (JWT validation)
• Rate limiting middleware

Known Chi Migration Notes

• Chi uses {id} style path params; old ServeMux used custom regex patterns
• Middleware execution order in chi differs from manual chaining
• Chi's 404/405 responses differ in format from net/http defaults
• CORS headers now applied by chi's CORS middleware (replaced custom) =============== END FILE ===============