Corregido Internal

Team chat and recording downloads refuse requests from other sites

A link or page on another site can no longer change anything in Team chat, or start preparing a recording's download, in a signed-in person's name.

/chat-api runs only its reads on a GET (ChatApiActions::READS); muting, blocking, opening a support conversation and every other change answer 405 unless they come as a POST with the chat token. The Download button on a recording's share page now sends the page's token, and /r/{uuid}/download refuses a request without it (419). PostHandlersCheckCsrfTest fails on any script in public/ that takes a POST without checking a token, unless it is listed with what proves the request came from Magpie's own page (a webhook signature, an OAuth client, a link secret).