v0.3 REST GetTask returns 500 for a non-integer historyLength #1381

What happens

GET /v1/tasks/{id}?historyLength=abc on the v0.3 REST transport returns 500 INTERNAL with unknown exception. The v1.0 REST transport returns 400 INVALID_ARGUMENT for the same input.

Why

REST03Handler.on_get_task calls int() on the query value directly, and the ValueError is not mapped to an A2A error.

Version

main @ e12d494