docs: Update documentation for 145 files

Generated by AurionDocs
Job ID: c99fff50-67a3-4294-b4df-3e73f4f12de9
Source commit: 4dcb480

docs/auriondocs/Code/src/EchoHub.Server/Config/ServerLogsOptions.cs.md

@@ -0,0 +1,11 @@
+# ServerLogsOptions
+
+> **File:** `src/EchoHub.Server/Config/ServerLogsOptions.cs`  
+> **Kind:** class
+
+```csharp
+public sealed class ServerLogsOptions
+```
+
+
+Live server-log room configuration is encapsulated by this strongly-typed options class. It binds to the ServerLogs config section and supports environment overrides, controlling whether the live streaming channel is created and who can view it. When Enabled is true, a read-only system channel is auto-created and log events are streamed in real time; log lines themselves are not stored as messages in the database, with persistence remaining in the rolling Serilog log files.

docs/auriondocs/Code/src/EchoHub.Server/Config/SpamOptions.cs.md

@@ -0,0 +1,19 @@
+# SpamOptions
+
+> **File:** `src/EchoHub.Server/Config/SpamOptions.cs`  
+> **Kind:** class
+
+```csharp
+public sealed class SpamOptions
+```
+
+
+SpamOptions is a configuration object that encapsulates the anti-spam thresholds used by the server. It is bound from the Spam config section and exposes the toggles and numeric limits that govern how the system enforces per-user rate limits, duplicate message handling, auto-muting behavior, and the protections around first-time channel joins and channel creation. The defaults are intentionally lenient so a fast typist won’t trip them, and moderators (and above) are exempt from these protections. Use this class to adjust spam-protection policy without changing code.
+
+## Remarks
+SpamOptions centralizes policy decisions for anti-spam enforcement, serving as a single source of truth for the thresholds consumed by the spam protection subsystem. By binding to configuration, it keeps rules out of hard-coded logic and enables runtime tuning via the Spam section. The design separates concerns across rate limiting (per-user messages), duplicate detection, auto-mute behavior, and early channel-join/channel-create protections, making it easier to tune each facet without collateral impact. The auto-mute behavior ties into the existing moderation tooling (MuteExpirationService), illustrating cohesive behavior with the broader user-suspension lifecycle. The note about end-to-end encrypted rooms clarifies that identical plaintext can yield different ciphertext, so the duplicate-detection rule may not apply in those contexts.
+
+## Notes
+- Auto-mute is controlled by AutoMuteMinutes. Setting AutoMuteMinutes to 0 disables auto-mute (rejections still apply if thresholds are reached). 
+- MaxMessagesPerWindow and WindowSeconds govern per-user message rate; adjust them with awareness of your typical user pacing to avoid false positives. 
+- MaxJoinsPerWindow and JoinWindowSeconds apply to first-time channel joins; joins to channels the user already belongs to do not count toward the limit, ensuring normal reconnects don’t trigger protections.

docs/auriondocs/Code/src/EchoHub.Server/Config/StatsOptions.cs.md

@@ -0,0 +1,19 @@
+# StatsOptions
+
+> **File:** `src/EchoHub.Server/Config/StatsOptions.cs`  
+> **Kind:** class
+
+```csharp
+public sealed class StatsOptions
+```
+
+
+StatsOptions is a bound configuration object that governs the periodic server-stats reporter. When Enabled is true, a background job periodically snapshots server activity, logs the snapshot as pretty-printed JSON, and persists it to the database; IntervalHours controls cadence, and RetentionDays controls how long reports are kept. The environment override Stats__Enabled allows turning the reporter on or off via environment configuration without changing code.
+
+## Remarks
+StatsOptions serves as a simple, sealed data contract that the configuration system binds to at startup, providing a single source of truth for the reporter settings. Centralizing these knobs here avoids scattering config keys throughout the code and makes it easy to swap configuration providers or add validation in one place. The defaults (Enabled = true, IntervalHours = 6, RetentionDays = 90) define the out-of-the-box behavior and can be overridden by environment or configuration.
+
+## Notes
+- RetentionDays: 0 means keep reports indefinitely; any positive number prunes older entries.
+- IntervalHours is a double; fractional values (e.g., 1.5) are allowed, but scheduling resolution depends on the hosting environment.
+- Enabled acts as the master switch for the background job; disabling it stops snapshots until re-enabled.

docs/auriondocs/Code/src/EchoHub.Server/Config/UploadLimits.cs.md

@@ -0,0 +1,31 @@
+# UploadLimits
+
+> **File:** `src/EchoHub.Server/Config/UploadLimits.cs`  
+> **Kind:** class
+
+```csharp
+public sealed class UploadLimits
+```
+
+
+UploadLimits is a configuration-bound value object that centralizes the admin-defined upload size caps. It reads sizes in megabytes from the Uploads configuration and exposes corresponding byte-sized properties used during enforcement. When the Uploads section is missing or incomplete, the defaults mirror HubConstants to preserve the historical built-in limits.
+
+## Remarks
+UploadLimits centralizes the policy governing uploads (files, images, audio, avatars) and the maximum number of attachments per message. The MB-based properties feed their byte-sized counterparts (MaxFileSizeBytes, MaxImageSizeBytes, etc.) for enforcement. MaxForKind provides a per-kind ceiling, while MaxRequestBodyBytes computes the overall request-body cap (largest file size multiplied by the attachment limit) to ensure configuration changes actually take effect at the HTTP boundary.
+
+## Example
+```csharp
+var limits = new UploadLimits
+{
+    MaxFileSizeMB = 64,
+    MaxAttachmentsPerMessage = 4
+};
+
+long maxImageBytes = limits.MaxImageSizeBytes;
+long imageCeiling = limits.MaxForKind(AttachmentKind.Image);
+long requestBody = limits.MaxRequestBodyBytes;
+```
+
+## Notes
+- Changing MaxAttachmentsPerMessage scales the MaxRequestBodyBytes non-linearly; the request-body cap will constrain multipart uploads even if per-file size increases.
+- Defaults are tied to HubConstants; if those constants change, the default limits change too unless overridden in the Uploads configuration.