Let the desktop client replace itself, and give the repository one version

Packaging for Windows, and the updater that only exists once something is
packaged. Velopack, win-x64, fed from the project's own forge — never from the
deployment a client signs in to, which is ADR 0011 rule 2 carried over
unchanged and is why the feed address is a constant in the code rather than a
setting. See docs/adr/0012-desktop-distribution-and-updates.md.

**Nothing is ever installed while somebody is using it.** A newer build is found
on a six-hourly pass, downloaded in the background, and then waits — for a
restart the user presses, or for the next launch they were going to do anyway.
That is a policy rather than caution: this application argues at length that
locking keeps shells running, because a lock that destroyed work would stop
being used, and a restart does not keep them. Having taught that, it owes the
user the choice at the one moment it stops being true, and the sentence saying
so counts the shells it would close.

**The version is now derived from the v* tag**, by MinVer, for everything. There
was no version before this — no property anywhere, so every assembly reported
the SDK's 1.0.0 and the API served that string as its serverVersion to every
client that asked. The tag was already the version of record for the container
image; this makes it the version of record full stop. MinVer's failure mode is
answering plausibly rather than failing, and here a wrong version is a client
that never updates, so it is guarded twice: fetch-depth 0 on every checkout, and
a step that fails a tag build when the tag and the computed version disagree.

**The pack id is DodoSSH.Desktop and not DodoSSH**, which is the one decision
here that would have destroyed data. Velopack installs to %LOCALAPPDATA%\<packId>
and removes that whole directory on uninstall, and %LOCALAPPDATA%\DodoSSH is
where ClientPaths keeps the encrypted cache, the outbox of changes not yet
pushed, and the device key. The obvious id would have had the uninstaller
silently delete work the server has never seen — the thing the application
refuses to do without a counted confirmation. Velopack's own advice to move user
data to roaming %APPDATA% is declined for the reason ClientPaths already gives.

**Releases are cut by a person, and CI gains no job that could.** The tempting
argument is that a forge write token is not a signing key. It does not survive
contact with what the token does: Velopack clients trust their feed and do not
verify a package signature when they apply one, so whoever can write a release
can ship an update every install runs. That is the capability ADR 0011 rule 1
puts on a machine which is not a runner, reached through a different door. The
mechanical objection — vpk needs Windows and the runners are Linux — is the
smaller of the two and is recorded beside it, because somebody will fix one and
believe they are done.

Unsigned for now, deliberately and with the cost stated where a user reads it:
SmartScreen warns once per person, on Setup.exe, because Mark-of-the-Web is
applied by the browser that downloaded it. In-app updates are fetched by the
application and applied from a local file, and never trip it.

The banner is a fourth row of the window rather than an overlay. Anything drawn
in the terminal's rectangle is sliced by the native child window that composites
above it — the defect this window has shipped once — and a sibling row is the
arrangement TitleBar and StatusBar already prove works.

----

Three defects surfaced on the way, none of them in the feature being built.

**A settings key absent from the file came back as the CLR default, not the
declared one.** The JSON source generator builds a record through a synthesised
parameterised constructor and assigns every property from its argument array, so
a property initializer runs and is then overwritten by a default for anything the
file did not contain. A settings.json of {} read back a font size of 0, clamped
up to the 8px floor rather than the 13px the renderer draws at. It could not bite
while there was one setting, because that setting was written on every save and
so was never absent; adding a second would have turned automatic update checks
off for every existing profile, silently, the opposite of the documented default.
Reflection-based deserialisation of the same JSON answers correctly, which is why
every way of checking it by hand agrees except the one that ships. The defaults
now live on the constructor parameters, which is the only place the generator
reads them from.

**Declaring a RuntimeIdentifier on the desktop head broke the server's image
build.** It is the obvious way to let a self-contained publish restore under
locked mode, and it writes a net10.0/win-x64 target into the lock file of every
project the head references transitively — including DodoSSH.Contracts and
DodoSSH.Crypto, which the API builds too. The Dockerfile restores those with no
RID and fails NU1004. Found by running docker build rather than by reading. The
RID stays out of the committed state; the two commands that need one ask for it
unlocked, and the release script puts the lock files back.

**A Docker ARG named VERSION silently sets MSBuild's Version.** An ARG is an
environment variable for the rest of the stage, MSBuild reads environment
variables as properties, and property names are case-insensitive. With the
workflow passing main-<short sha> on a main build the publish died with
NETSDK1018 pointing at DodoSSH.Contracts, a project nobody had touched. The build
stage's argument is ASSEMBLY_VERSION now, empty except on a tag build.

All three are in docs/platform-flags.md, which is where the next person will look.

----

