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

Components/Daisy/DataDisplay/DTextRotate.razor

@@ -5,19 +5,16 @@
    duration-* in Class (default 10s). *@
 <span @attributes="AdditionalAttributes" class="@Cx("text-rotate", Class)">
 	<span class="@(Centered ? "justify-items-center" : null)">
-		@if (Items is not null)
+		@foreach (var item in Items.Take(6))
 		{
-			foreach (var item in Items.Take(6))
-			{
-				<span>@item</span>
-			}
+			<span>@item</span>
 		}
 		@ChildContent
 	</span>
 </span>
 
 @code {
-	[Parameter] public IEnumerable<string> Items { get; set; }
+	[Parameter] public IEnumerable<string> Items { get; set; } = [];
 	[Parameter] public RenderFragment ChildContent { get; set; }
 	/// <summary>Centre the lines horizontally.</summary>
 	[Parameter] public bool Centered { get; set; }