fix: apply min/max modifiers to ZodNumber in secureZodParser

[Osamaali313]

Description

SecureZodSchemaParser.applyModifiers (packages/components/src/secureZodParser.ts) applies .min() / .max() for ZodString and ZodArray, but has no ZodNumber branch — so numeric bounds are silently dropped:

case 'max':
    if (modifier.args[0] !== undefined) {
        if (zodType._def?.typeName === 'ZodString') { ... }
        else if (zodType._def?.typeName === 'ZodArray') { ... }
        // no ZodNumber branch
    }

A user schema like z.number().min(0).max(100) therefore accepts out-of-range values (e.g. 999, -50). This parser is used by the Structured Output Parser (Advanced) and Custom Tool nodes, so LLM structured output / tool arguments that the author explicitly bounded are passed through unvalidated. The sibling int case already branches on ZodNumber, confirming numeric modifiers are meant to apply.

Repro (schema z.object({ score: z.number().min(0).max(100) })): before, score: 999 and score: -50 are accepted; after, they're rejected (too_big / too_small), while a z.string().max(5) control already worked.

Fix

Add the missing ZodNumber branch to both min and max:

} else if (zodType._def?.typeName === 'ZodNumber') {
    zodType = (zodType as z.ZodNumber).max(modifier.args[0])   // and .min(...) in the min case
}

String/array bounds are unchanged. (There was no existing test file for secureZodParser.ts; happy to add one if you'd like.)

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.