feat(ui): per-schedule performance scorecards on Agent Detail (Overview + Schedules tab) (#1115)

[dolho]

Summary

Surfaces per-schedule performance in two schedule-centric places, both from a single compact aggregate (no N per-schedule round-trips):

1. Overview tab — a Schedules performance section comparing every schedule at a glance.
2. Schedules tab — inline mini-stats per schedule row.

Extends #1107 (Overview) and generalises #868 (per-schedule deep analytics, which stays the drill-in target).

Backend

• DB get_agent_schedules_summary(agent, hours) (db/schedules.py): one rollup per non-deleted schedule (zero-run schedules included with zeros). Per schedule — terminal success_rate (success / (success + failed[incl. error]); None → — when zero terminal), NULL-skipping avg_duration_ms, cost_total, context_avg, tool_call_total (parsed over the newest 5,000 rows agent-wide, tool_calls_sampled flag), last-run outcome. Cheap grouped SQL; iso_cutoff window (Invariant #16).
• Router GET /api/agents/{name}/schedules/analytics-summary?window=7d|14d|30d (AuthorizedAgent). Declared before /{schedule_id} in routers/schedules.py so the literal analytics-summary isn't captured as a schedule_id — putting it in analytics.py would be shadowed since schedules_router mounts first (Invariant fix: add missing logging_config.py to backend Dockerfile #4).
• Models ScheduleSummaryRow + AgentSchedulesSummaryResponse (Invariant Add internal health route, without which main didn't start #14).

Frontend (one fetch, two consumers — Invariant #7)

• executions.js fetchSchedulesSummary, cached per ${name}:${window} like fetchAgentAnalytics.
• OverviewPanel: "Schedules performance" section, honors the existing 7/14/30d selector, each row deep-links to the Schedules tab; hidden at zero schedules.
• SchedulesPanel: inline mini-stats per row (success rate, avg duration, runs, last-run dot) — badge style, no new chart/modal.

Verification

• tests/unit/test_1115_schedules_summary.py — 6 tests: terminal success rate (incl. error; non-terminal excluded), NULL-skip avg duration, tool-call total (malformed JSON skipped), zero-run-still-appears (rate=None), soft-delete excluded, out-of-window excluded.
• Full analytics suites green together (feat: per-schedule and per-playbook execution analytics — duration, token, and tool call distributions #868 + feat(ui): Agent Detail Overview dashboard as default tab + Info tab redesign #1107 + feat(ui): per-schedule performance scorecards on Agent Detail (Overview + Schedules tab) #1115 = 30 passed, randomized).
• Frontend production build clean; dev-server HMR clean; components serve 200.
• Endpoint verified live across 7/14/30d on a real busy agent (window filtering correct: 619 runs @7d/14d vs 1580 @30d; terminal success_rate + avg duration coherent); 422 on bad window; /{id} route not shadowed (404 on unknown id).

AC

• Single aggregate call, both surfaces reuse it; no N round-trips
• success rate (terminal, — on zero), token/cost, avg duration, total tool calls
• Read-only / DB-sourced (renders when stopped)
• Zero-run schedule still appears; only non-deleted
• Backend unit test (rollup, success rate, duration avg, tool-call total, empty)
• Overview section labeled by command + name, honors window selector, deep-links, hidden at zero
• Schedules-tab inline stats, compact, same single source

Related to #1115

🤖 Generated with Claude Code

[github-actions]

⚠️ Nightly unit-suite check skipped — merge conflict against dev.

Resolve by running git merge dev locally and pushing the result. The next nightly run will re-test once the conflict is gone.