rebase before landing

fix frog callback return type to be Promise<FrogResponse> | FrogResponse

rebase

fix setting parent

rebase

rebase

rebase

rebase

rebase

In D14086#392872, @ashoat wrote:

I haven't actually seen this utilized when we render the frame on the validator or warpcast, so I don't believe the title matters too much

Sounds like you don't know how it's used. It would be good to figure out before landing this... I worry that, for instance, we'll end up with an application titled "Comm Frame" in some mini-app directory.

I think it would probably be better to just use "Comm" if you truly have no clue what this is or how it is used, even after spending an hour or so trying to dig up information.

rebase

change frame title to "Comm Frame" instead of "Comm Frame App"

feedback

feedback

feedback

feedback

rebase

feedback

feedback and changed button label from "Invite Link" to "Join chat"

Testing that adding WEB_PUSH_ERROR and APNS_ERROR error types to an error log will trigger an alarm + email notif has already been tested. I don't think this needs further testing.

use /* eslint-disable approach

move react.automatic line

avoid flow errors by setting react.runtime option to automatic