fix(config): guard nullable record in appendNumericBoundHint call

tanshanshan · claude · tanshanshan · commit 846ac0629bba · 2026-05-21T14:31:23.000+08:00
ClawSweeper P1: `record` from `toIssueRecord()` can be null, but
`appendNumericBoundHint` expects a non-null `UnknownIssueRecord`.
Guard with a ternary so the original message is returned when record
is null (which only happens for malformed/empty issues that already
produce generic "Invalid input" messages).

Co-Authored-By: Claude Sonnet 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/src/config/validation.ts b/src/config/validation.ts
@@ -609,7 +609,7 @@ function mapZodIssueToConfigIssue(issue: unknown): ConfigValidationIssue {
   // Numeric ceiling/floor hints (too_big / too_small with numeric origin).
   // Append a parenthesized bound alongside Zod's native message,
   // matching the clarity that enum/union rejections get via (allowed: …).
-  const enrichedMessage = appendNumericBoundHint(message, record);
+  const enrichedMessage = record ? appendNumericBoundHint(message, record) : message;
 
   const allowedValuesSummary = summarizeAllowedValues(collectAllowedValuesFromUnknownIssue(issue));
 
