chore(release): finalize 2.17.0

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/whatsnew.md

@@ -10,13 +10,17 @@ For deep technical notes, see [architecture.md](architecture.md). For the full g
 
 ## Unreleased
 
+---
+
+## 2.17.0 — 2026-09-07
+
 ### Features
 
 - **Repeater regions can now be managed from the interface, not just the CLI.** A repeater decides which *flood-scoped* packets it passes on from its own list of regions — a name like `pl` that a sender stamps on a packet, which only repeaters allowing that region will forward. Setting that up meant typing `region` commands into the console and reading back an indented text tree. **My Repeaters → Settings → Regions** now shows that tree as a list: each region with its **Flood allowed** / **Flood denied** state, nested regions indented under their parent, and the **home** region marked. A ⋮ menu on each row allows or denies flood, sets the home region, **moves the region somewhere else in the hierarchy** (previously only possible by deleting it and adding it again), or deletes it, and **Add region** takes a name plus an **Inside** picker, so a region can be nested inside an existing one or left at the top level. The wildcard row at the top — *Packets without a region scope* — is the rule for ordinary unstamped packets, and can be switched like any other. Below the list, **Default scope** sets the region this repeater stamps on packets it sends itself.
 
   Changes behave the way the firmware does, and the screen is explicit about it: adding, deleting or switching a region takes effect at once but lives only in the repeater's memory, so an orange banner appears until you press **Save**, and leaving with unsaved changes asks first. Without that save the repeater forgets them at its next reboot. The Default scope card is the exception — the firmware stores that one by itself, and the card says so.
 
-- **The Path Analyzer's map can be maximized to the whole screen.** On a phone the map view splits the screen between the message list and the map, leaving the map about 45% of the height — enough to know a route was drawn, not enough to read it. The ⛶ button in the map's top-right corner now expands the map over everything else, the panel header included, so a five-hop route across half of Poland is legible without pinching. The button turns into **✕ Close** while maximized, Escape does the same, and either way the route you had drawn and the area you had panned to are still there when the normal layout comes back.
+- **The Path Analyzer's map can be maximized to the whole screen.** On a phone the map view splits the screen between the message list and the map, leaving the map about 45% of the height — enough to know a route was drawn, not enough to read it. The ⛶ button in the map's top-right corner now expands the map over everything else, the panel header included, so a five-hop route across half of Poland is legible without pinching. The button turns into **✕ Close** while maximized, Escape does the same, and either way the route you had drawn and the area you had panned to are still there when the normal layout comes back. To make room for it, the **All repeaters** and **Alternative paths** checkboxes moved from the map's top-right corner to the bottom-left.
 
 ---