House rules: numbers through one formatter, no made-up server errors, and the rules fail the build

- Every number shown on a page goes through NumbersExtensions: counts,
  percentages, the nerd readouts and the values written into a style.
- A failure the client builds itself (offline, timeout, retries run out, an
  answer it can't read) is a 400 that names its kind; only a server's own 5XX
  passes through.
- Login, sign-up, recovery and password confirmations leave autocomplete to
  the browser, so it can offer the saved login.
- The Daisy components start with empty lists and attributes, and a
  decorative image still renders alt="".
- Arasaka.HouseRules.Analyzers checks all of this in every build, together
  with PrivaPub.ClientModels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01W4YtEJrgxG12Pc39Fai8Bd

Pages/Login.razor

@@ -60,13 +60,13 @@
 
 						<label class="flex flex-col gap-1">
 							<span class="text-sm">@Localizer["Username"]</span>
-							<DInput TValue="string" class="w-full" @bind-Value="form.UserName" autocomplete="username" autocapitalize="none" spellcheck="false">
+							<DInput TValue="string" class="w-full" @bind-Value="form.UserName" autocapitalize="none" spellcheck="false">
 								<Prefix><i class="ion-md-person"></i></Prefix>
 							</DInput>
 						</label>
 						<label class="flex flex-col gap-1">
 							<span class="text-sm">@Localizer["Password"]</span>
-							<DInput TValue="string" Type="password" class="w-full" @bind-Value="form.Password" autocomplete="current-password">
+							<DInput TValue="string" Type="password" class="w-full" @bind-Value="form.Password">
 								<Prefix><i class="ion-md-key"></i></Prefix>
 							</DInput>
 						</label>