fix(ui): keep pushed screens clear of the Android navigation bar

Plezy is edge-to-edge on Android whether it asks to be or not: targetSdk is
36, Android 15 enforces edge-to-edge for apps targeting 35+, and Android 16
disables the windowOptOutEdgeToEdgeEnforcement escape hatch. The only
SystemUiMode.edgeToEdge call in the app fires on video-player exit, so on
API 35+ the window is edge-to-edge from the first frame and
MediaQuery.padding.bottom is a real ~48dp overlap under 3-button navigation.

MainScreen's phone layout hides that. It supplies a bottomNavigationBar and
never sets extendBody, so Flutter's Scaffold strips padding.bottom from the
body MediaQuery and every tab is already safe. Routes pushed on the profile
navigator are full-screen siblings of MainScreen with no bottom bar, so they
receive the untouched inset and nothing consumes it - the last settings card
and the final log lines render under the back, home, and recents buttons.

Three shared hosts own most of those routes, so the inset is consumed there:
FocusedScrollScaffold (25 screens, counting the SettingsPage wrapper) and
FocusableDetailScreenMixin.buildDetailScaffold (4) now append a trailing
SliverSystemBottomInset, and the four screens that build their own Scaffold
around a CustomScrollView append it directly.

The new widget codifies the convention this repository had already written
down but open-coded - insets baked into the scroll content rather than a
SafeArea around the scroll view - so content still paints under the bar while
the scroll extent grows enough to bring the last row above it. It reads
padding from its own context and collapses to zero height wherever the inset
is already zero: desktop, Android TV, tvOS via _AppleTvScale, and inside
MainScreen's tab bodies. No platform branching, and it stacks additively with
the music detail screens' existing mini-player spacers, which is correct
because the mini-player itself floats above the navigation bar on a pushed
route.

Scroll views that are not sliver lists take the inset in their own padding:
the companion remote's ListView, the auth screen's scroll container, and the
two SliverFillRemaining sign-in forms, whose children size themselves from
the extent remaining before them and so cannot be helped by a trailing
sliver. The logs empty state is left alone for the same reason inverted - it
already fills the viewport, and a trailing inset would only add scroll slack.

Verified on a Pixel 7 running Android 16 (API 36) with 3-button navigation:
Settings, Logs, and Video Playback all end clear of the bar.

close #1766

lib/widgets/focused_scroll_scaffold.dart

@@ -3,6 +3,7 @@ import '../focus/input_mode_tracker.dart';
 import '../focus/key_event_utils.dart';
 import 'desktop_app_bar.dart';
 import 'ios_status_bar_tap_scroll_to_top.dart';
+import 'system_bottom_inset.dart';
 
 /// A scaffold widget that wraps Focus + Scaffold + CustomScrollView
 /// with consistent keyboard navigation handling and app bar styling.
@@ -122,6 +123,9 @@ class _FocusedScrollScaffoldState extends State<FocusedScrollScaffold> {
                     automaticallyImplyLeading: widget.automaticallyImplyLeading,
                   ),
                 ...widget.slivers,
+                // Keeps the last row scrollable clear of the Android
+                // navigation bar / iOS home indicator; zero-height elsewhere.
+                const SliverSystemBottomInset(),
               ],
             ),
           ),

lib/widgets/system_bottom_inset.dart

@@ -0,0 +1,34 @@
+import 'package:flutter/widgets.dart';
+
+/// Reserves the system bottom inset — Android's navigation bar, iOS's home
+/// indicator — at the end of a scroll view.
+///
+/// Plezy always runs edge-to-edge on Android: `targetSdk` is 36, and Android
+/// 15 enforces edge-to-edge for apps targeting 35+ while Android 16 removes
+/// the opt-out entirely. So `MediaQuery.padding.bottom` is a real overlap on
+/// phones (~48dp with 3-button navigation, less with gesture navigation) and
+/// every full-screen pushed route has to consume it.
+///
+/// The convention is to bake the inset into the scroll *content* rather than
+/// wrapping the scroll view in a [SafeArea]: content keeps painting under the
+/// bar, and only the scroll extent grows so the last row can be scrolled clear
+/// of it. See `media_detail_screen.dart` and `discover_screen.dart` for the
+/// hand-rolled precedents this widget replaces.
+///
+/// Collapses to zero height wherever the bottom padding is already zero, so it
+/// needs no platform branching: desktop and Android TV report no inset, tvOS
+/// has it zeroed by `_AppleTvScale`, and inside `MainScreen`'s tab bodies
+/// Flutter's [Scaffold] has already stripped it because a `bottomNavigationBar`
+/// is present.
+///
+/// Reading the padding from this widget's own [BuildContext] — instead of the
+/// enclosing screen's — keeps it correct below any ancestor that removes
+/// padding, and limits inset-driven rebuilds to the spacer itself.
+class SliverSystemBottomInset extends StatelessWidget {
+  const SliverSystemBottomInset({super.key});
+
+  @override
+  Widget build(BuildContext context) {
+    return SliverPadding(padding: .only(bottom: MediaQuery.paddingOf(context).bottom));
+  }
+}