fix: pin starlette dependency to >=1.1.0 (#184)

## Summary
- Pin the `starlette` dependency to `>=1.1.0` in both the codegen
template and the generated Python SUT `pyproject.toml`
- Previously the dependency was unpinned, accepting any version

## Test plan
- [x] Python SUT `uv sync` resolves successfully with starlette 1.1.0
- [x] Java SUT TCK tests pass (242 passed, 99% compatibility)
- [x] Pre-commit hooks pass (ruff lint + unit tests)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

feat: add push notification webhook delivery tests (#178)

Add tests that spin up a lightweight HTTP server to receive push
notification webhooks from the SUT, verifying at-least-once delivery,
authentication headers (both token and Authorization), and v0.3 Task
object payload format.

Also fix gRPC client to pass the authentication field through when
setting push notification configs.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

feat: allow additional fields in Agent Card schema validation (#179)

The A2A spec permits extension fields on agent cards, but the JSON
schema's additionalProperties:false was rejecting them. Add an
allow_additional parameter to JSONSchemaValidator.validate() that strips
that constraint, so the TCK validates structure and types without
rejecting unknown fields.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

fix: Remove 0.4.0 features from 0.3.x branch. (#171)

Also undoes the added PushNotificationConfig tests.
Better lifecycle handling of gRPC clients

---------

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
Co-authored-by: Emmanuel Hugonnet <ehugonne@redhat.com>

Fixing resubscribe issue and removing hardcoded answers for gRPC

tagging 0.3.0 beta2 version

tagging 0.3.0 beta version

Maeste/issue37 (#47)

# Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:

- [x] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #37

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

fix: Remove test_message_send_continue_nonexistent_task and the corre…

…sponding handling from the python-sut agent executor implementation since it's not needed (#34)

fixing gitignore