[felipefreitag]

Type checkers now accept topic_id when you read a broadcast. The API already returns the field, but the response type did not declare it, so strict mypy rejected the key.

Not covered. Six other broadcast response fields can be null, but the SDK still types them as strings. A nullable type can break type checks in user code, so that change needs its own release decision.

---

Summary by cubic

Declares topic_id on the Broadcast response type so strict type checkers accept the field. The API already returns it, so there's no runtime behavior change.

Not covered

• Six other broadcast response fields can be null but are still typed as strings, which can break type checks in user code.

^{Written for commit 5dac853. Summary will update on new commits.}

[klotty]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Auto-approved: Adds the optional topic_id field to the Broadcast response type and tests it with null and non-null values; no runtime behavior changes, so the change is bounded and clearly beneficial.

View guided diff | Re-trigger cubic</sub>