House rules 1.1.0, and the docs say why refusals keep their reason codes instead of numbered errors

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

PATTERNS.md

@@ -50,7 +50,12 @@ MeWeb builds with none and carries no suppression. Applied to MeWeb:
   - `NumbersExtensions` holds the invariant values that fill a localized template: `ToOneDecimal`, `ToWholeMegabytes`.
   - `Texts` holds what the App formats in the reader's culture: money and dates.
 - **JSON:** one source-generated context per assembly (#84).
-- **Not applicable:** the `.razor` rules (HR0101–HR0106, HR0201), since the App is Avalonia. Their counterparts are
+- **Error codes** (HR0012, HR0013) are not turned on: a refusal already carries a stable machine code,
+  `ViewRefusal.Reason` (`too-many`, `busy`, `bad-ports`…), which installed apps read and translate. A numbered prefix
+  would change what they receive.
+- **Spreadsheets** (HR0319): none; findings are shown in the app and shared as the submission JSON the person reads.
+- **Not applicable:** passwords (HR0311), since there are no accounts.
+- **Not applicable:** the `.razor` rules (HR0101–HR0108, HR0201), since the App is Avalonia. Their counterparts are
   #27, #43, #44 and #93. `Localizer.Instance[key]` already returns a string (#91).
 
 ---