[vishwakt]

Issue number: closes #8584

Summary

Changes

One fix plus one test per bug, in the order listed in the issue:

1. Bedrock Agent kwargs: with enable_validation=False, every event parameter was injected as a kwarg, so a query parameter missing from the handler signature raised TypeError. _convert_matches_into_route_keys now injects only parameters matching the route path keys.
2. Bedrock Agent response media type: a Response without a content type produced "responseBody": {"null": {...}}. The media type key now defaults to application/json.
3. AppSync Events registry: registering a resolver with an invalid path warned and returned None, so the decorated function name was bound to None. The function is now returned unregistered.
4. AppSync context leak: resolve() returned the exception handler result before clear_context(), so app.context leaked into the next invocation. Clearing now happens in a finally block. The coroutine exemption from Bug: Router context not being available when using AppSync with async resolvers #5290 is preserved, and an unhandled exception now also clears the context, which matches the documented behavior of clearing after every invocation.
5. Router duplicates: Router silently overwrote a duplicate route registration while the resolver warns. Router.route now emits the same warning.
6. Function URL base path: _get_base_path compared request_context.http.method against the stage prefix instead of http.path. Unreachable today since Function URLs only use $default, fixed as a typo and covered by a direct test of the method.
7. Depends with a class: Depends(SomeClass) read annotations with get_type_hints on the class, which returns class-level attributes, so Request injection and nested Depends declared on __init__ were never found. Hints are now read from __init__ when the dependency is a class.

User experience

Each repro from the issue snippet now behaves as expected: no TypeError for extra Bedrock parameters, a valid media type key, the decorated AppSync Events function stays usable, app.context is empty after an exception handler runs, duplicate Router routes warn, and a class dependency can receive Request or nested Depends.

Seven tests added, one per bug, each verified to fail before its fix. Full tests/functional/event_handler and tests/unit/event_handler suites pass (1198 tests), ruff and mypy clean on the changed files.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[leandrodamascena]

Thanks @vishwakt, all seven hold up. I ran the AppSync context one on a real Lambda with three warm invocations: on develop each invocation started with the context left by the previous one, with your finally it starts empty every time while the exception handler still sees the current invocation's context. The Bedrock kwargs and media type, the Events registry, the Router warning and the class-based Depends all behave as the issue asked.

Your branch conflicted with tests I had added to test_depends.py in the meantime, so I merged develop into it keeping both sets and formatted the file. Nothing for you to do.

Approving. This goes out in 3.39.0, so it will sit here for a while before I merge it. I'll note in the release notes that AppSyncResolver now also clears the context when an exception propagates, since that is visible. You'll be credited there.