fix: Disable unparam linter due to Go generics panic (#199)

The unparam linter panics when analyzing code that uses Go generics with
type constraints (e.g., ~string). This is a known upstream issue in the
underlying Go types package.

Workaround: Disable unparam globally and rely on revive's unused-parameter
rule for similar coverage.

See: golangci/golangci-lint#5254

Co-authored-by: Ben Coombs <[email protected]>

Author: bjcoombs

.golangci.yml

@@ -25,7 +25,9 @@ linters:
     - goconst        # Repeated strings that could be constants
     - gocognit       # Cognitive complexity
     - unconvert      # Remove unnecessary type conversions
-    - unparam        # Unused function parameters
+    # - unparam      # Disabled: panics on Go generics with type constraints (e.g., ~string)
+    #                # See: https://github.com/golangci/golangci-lint/issues/5254
+    #                # revive's unused-parameter rule provides similar coverage
     - nakedret       # Naked returns in long functions
     - prealloc       # Slice preallocation
     - nilerr         # Check for nil error returns
@@ -188,8 +190,7 @@ linters:
     nakedret:
       max-func-lines: 30
 
-    unparam:
-      check-exported: false
+    # unparam settings removed - linter disabled due to Go generics panic
 
     revive:
       confidence: 0.8