feat: upgrade to api spec v129.24.0

[szuperaz]

Breaking changes

1. Chat API – return type change

• runMessageAction, commitMessage, translateMessage now return
  Promise<StreamResponse<MessageActionResponse>> instead of
  Promise<StreamResponse<MessageResponse>>.
• Import change: MessageResponse was replaced by MessageActionResponse for these methods. Code that types the result as MessageResponse or destructures assuming MessageResponse will break.

---

2. Removed types / decoders (no direct replacement)

• ActivityMarkedEvent – removed.
• AnyEvent – removed.
• Channel – removed (replaced by ChannelResponse in event payloads).
• ChannelMember – removed (replaced by ChannelMemberResponse).
• ChannelMemberLookup – removed.
• Device – removed (only DeviceResponse remains).
• Message – removed (use MessageResponse).
• DeliveryReceipts, ReadReceipts, TypingIndicators – removed.
• DenormalizedChannelFields – removed.
• MessageReminder, Poll, PollOption, PollVote – removed.
• PrivacySettings, PushPreferences – removed (replaced by request/response variants).
• SessionClient – removed.
• SortParam – removed.
• OwnUser – removed (check current exports for replacement).
• ConfigOverrides, Coordinates, Location, Label, LimitInfo – removed (replaced by *Response or *Request variants).
• Flag, FlagDetails, FlagFeedback, FlagMessageDetails – removed (replaced by *Response).
• ModerationActionConfig – removed (replaced by ModerationActionConfigResponse).
• FeedsModerationTemplateConfig – removed (replaced by FeedsModerationTemplateConfigPayload).
• ChannelMessages – removed (replaced by ChannelMessagesResponse).
• ChannelPushPreferences – removed.
• ParsedPredefinedFilter – removed (replaced by ParsedPredefinedFilterResponse).

Any code that imports or references these types/decoders will break.

---

3. Renamed types (same shape, new name)

Old name	New name
AutomodDetails	AutomodDetailsResponse
Ban	BanInfoResponse (and channel/target → user)
MessageResponse (for action endpoints)	MessageActionResponse
ReactionGroupResponse (in Feeds)	FeedsReactionGroupResponse

---

4. Request/response type renames

Many request types were renamed with a Payload or Request/Response suffix, e.g.:

• BanActionRequest → BanActionRequestPayload
• BlockActionRequest → BlockActionRequestPayload
• ChannelMemberRequest / ChannelMemberResponse – redefined (previously different shapes).
• ConfigOverrides → ConfigOverridesRequest
• CustomActionRequest → CustomActionRequestPayload
• DeleteActivityRequest → DeleteActivityRequestPayload
• DeleteCommentRequest → DeleteCommentRequestPayload
• DeleteMessageRequest → DeleteMessageRequestPayload
• DeleteReactionRequest → DeleteReactionRequestPayload
• DeleteUserRequest → DeleteUserRequestPayload
• MarkReviewedRequest → MarkReviewedRequestPayload
• RejectAppealRequest → RejectAppealRequestPayload
• RestoreActionRequest → RestoreActionRequestPayload
• SIPChallenge → SIPChallengeRequest
• ShadowBlockActionRequest → ShadowBlockActionRequestPayload
• UnbanActionRequest → UnbanActionRequestPayload
• UnblockActionRequest → UnblockActionRequestPayload

Imports or type annotations using the old names will break.

---

5. Ban / BanInfoResponse shape change

• Ban → BanInfoResponse:
  • channel and target were removed.
  • user (replacing target) and created_by are now UserResponse.
    Code that used Ban.channel or Ban.target will break.

---

6. Event payloads – User → UserResponseCommonFields

Channel and related events now use UserResponseCommonFields instead of User for the user field (e.g. ChannelHiddenEvent, ChannelUpdatedEvent, ChannelVisibleEvent, ChannelCreatedEvent, ChannelDeletedEvent, ChannelMutedEvent, ChannelUnmutedEvent, ChannelTruncatedEvent).
Some events also gained received_at and channel. Code that types user as User will break.

---

7. ActivityResponse (Feeds)

• reaction_groups type: ReactionGroupResponse → FeedsReactionGroupResponse.

---