Access logs always report status 0, never the real response code

Log-based monitoring and alerting (e.g. "page if the 5xx rate exceeds X%") is completely blind: every request, whether it succeeded, was rejected, or crashed, is logged with the same meaningless status. A real outage -- every request suddenly 500ing -- would produce logs that look identical to a healthy service. On-call has no way to tell from the logs alone that anything is wrong.

Every access log line's status field is 0, regardless of what status code was actually sent to the client.

1. go test ./tickets/tests/... -run TestTicket06 -v

AccessLog wraps the http.ResponseWriter in a chi WrapResponseWriter specifically so it can read back .Status() after the handler runs -- but it then calls next.ServeHTTP with the original, unwrapped writer, not the wrapper. The real handler writes its response straight to the original writer; the wrapper never observes any of it, so stays at its unset zero value forever.

Look at the two variables AccessLog creates (w, the parameter, and ww, the wrapper) and check which one gets passed to next.ServeHTTP.