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/Services/Stats/ServerStatsCollector.cs.md

@@ -0,0 +1,75 @@
+# ServerStatsCollector.cs
+
+> **Source:** `src/EchoHub.Server/Services/Stats/ServerStatsCollector.cs`
+
+## Contents
+
+- [ServerStatsCollector](#serverstatscollector)
+- [StatsCounters](#statscounters)
+
+---
+
+## ServerStatsCollector
+> **File:** `src/EchoHub.Server/Services/Stats/ServerStatsCollector.cs`  
+> **Kind:** class
+
+```csharp
+public sealed class ServerStatsCollector
+```
+
+
+ServerStatsCollector is a thread-safe, in-memory accumulator for server activity counters that have no natural database timestamp (connections, disconnections, kicks, bans, and peak concurrency). It updates counters via lock-free increments and uses a periodic SnapshotAndReset to emit a windowed StatsCounters and prepare the next window, including resetting the peak to the current online count.
+
+## Remarks
+
+Because it is registered as a singleton, multiple threads can record events without blocking. The class uses Interlocked and Volatile to implement a lock-free maximum-tracking algorithm for PeakOnline; SnapshotAndReset atomically drains all counters and resets PeakOnline to the provided onlineNow, which defines the starting point for the next window. This design favors low-latency updates in hot paths while deferring aggregation to the reporting window.
+
+## Notes
+
+- The next window's PeakOnline baseline is reset to the supplied onlineNow; if that baseline is lower than the actual concurrency at snapshot time, the subsequent peak may undercount.
+- SnapshotAndReset resets the per-window counters to zero (except PeakOnline, which is reset to onlineNow); ensure you call it on the cadence that matches your reporting window to align with dashboards.
+
+---
+
+## StatsCounters
+> **File:** `src/EchoHub.Server/Services/Stats/ServerStatsCollector.cs`  
+> **Kind:** record
+
+```csharp
+public readonly record struct StatsCounters(
+    long Connections,
+    long Disconnections,
+    long Kicks,
+    long Bans,
+    int PeakOnline)
+```
+
+**Parameters:**
+
+| Parameter | Type | Default |
+|-----------|------|---------|
+| `Connections` | `long` | — |
+| `Disconnections` | `long` | — |
+| `Kicks` | `long` | — |
+| `Bans` | `long` | — |
+| `PeakOnline` | `int` | — |
+
+
+StatsCounters is an immutable snapshot of the counters held by ServerStatsCollector. It captures the total connections, disconnections, kicks, bans, and the peak online count at a single moment, enabling safe sharing and logging without mutating the underlying counters.
+
+## Remarks
+StatCounters uses a readonly record struct to provide value semantics, meaning two instances with the same values compare equal and it can be passed by value without side effects. It is intended to be produced by the ServerStatsCollector and consumed by telemetry, dashboards, or loggers that need a stable view of current activity. Because it is immutable, readers can snapshot and transport it across threads without additional synchronization concerns.
+
+## Example
+```csharp
+// Create a snapshot of current counters
+var snapshot = new StatsCounters(Connections: 1024, Disconnections: 64, Kicks: 3, Bans: 0, PeakOnline: 128);
+
+// Deconstruct to access individual values
+var (connections, disconnections, kicks, bans, peakOnline) = snapshot;
+```
+
+## Dependencies
+- ServerStatsCollector
+
+---

docs/auriondocs/Code/src/EchoHub.Server/Services/Stats/ServerStatsReportService.cs.md

@@ -0,0 +1,19 @@
+# ServerStatsReportService
+
+> **File:** `src/EchoHub.Server/Services/Stats/ServerStatsReportService.cs`  
+> **Kind:** class
+
+```csharp
+public sealed class ServerStatsReportService : BackgroundService
+```
+
+
+ServerStatsReportService is a background task that periodically snapshots server activity over the current reporting window, logs the snapshot as pretty-printed JSON (visible in the live server-logs room), and persists a ServerStatsReport to the database for historical trend analysis. The cadence and retention are controlled by StatsOptions; if IntervalHours is non-positive the service uses a 6-hour default.
+
+## Remarks
+To achieve this, the service reads the online user count from PresenceTracker, captures in-memory statistics from ServerStatsCollector, and then opens a scoped EchoHubDbContext to compute metrics such as messages sent, active members, files uploaded, and new users within the reporting window. A fresh DI scope is created per report to ensure proper EF Core lifetimes and isolation between reports. The reporting window is defined by _periodStart and periodEnd to align live counters with database-derived metrics, ensuring the report reflects the same time span across in-memory and persisted data. The pretty-printed JSON log enhances operational visibility by surfacing structured data in the logs.
+
+## Notes
+- The background loop honors cancellation by awaiting Task.Delay with the provided CancellationToken and catching OperationCanceledException to exit promptly.
+- IntervalHours is validated: non-positive values fall back to 6 hours, and the interval is floored at 1 second to avoid a spinning loop.
+- Each report uses its own DbContext scope (via _scopeFactory.CreateScope()) to query the database and persist the resulting ServerStatsReport, ensuring clean lifetimes and minimal cross-report contention.