Go tests run with -race and -cover under Go's own timeout (closes #88)

backend/script/test runs go test -timeout 30s -race -cover and, if
that fails, runs it again with -v and fails. The root script/test drops
its one 30-second timeout around both halves: from a cold Go build
cache, compiling the tests with -race used it all up on four cores.
Each half keeps its own limit. The builder stage of the Dockerfile
gains gcc and musl-dev for the race detector; make build still sets
CGO_ENABLED=0. New tests: the health check's answer, a valid report's
answer, a report file's exact lines, and the flush at the 10 MiB
threshold. The handlers TestImport stub is gone.

Model: opus-5-5

Dockerfile

@@ -20,7 +20,10 @@ RUN make lint
 # golang:1.25-alpine (2026-02-27)
 FROM golang:1.25-alpine@sha256:f6751d823c26342f9506c03797d2527668d095b0a15f1862cddb4d927a7a4ced AS builder
 
-RUN apk add --no-cache git make
+# gcc and musl-dev are for make test: its race detector needs cgo, which
+# Go turns on by itself once a C compiler is present. make build still
+# sets CGO_ENABLED=0, so the binary stays static.
+RUN apk add --no-cache gcc git make musl-dev
 
 WORKDIR /src