Skip to content

Type a run response state as RunState - #358

Merged
czpython merged 1 commit into
mainfrom
orphaned-run-in-a-timeline
Aug 30, 2026
Merged

Type a run response state as RunState#358
czpython merged 1 commit into
mainfrom
orphaned-run-in-a-timeline

Conversation

@czpython

Copy link
Copy Markdown
Owner

RunResponse.state pinned the state to a Literal of six values while RunState declares seven. from_run silenced the mismatch with a # type: ignore.

RunResponse and from_run are on the author surface, so an app that held an orphaned run got a ValidationError instead of a response. The field takes RunState now, so every state a run can derive projects.

The read side is unaffected: an orphaned run has no workflow_status row, so it never matches a subject and never reaches a timeline.

RunResponse pinned state to a Literal of six states while RunState declares
seven, and from_run silenced the mismatch with a type: ignore. from_run is on
the author surface, so an app holding an orphaned run got a validation error
instead of a response. The field takes RunState now.
@czpython
czpython merged commit d74e47c into main Aug 30, 2026
1 check passed
@czpython
czpython deleted the orphaned-run-in-a-timeline branch August 30, 2026 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant