code/backend/Cleanuparr.Api/Controllers/EventsController.cs:156

• The /api/events/stats endpoint was removed here, but the Angular frontend still calls it (code/frontend/src/app/core/api/events.api.ts#getEventStats). This will break the UI at runtime unless the frontend is updated in the same PR, or this endpoint is kept for backward compatibility (e.g., reintroduce it and have it delegate to the new stats service / return the previously expected shape).

    /// <summary>
    /// Manually triggers cleanup of old events
    /// </summary>
    [HttpPost("cleanup")]
    public async Task<ActionResult<object>> CleanupOldEvents([FromQuery] int retentionDays = 30)

code/backend/Cleanuparr.Infrastructure/Health/HealthCheckService.cs:216

• In CheckArrInstanceHealthAsync, the exception path returns an ArrHealthStatus with only InstanceId populated; InstanceName and InstanceType will be empty/default. That makes downstream consumers (like /api/stats which serializes Type via InstanceType.ToString()) misleading when a check fails. Consider capturing the instance/config info before the health check call and populating InstanceName/InstanceType even on error.

        catch (Exception ex)
        {
            _logger.LogError(ex, "Error performing health check for arr instance {instanceId}", instanceId);

            var status = new ArrHealthStatus
            {
                InstanceId = instanceId,
                IsHealthy = false,
                LastChecked = DateTime.UtcNow,
                ErrorMessage = $"Error: {ex.Message}"
            };

            UpdateArrHealthStatus(status);
            return status;

docs/docs/configuration/stats/index.mdx:99

• The API response includes a top-level generatedAt field (see StatsResponse.GeneratedAt), but the documentation only describes the events/strikes/jobs/health sections. Please document generatedAt (and ideally show an example of the full top-level response shape) or remove the field if it isn’t intended to be part of the contract.

<SectionTitle icon="📋">Response Reference</SectionTitle>

<ConfigSection
  title="events"
  icon="📝"
>

docs/docs/configuration/stats/index.mdx:70

• The controller clamps hours to 1–720 (Math.Clamp(hours, 1, 720)), so out-of-range values won’t error but will be silently adjusted. The docs currently state a range, but don’t mention the clamping behavior; consider clarifying this to avoid confusing dashboard integrations that accidentally send e.g. hours=0 or hours=999.

**Query Parameters:**

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `hours` | integer | `24` | Timeframe in hours (range: 1–720) |

code/backend/Cleanuparr.Api/Controllers/StatsController.cs:36

• There are no automated tests added for the new stats aggregation behavior (e.g., timeframe filtering, job NextRunAt enrichment, and health serialization). Given the endpoint is intended for external dashboard polling, please add coverage (unit tests for StatsService and/or an API test for GET /api/stats).

    /// <summary>
    /// Gets aggregated application statistics for the specified timeframe
    /// </summary>
    /// <param name="hours">Timeframe in hours (default 24, range 1-720)</param>
    [HttpGet]
    public async Task<IActionResult> GetStats([FromQuery] int hours = 24)
    {
        try
        {
            hours = Math.Clamp(hours, 1, 720);

            var stats = await _statsService.GetStatsAsync(hours);
            return Ok(stats);