⚡ Bolt: Fix goroutine leak in ScanPorts on premature cancellation

.jules/bolt.md

@@ -45,3 +45,6 @@
 ## 2026-07-28 - [Validating Context Cancellation for Blocking OS Executions]
 **Learning:** Functions that wrap long-running system operations (such as `exec.CommandContext` or `net.DialContext`) generally handle context cancellation automatically, but early aborts for network calls need explicit testing. Merely relying on lower-level Go standard library propagation does not automatically guarantee zero side-effects if the cancellation happens before execution logic completes in consumer boundaries.
 **Action:** Always include fine-grained tests that explicitly pass a pre-cancelled context to network discovery and connection routines (e.g. Ping, LookupAddr) to definitively prove zero leakage of OS processes or goroutines on early aborts.
+## YYYY-MM-DD - Fix Goroutine Leak in ScanPorts on Context Cancellation
+**Learning:** Worker goroutines can leak when sending on an unbuffered channel (`out <- p`) if the consumer prematurely stops reading due to context cancellation.
+**Action:** Wrap channel send operations in a `select` statement with `ctx.Done()` to prevent goroutines from blocking indefinitely when the consumer aborts.

pkg/ports/scanner.go

@@ -54,7 +54,11 @@ func ScanPorts(ctx context.Context, ip string, ports []int, timeoutMs int) <-cha
 				conn, err := dialer.DialContext(ctx, "tcp", address)
 				if err == nil {
 					conn.Close()
-					out <- p
+					select {
+					case <-ctx.Done():
+						return
+					case out <- p:
+					}
 				}
 			}
 		}()