v10.1.5-alpha — Snapshot map feeds stop stranding dead shapes on devices

What's new

Snapshot-style map feeds — fire perimeters above all — get a proper lifecycle, so devices stop accumulating outdated shapes that never go away.

Sources like the California fire-perimeter layer publish a brand-new record every time a fire changes. Until now that meant every update was a delete-and-re-add, and any device that happened to be offline at that moment kept the stale outline on its map indefinitely — because the client never learns about deletions it missed while away.

This release fixes that end to end:

• Stable identity per real-world entity. A feed can now key each shape to a stable value (e.g. per fire) so a growing fire updates the same shape in place instead of leaving a trail of orphans. Feeds that don't need this are unchanged.
• No more map churn. Feeds stop flip-flopping between competing versions of the same feature, so shapes hold steady instead of flickering on and off.
• Clear Ghosts. A one-tap action per feed that sweeps already-orphaned shapes off every device as it reconnects over the following two weeks — automatically, with no per-device cleanup and no touching anyone's tablet.
• Map bridge sees every channel again. On deployments where the built-in map's server connection had been pinned to an empty channel set, live feeds now reliably reach it.

Also in this release — fresh install & update robustness:

• A brand-new server that doesn't yet have Docker now installs it correctly on locked-down (non-root) setups, instead of failing mid-deploy.
• The automatic post-update step that refreshes map feeds could silently skip on some servers — it now runs on every update.
• An internal permissions issue that could make a feed refresh fail on the strictest security posture is resolved.

Upgrade: applied automatically on the next console update. Healthy boxes are left untouched.