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/Join.razor

@@ -29,13 +29,13 @@
 					<DInput TValue="string" class="w-full font-mono text-xs" @bind-Value="form.InvitationCode" autocomplete="off" autocapitalize="none" spellcheck="false"
 							maxlength="@PrivaPub.ClientModels.Constants.GroupInvitationLength" data-join-code />
 				</label>
-				<DInput TValue="string" Type="password" class="w-full" @bind-Value="form.InvitationPassword" autocomplete="off"
+				<DInput TValue="string" Type="password" class="w-full" @bind-Value="form.InvitationPassword"
 						placeholder="@Localizer["Invitation password, if it has one"]" data-join-code-password />
 
 				<b class="text-sm">@Localizer["Your login"]</b>
 				<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" data-join-username>
+					<DInput TValue="string" class="w-full" @bind-Value="form.UserName" autocapitalize="none" spellcheck="false" data-join-username>
 						<Prefix><i class="ion-md-person"></i></Prefix>
 					</DInput>
 				</label>