Using `require.Equal` inside an `httptest.Server` handler goroutine at line 40 of `agent_cert_resolution_test.go` is a Go testing anti-pattern: `require.Equal` calls `t.FailNow()` → `runtime.Goexit()`, which only terminates the handler goroutine, not the test goroutine. This leaves the HTTP response unwritten, causing the client to receive a connection reset, and the test then fails on `require.NoError` with a misleading error instead of the actual `projectId` mismatch message. Replace `require.

TestSlugResolutionCompletesBeforeIssuance does not actually test the race condition fix — it calls resolveCertificateNameReferences() and api.CallIssueCertificate() sequentially and explicitly in the test body, so the ordering assertion is trivially true by construction. The test would pass identically against the pre-fix buggy code, providing false confidence that the goroutine-ordering race is covered.