internal/settings/settings.go (1)

567-575: Preserve field context when UnmarshalText fails.

Returning raw unmarshaler errors here makes diagnostics less consistent than the typed parse branches. Consider wrapping with the config key/field path.

Proposed diff

 			if current.CanAddr() {
 				if unmarshaler, ok := current.Addr().Interface().(encoding.TextUnmarshaler); ok {
 					if err := unmarshaler.UnmarshalText([]byte(value)); err != nil {
-						return err
+						return SettingsError{
+							Field:   key,
+							Message: err.Error(),
+						}
 					}
 					return nil
 				}
 			}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@internal/settings/settings.go` around lines 567 - 575, Wrap errors returned
from unmarshaler.UnmarshalText with a contextual message that includes the
config key/field path so diagnostics match other parse branches: inside the
block where current.CanAddr() and
current.Addr().Interface().(encoding.TextUnmarshaler) are used, change the error
return to wrap the unmarshaler error (e.g. return fmt.Errorf("unmarshal text for
%s: %w", <keyOrFieldPath>, err)) and add fmt to imports if necessary; use the
same identifier used elsewhere for the config key/field path (e.g. key, path, or
fieldPath) to keep messages consistent.