Prepare the requested observer/UI cleanup for the 1.3.2 release, before post-release My Atlas #97. Keep the observer list on the left while displaying monitoring; use a compact coloured status icon; remove the marked traffic badge, duplicate observer picker, explanatory paragraphs and exact-activity table. Remove the channel scope-help block and Analytics retention banner, and collapse the Mesh overview scope table. Keep useful data/error states, English/French labels, keyboard access and the existing bounded queries. Navigation begins with Observers, followed by Packets, Channels, Map, Nodes, Routes, Traces and Analytics; Atlas remains excluded from this release.
The map layer currently receives HTTP 204 for YKF/YOW on both sites because no boundaries are configured. Restore geometry from validated public MeshMapper boundary snapshots through the existing borderFile support, with operator documentation and rollback, without adding a recurring importer or per-ingest work during this release freeze.
The maintainer's open PR review fixes are addressed on their own branches before this cleanup. Test the complete release candidate on the Pi, update the source/changelog and roadmap, and keep production merges/version tags under maintainer control.
Prepare the requested observer/UI cleanup for the 1.3.2 release, before post-release My Atlas #97. Keep the observer list on the left while displaying monitoring; use a compact coloured status icon; remove the marked traffic badge, duplicate observer picker, explanatory paragraphs and exact-activity table. Remove the channel scope-help block and Analytics retention banner, and collapse the Mesh overview scope table. Keep useful data/error states, English/French labels, keyboard access and the existing bounded queries. Navigation begins with Observers, followed by Packets, Channels, Map, Nodes, Routes, Traces and Analytics; Atlas remains excluded from this release.
The map layer currently receives HTTP 204 for YKF/YOW on both sites because no boundaries are configured. Restore geometry from validated public MeshMapper boundary snapshots through the existing borderFile support, with operator documentation and rollback, without adding a recurring importer or per-ingest work during this release freeze.
The maintainer's open PR review fixes are addressed on their own branches before this cleanup. Test the complete release candidate on the Pi, update the source/changelog and roadmap, and keep production merges/version tags under maintainer control.