pkg/runner/options.go (1)

76-76: Consider minor comment refinement.

The comment "Payload to use with CONNECT scan types" could be slightly clearer. Consider "Payload to send in CONNECT scans" to match the CLI help text.

-	ConnectPayload    string              // Payload to use with CONNECT scan types
+	ConnectPayload    string              // Payload to send in CONNECT scans

pkg/runner/validate.go (1)

144-146: Consider validation ordering for better UX.

The validation correctly enforces that connect payloads require connect scans. However, the current placement means users might see this error even when the code would automatically fall back to connect scan (e.g., due to routing failure at line 148-151).

Consider moving this validation after all automatic scan-type adjustments, or automatically switching to connect scan when a payload is specified (similar to the proxy handling at lines 139-142).

Current flow:

1. Line 139-142: Auto-adjust SynScan → ConnectScan if proxy is used
2. Line 144-146: Error if ConnectPayload with non-ConnectScan
3. Line 148-151: Auto-adjust SynScan → ConnectScan if routing fails

Potential improvement:

// Move after routing check (line 151)
if options.ConnectPayload != "" && options.ScanType != ConnectScan {
	gologger.Warning().Msgf("Connect payload requires connect scan: falling back to connect scan")
	options.ScanType = ConnectScan
}

Or move after all adjustments:

// After line 151
if options.ConnectPayload != "" && options.ScanType != ConnectScan {
	return errors.New("connect payload can only be used with connect scan")
}

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro