fix(cmd): keep runToolMultiService under the gocyclo budget

Making runToolFromCSV return an error (so the CSV purchase path is
unit-testable) added an `if err != nil { log.Fatalf }` branch to
runToolMultiService, pushing its cyclomatic complexity from 10 to 11 and
tripping the gocyclo pre-commit hook (over 10).

Extract the error-to-fatal glue into runCSVPathOrFatal so the entrypoint
drops back to complexity 10 while runToolFromCSV keeps its testable
error return.

Author: cristim

cmd/multi_service.go

@@ -76,9 +76,7 @@ var shutdownRequested atomic.Bool
 // (2) score, display, confirm, and purchase.
 func runToolMultiService(ctx context.Context, cfg Config) {
 	if cfg.CSVInput != "" {
-		if err := runToolFromCSV(ctx, cfg); err != nil {
-			log.Fatalf("%v", err)
-		}
+		runCSVPathOrFatal(ctx, cfg)
 		return
 	}
 
@@ -258,9 +256,19 @@ func buildServiceStats(recs []common.Recommendation, results []common.PurchaseRe
 	return stats
 }
 
+// runCSVPathOrFatal runs the CSV purchase path and exits fatally on error.
+// It isolates the error-to-fatal glue from runToolMultiService so that path
+// stays under the cyclomatic-complexity budget while runToolFromCSV remains
+// unit-testable via its returned error.
+func runCSVPathOrFatal(ctx context.Context, cfg Config) {
+	if err := runToolFromCSV(ctx, cfg); err != nil {
+		log.Fatalf("%v", err)
+	}
+}
+
 // runToolFromCSV processes recommendations from a CSV input file.
 // It returns an error instead of exiting so the orchestration glue is
-// unit-testable; the caller (runToolMultiService) turns errors fatal.
+// unit-testable; the caller (runCSVPathOrFatal) turns errors fatal.
 func runToolFromCSV(ctx context.Context, cfg Config) error {
 	// Determine if this is a dry run
 	isDryRun := !cfg.ActualPurchase