Add `__post_init__` validation to ensure Agent name is a string  
  
The Agent class previously only used type hints for the name field
without
runtime validation, allowing non-string values like integers to be
passed.
This caused downstream errors during JSON serialization, tracing, and
other
operations that expect the name to be a string.  
  
Changes:  
- Add `__post_init__` method to Agent class with `isinstance` check  
- Raise TypeError with descriptive message for non-string names  
- Validation occurs at instantiation time to fail fast  
  
Fixes issue where `Agent(name=1)` would succeed but cause errors later  
in the execution pipeline.  

Fixes #996

---
[//]: # (BEGIN SAPLING FOOTER)
* #1388
* __->__ #1382

…oncurrent access in SQLiteSession (#1399)

…mpt (#1426)

…delSettings (#1439)

This pull request resolves #1407 ; the "minimal" reasoning effort param
is already supported.

This pull request adds a simple gpt-oss example app

)

## Summary

Fixed a type safety issue where user input was being used as a string
without conversion to integer, which could cause runtime errors and type
mismatches.

## Problem

The code was using `input()` which returns a string, but then using it
directly in the f-string without converting it to an integer. This could
cause:
- Type mismatches when the string is passed to functions expecting
integers
- Runtime errors when users enter non-numeric input
- Inconsistent behavior with the function signature expectations

## Changes Made

Added proper input validation and type conversion:
- Wrapped the input processing in a try-except block
- Convert user input to integer using `int(user_input)`
- Added error handling for invalid input with user-friendly message
- Used the converted integer value in the f-string instead of raw string
input

This ensures type safety and provides better user experience with proper
error handling.

…1354)

Automated update of translated documentation

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

This pull request migrates the translation script from o3 to gpt-5
model.

…#1472)

Automated update of translated documentation

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

There was a problem with the current implementation, where for a single
repsonse, we might have many different guardrails fire. We should have
at most one per response.