fix(seer): Make ToolResult.content optional to prevent Pydantic validation error

[sentry]

This PR addresses a ValidationError for SeerRunState that occurred when deserializing responses from Seer. The error, none is not an allowed value for blocks -> tool_results -> content, stemmed from a schema mismatch.

Seer's internal Message model, used for tool results, allows content to be None (e.g., for tool-call-only assistant messages). However, Sentry's ToolResult Pydantic model in src/sentry/seer/agent/client_models.py defined content as a non-optional str.

The fix updates ToolResult.content from str to str | None = None, aligning Sentry's client model with Seer's actual data structure. An audit for existing usages of tool_result.content in Sentry found no direct accesses that would break with this change, ensuring a safe and targeted fix.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Fixes SENTRY-5P20

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit fe11775. Configure here.}

[cursor]

Frontend TypeScript type not updated for nullable content

Low Severity

Making ToolResult.content nullable in the Python model means null values now flow through to the frontend API response. The corresponding TypeScript ToolResult interface in static/app/views/seerExplorer/types.tsx still declares content: string as required and non-nullable. While no frontend code currently accesses .content on ToolResult, this type mismatch can silently mislead a future developer into assuming content is always a string, potentially causing a runtime error.

 

^{Reviewed by Cursor Bugbot for commit fe11775. Configure here.}