Give DodoSSH a phone, and a shared shell for both heads to drive

The Android head from docs/android-port.md, taken as far as its step 6.

Step 3, the spike, is answered and its throwaway screen is gone: libsodium.so and
libe_sqlite3.so are both in the arm64 APK, so NSec resolves its native half on Android
despite shipping no Android build, and the local cache opens. Two findings the audit
could not have had: Avalonia.Controls.WebView only ships net10.0-android36.0, which
settles the open "which Android versions" question at targetSdk 36; and Android has
blocked cleartext HTTP since API 28, so the terminal renderer needs a network security
config scoped to 127.0.0.1 or the WebView loads nothing.

DodoSSH.Client.Shell is new and is why the phone can exist: the view models, the terminal
renderer files and the palette moved there so both heads drive one state machine and draw
from one set of tokens. The desktop head is otherwise untouched and its 144 tests still
pass.

The platform pieces behind interfaces that already existed: the profile directory from
filesDir, a device key wrapped by a StrongBox-backed key that a fingerprint releases, and
a foreground service so a shell outliving a vault lock stays true on a platform that
stops backgrounded processes.

Sign-in is deliberately absent rather than approximated. It needs an app link, because
reusing the desktop loopback listener is the attack RFC 8252 section 8.3 names.

src/DodoSSH.Client.Android/Views/PendingScreen.axaml

@@ -0,0 +1,38 @@
+<UserControl xmlns="https://github.com/avaloniaui"
+             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
+             xmlns:views="using:DodoSSH.Client.Android.Views"
+             x:Class="DodoSSH.Client.Android.Views.PendingScreen"
+             x:DataType="views:PendingScreen"
+             Background="{StaticResource Canvas}">
+
+  <!--
+    The phone's counterpart of the desktop head's NotBuiltScreen, and it exists for the same reason: a
+    screen that is not built says so, in its own words, rather than being dropped from the shell or filled
+    with plausible-looking data. See README — nothing here is rendered with invented data.
+
+    Two properties rather than a shared string, because the copy is written per state. "No items" would be
+    the exact failure this control is here to avoid.
+  -->
+
+  <ScrollViewer>
+    <StackPanel VerticalAlignment="Center" Margin="24,48" Spacing="12">
+
+      <Border Width="44" Height="44" BorderBrush="{StaticResource BorderMid}" BorderThickness="1"
+              HorizontalAlignment="Left">
+        <TextBlock Text="&gt;_" Foreground="{StaticResource TextFaint}" FontFamily="{StaticResource MonoFont}"
+                   FontSize="16" FontWeight="SemiBold"
+                   HorizontalAlignment="Center" VerticalAlignment="Center" />
+      </Border>
+
+      <TextBlock Text="{Binding Heading}" Foreground="{StaticResource Text}"
+                 FontFamily="{StaticResource MonoFont}" FontSize="14" FontWeight="SemiBold"
+                 TextWrapping="Wrap" />
+
+      <TextBlock Text="{Binding Detail}" Foreground="{StaticResource TextDim}"
+                 FontFamily="{StaticResource MonoFont}" FontSize="11" LineHeight="19"
+                 TextWrapping="Wrap" />
+
+    </StackPanel>
+  </ScrollViewer>
+
+</UserControl>