chore(docs): audit every screenshot for identity and branding leaks

CHANGELOG.md

@@ -30,6 +30,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 
+- **Six documentation screenshots carried the deployment's own branding, and two of them a real Discord avatar photo.** An audit of all seventy committed images found the site title "PoGO Alerts Network" in the toolbar of `areas`, `user-menu` (both the docs and in-app copies), `pokemon-add-dialog`, `fort-changes-add-dialog` and `scope-picker`, the operator's custom back-to-map nav link beside it, and beneath the grey silhouette placeholder on three of them the original avatar photo still showing around the rim, where an earlier pass had pasted a circle a few pixels too small. The three dialog shots were retaken against an anonymous session; `areas` and the two `user-menu` copies had the toolbar band replaced, which fixes all three leaks at once without discarding the configured pin, places and areas that made those images worth having. The other sixty-four images are clean.
 - **Deleting a saved place that alarms still point at says which alarms.** The refusal already carried the list, but each entry arrived as a fragment of raw JSON rather than a name, so there was nothing worth showing and the count was all anyone could use. It now reads as "raid 424". Deleting a place was also the last thing on this page still talking to Poracle's older API while everything around it had moved.
 - **Your alert language stops being forgotten when it is Portuguese (BR).** Poracle stores what it is given in lower case, so `pt-BR` comes back as `pt-br`, and the language picker was comparing the two exactly -- finding no match, discarding the answer and quietly falling back to the server's own language. It affected anyone whose alert language was set through the Poracle bot as well. The comparison ignores case now.
 - **Saving a place with a name you already have says so, instead of reporting a server error.** Poracle answers this one differently on its two API surfaces, and the newer answer -- a genuine refusal, with a reason -- was being read as the server having broken. So was a name too long for the column, which now never leaves the browser: 64 characters, said plainly, rather than a database error relayed verbatim.
@@ -54,7 +55,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Every version requirement in the docs said 5.2.1 and every gate in the code says 5.2.0.** 5.2.1 is the release production happens to run, not the release that added the features, so a self-hoster on exactly 5.2.0 was told four working features were unavailable to them. Corrected on the compatibility page, and the page now names the three constants it is describing so the next drift is visible.
 - **The in-app help covers the new features too, in all eleven languages.** It gained a Quiet Periods section, an Active Hours section -- which the help had never explained despite the quest summary page referring readers to it twice -- and entries for costume filters, PokéCoin rewards, Pokéstop Events and the rule description on an alarm card. The FAQ's "why am I not getting alerts" list now includes a quiet period as a cause, since that one produces silence with no banner to spot, and gained an entry for the controls that appear only on a new enough Poracle server, which is the likeliest reason something the guide describes is not on your screen.
 - **Screenshots refreshed.** The dashboard, the Pokemon list, the profiles page, the quest dialog and the server versions card all showed a site that no longer exists, and new ones were taken for the Pokéstop Events dialog, the quiet sheet, the PokéCoins tab and a repeating schedule rule.
-- **The PoracleNG version compatibility page has been rewritten, and its premise replaced.** It described PoracleNG as having two long-lived branches and this site supporting both; develop shipped as 5.2.1 and merged, so the real question is 5.1.0 versus 5.2.1 and newer. It now covers how support is decided, why a database migration number is a better thing to gate on than a version string, which features need a newer server, how to add another, and two traps worth knowing: PoracleNG's v1 API is unchanged on 5.2.1 -- the new error format and status codes in its release notes apply to v2 only -- and its OpenAPI document numbers the days of the week differently from the scheduler that reads them.
 
 ## [2.17.1] - 2026-08-21