Translations and renamed posts show at once, monitor interval edits, UTF-8 bodies

Fixed

Publishing a translation updates its address immediately. Publishing a page's locale twin now drops every address a reader can ask for it at — ?locale=<code> on the original page's address and the /<code>/<page> path form — from both our web tier and the edge, on your own domains too. Legal documents are included: publishing the Spanish version of your privacy policy shows at /legal/privacy?locale=es straight away, with no manual purge.

A renamed blog post's old address redirects straight away. The old address answered 404 (only a request carrying a query string reached the 308). It now redirects to the new one at once, and the rename drops both addresses from every cache.

POST …/spaces/{spaceId}/cache/purge purges the whole space. It used to reach only the current addresses of live pages, so a blog (whose posts are not pages), the old address of a renamed piece and translation variants were left as they were. It now clears everything under the space's addresses.

PATCH …/status/monitors/{monitorId} with intervalSeconds no longer answers 500. Every PATCH that touched the interval failed, including one that resent the current value. It is now applied (clamped by the monitor's kind, as before), and resending a value the monitor already has is a 200 that changes nothing.

Changed

A request body that is not valid UTF-8 is a 400 request.malformed. It used to be decoded with the unreadable bytes replaced by � and stored that way — a Latin-1 Español became Espa�ol for good. Nothing is written now. A body whose Content-Type names another charset is unaffected. See API conventions.