@vladyslav
can action: { type: 'form' } be used here to allow an easier separation for cast actions and composer actions for warpcast/other app clients?
an action with such type would be only allowed to respond with type: 'form' message.
or is there another way to detect if an action is a composer action or a cast action?