fix agent schema description

[j4ys0n]

No description provided.

[j4ys0n]

Automated review 🤖

Summary of Changes
Bumps package version from 0.3.0 to 0.3.1 and tightens validation for the temperature field in UpdateAgentSchema by adding .min(0).max(2) constraints, clarifying the valid range as 0-2 in the description.

Key Changes & Positives

• Enforces stricter input validation for temperature in src/schemas.ts line 135, preventing out-of-range values (e.g., negative or >2) that could cause runtime errors or unexpected model behavior. 🟢
• Improves schema documentation clarity by explicitly stating the valid range (0-2) instead of referencing arbitrary values like -1.

Potential Issues & Recommendations

1. Issue / Risk: Existing clients sending temperature: -1 (previously allowed as "omit to use default") may now fail validation.
   Impact: Breaking change for callers relying on -1 as a sentinel value to trigger default temperature.
   Recommendation: Update client code to omit temperature entirely instead of passing -1, or adjust schema to accept -1 as a special case (e.g., .min(-1).max(2) with explicit handling).
   Status: 🟡 Needs review

Language/Framework Checks

• Zod schema updated correctly with .min(0).max(2) chain in src/schemas.ts line 135.
• Description updated concisely to reflect new constraint without ambiguity.

Approval Recommendation
Approve with caveats

• Verify whether -1 was intentionally supported elsewhere (e.g., backend defaults); if so, either restore support or document migration path.
• Ensure clients are aware of the stricter validation before deploying.