Give the application a settings area built from what really exists

src/DodoSSH.Client.App/Views/ImportScreen.axaml.cs

@@ -1,6 +1,5 @@
 using Avalonia.Controls;
 using Avalonia.Controls.Primitives;
-using Avalonia.Input;
 using Avalonia.Interactivity;
 using DodoSSH.Client.Shell.ViewModels;
 
@@ -10,7 +9,11 @@ namespace DodoSSH.Client.App.Views;
 /// Importing hosts from <c>~/.ssh/config</c>.
 /// </summary>
 /// <remarks>
-/// A task rather than a destination, which is why it is reached from preferences and not from the nav rail.
+/// A task rather than a destination, which is why it is reached from Preferences rather than from the nav
+/// rail. v5c-3 moved it inside settings mode as an overlay over the Preferences page — it no longer has a
+/// keyboard target of its own to hand back: <c>MainWindow.axaml.cs</c>'s <c>KeyboardHome</c> falls back to
+/// the window for settings mode as a whole, the same way it already does for the account and logs screens,
+/// so a <c>KeyboardTarget</c> property here would be dead code nothing reads.
 /// </remarks>
 internal sealed partial class ImportScreen : UserControl
 {
@@ -24,9 +27,6 @@ internal sealed partial class ImportScreen : UserControl
         AddHandler(ToggleButton.IsCheckedChangedEvent, OnTickChanged, RoutingStrategies.Bubble);
     }
 
-    /// <summary>Where the keyboard lands when this screen is the one showing.</summary>
-    internal IInputElement KeyboardTarget => this;
-
     private void OnTickChanged(object? sender, RoutedEventArgs e)
     {
         if (DataContext is ImportViewModel import)