fix: Set messages in state_schema at init time of Agent

[sjrl]

Related Issues

• fixes Agent component doesn't have an output called messages #9193

Proposed Changes:

• Set messages in state_schema at init time of Agent. This is needed to properly set messages as an output type of Agent and was the original intent of this PR feat: Move storing of messages into State in Agent #9150

How did you test it?

• Added tests
• Also added more tests for State

Notes for the reviewer

Most of the line changes come from adding tests.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 14373748478

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 6 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.03%) to 90.378%

---

Files with Coverage Reduction	New Missed Lines	%
dataclasses/state.py	1	98.25%
components/agents/agent.py	5	95.24%

Totals
Change from base Build 14373744615:	0.03%
Covered Lines:	10670
Relevant Lines:	11806

---

💛 - Coveralls

[mpangrazzi]

LGTM! One thing (but you're probably aware of): modifying a mutable object obtained via get() can affect the internal state directly.

Example:

def test_state_mutability():
    state = State({"my_list": {"type": list}}, {"my_list": [1, 2]})

    my_list = state.get("my_list")
    my_list.append(3)

    assert state.get("my_list") == [1, 2, 3]

Feel free to ignore if you don't think this can possibly be a bug ;)