Issue #24

Proposals pile up: Windows job objects, MaxHeaderCount, httptest tweak

Three proposals land on the tracker at once. One asks os/exec on Windows to attach a JOB_OBJECT at process creation so the whole tree can be killed reliably, a fix driven by a real Woodpecker CI bug. Another would add Server.MaxHeaderCount to net/http, and a third argues httptest.ResponseRecorder should skip the bodyAllowedForStatus check when the write is empty. Over on r/golang the moderators reopen the perennial "good Go project to study or contribute to" thread, which is the kind of FAQ worth bookmarking before the next time someone asks in your team chat. On the writing side, a Medium piece walks through a channel pattern that looks correct, passes its tests, and quietly leaks goroutines anyway. Pairs well with another post on retained memory and reachability for anyone debugging long-lived workers.