Verified: the whole solution builds and restores locked; 289 shell, 93 layout and
54 session tests pass, including the regression test for the settings defect and
a measurement of the banner at the window's minimum width. vpk pack runs end to
end and reports "Verified VelopackApp.Run()" against Program.Main. The API image
builds correctly both as a main build and as a tag build, carrying 1.0.0 and
0.1.0 respectively.

Not verified, and it needs a published release to be: installing, updating and
uninstalling on a real machine. That is Phase 15 of docs/manual-checks.md, and
the pack id and the WebView2 profile fix are reasoned and commented but only
proved by walking it. Two things to watch at the first upload — the reverse
proxy's body-size limit for a 64 MB asset, and whether vpk upload gitea is happy
with Gitea 1.27.1.

src/DodoSSH.Client.Session/ClientSettings.cs

@@ -19,8 +19,38 @@ namespace DodoSSH.Client.Session;
 /// belongs in the cache, behind the passphrase.
 /// </para>
 /// </remarks>
-public sealed record ClientSettings
+/// <param name="TerminalFontSize">The terminal font size, in CSS pixels.</param>
+/// <param name="AutomaticUpdateChecks">
+/// Whether this machine looks for a newer build on its own. See the remarks on the property.
+/// </param>
+public sealed record ClientSettings(
+    int TerminalFontSize = ClientSettings.DefaultTerminalFontSize,
+    bool AutomaticUpdateChecks = true)
 {
+    /*
+      A positional record, and the defaults live on the parameters rather than on property initializers.
+      That is not a style choice — it is the only place System.Text.Json will read them from, and getting
+      it wrong fails silently.
+
+      What the source generator emits for a record is an ObjectWithParameterizedConstructorCreator: it
+      treats the init-only properties as constructor arguments and builds the object as
+
+          new ClientSettings() { TerminalFontSize = (int)args[0], AutomaticUpdateChecks = (bool)args[1] }
+
+      so a property initializer does run — and is then immediately overwritten by args, which for a member
+      absent from the JSON is the CLR default. Measured before this was fixed: a settings file of {} read
+      back TerminalFontSize 0, clamped to the 8px floor rather than the 13px the renderer draws at, and
+      AutomaticUpdateChecks false. Reflection-based deserialisation of the same JSON answers 13 and true,
+      which is what makes it so easy to miss. Setting GenerationMode to Metadata does not help either; it
+      was tried.
+
+      Constructor parameter defaults are carried into the generated metadata, so absence resolves to the
+      value declared here. ASettingAbsentFromTheFile_ComesBackAsItsDeclaredDefault fails without this.
+
+      The type is still used exactly as before — new ClientSettings(), and `with` expressions — because
+      every parameter is optional.
+    */
+
     /// <summary>The size a terminal draws at with nothing stored.</summary>
     /// <remarks>
     /// Matches the renderer's own default, and has to: the page creates panes at its own constant until
@@ -43,8 +73,34 @@ public sealed record ClientSettings
     /// </remarks>
     public const int MaximumTerminalFontSize = 32;
 
-    /// <summary>The terminal font size, in CSS pixels.</summary>
-    public int TerminalFontSize { get; init; } = DefaultTerminalFontSize;
+    /*
+      AutomaticUpdateChecks: why it is on by default, and the three neighbours it deliberately does not
+      have. Prose rather than XML doc because the property is declared in the parameter list above, and a
+      param tag is the wrong shape for several paragraphs.
+
+      On by default. A client that quietly runs a year behind is the failure ADR 0011 names as the real
+      cost of distributing outside a store, and the desktop has the mechanism to avoid it — so the
+      default should use it. It costs little to leave on, because a check downloads and never installs:
+      nothing happens to a running application except a line offering a restart.
+
+      Three neighbours this deliberately does not have, because each would be a mistake worth
+      naming rather than an omission.
+
+      No feed address. Where builds come from is a constant in the code, and ADR 0011 rule 2 is
+      why: an operator who could point this at themselves could pin a chosen user to a build with a known
+      hole. This file is plaintext and hand-editable, which is exactly what makes it the wrong home for
+      that value.
+
+      No last-checked timestamp. The rule above about nothing secret is not only about secrets —
+      a record of when this machine last contacted the project's forge is a small fact about a person
+      that this file does not otherwise carry. It also buys little: the check runs on a timer measured
+      from launch, so any machine that runs at all is current within hours. What the screen shows is
+      remembered for the session and no longer.
+
+      No channel switch. There is one release channel. A toggle offering a second would be a
+      preference with nothing behind it, which is the thing the preferences screen's own opening comment
+      warns against.
+    */
 
     /// <summary>Brings a value inside the range this type will store.</summary>
     public static int ClampTerminalFontSize(int pixels) =>