[warp-agent-staging]

Build container and standalone workers with Go 1.27.3 so their bundled crypto/x509 rejects compromised eMudhra intermediate keys (GO-2026-6809). CI and release builds already derive Go from go.mod. Rebuild and redeploy workers to pick up the fix.

Pin CI to Go 1.27-compatible golangci-lint v2.15.0 through its /v2 module path. Handle connection-shutdown errors, assert blocked tracing flushes fail, and remove a redundant Docker log error check.

Tracked in REMOTE-3614.

Validation

• Go 1.27.3: full go test -p 4 ./..., go vet -p 4 ./..., and go build -p 4 ./... passed. go fmt ./... made no changes.
• Offline comparison used all 14 chains from the incident reporter, including cross-signs and no-CT variants, with the original roots explicitly trusted. Go 1.26.6 accepted all 14; Go 1.27.3 rejected all 14 (no valid chains built). This is upstream-verifier proof, not a deployed-worker test.
• Installed github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.15.0 with Go 1.27.3, matching CI. Its full run passed with zero issues.
• Full tests passed after the analyzer corrections; the affected worker package passed again after shutdown error handling. Existing Docker log/shutdown tests are retained, and the bounded tracing test now checks its flush error. Final gofmt -s -w . completed; Docker image builds were not run.

Plans:

• Repair server Go 1.27.3 CI fallout

[warp-agent-staging]

This PR was generated with Warp.

Comment @warp-staging-factory on this PR to send it follow-up work.