Step 1/N for implementing typed-events; first just preserve the existing behaviors with no changes to the public api.

A follow-up change will update how we invoke callbacks and pass invocation_state around, while this one just adds typed classes for events internally.

---------

Co-authored-by: Mackenzie Zastrow <[email protected]>

* summarization manager - add summary prompt to messages

* summarize conversation - assistant to user role

* fix test

* add period

Move away from "callback" nested properties in the dict and explicitly passing invocation_state migrating to behaviors on the TypedEvent:

 - TypedEvent.is_callback_event for determining if an event should be yielded and or invoked in the callback
 - TypedEvent.prepare for taking in invocation_state

Customers still only get dictionaries, as we decided that this will remain an implementation detail for the time being, but this makes the events typed all the way up until *just* before we yield events back to the caller

---------

Co-authored-by: Mackenzie Zastrow <[email protected]>

* feat: add citations to document content

* feat: addes citation types

* chore: remove uv.lock

* test: add letter.pdf for test-integ

* feat: working bedrock citations feature

* feat: fail early for citations with incompatible models

* fix: validates model ids with cross region inference ids

* Apply suggestion from @Unshure

Co-authored-by: Nick Clegg <[email protected]>

* fix: addresses comments

* removes client exception handling
* moves citation into text elif
* puts relative imports back

* fix: tests failing

* Update src/strands/models/bedrock.py

Removes old comment

Co-authored-by: Nick Clegg <[email protected]>

* Update src/strands/models/bedrock.py

Removes old comment

Co-authored-by: Nick Clegg <[email protected]>

* Update imports in bedrock.py

Refactor imports in bedrock.py to include CitationsDelta.

* feat: typed citation events

---------

Co-authored-by: Nick Clegg <[email protected]>

It's been a customer ask and we don't have a pressing need to keep it restricted.

The primary concern is that because agent's state is manipulated between invocations (state is reset) hooks designed for a single agent may not work for multi-agents. With documentation, we can guide folks to be aware of what happens rather than restricting it outright.

---------

Co-authored-by: Mackenzie Zastrow <[email protected]>

Addresses issue #579, #750

---------

Co-authored-by: Mackenzie Zastrow <[email protected]>

Co-authored-by: Dean Schmigelski <[email protected]>

* fix: fix stop reason for bedrock model when stop_reason is end_turn in tool use response.

* change logger info to warning, optimize if condition

* fix: add unit tests

---------

Co-authored-by: Jack Yuan <[email protected]>

Expand the Unit Tests for the yielded event to verify actual tool calls - previous to this, the events were not being emitted because the test was bailing out due to mocked guard rails.  To better test the situation, we now have a much more extensive test for the successful tool call

Co-authored-by: Mackenzie Zastrow <[email protected]>

* fix: fix loading tools with same tool name

* simplify if condition

---------

Co-authored-by: Jack Yuan <[email protected]>