3 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	0b2fbf13fc	feat(settings): Settings → System shows table sizes and what the last cleanup removed (#5469) ... #5469 "Settings → System: table sizes and what the last cleanup removed". - Storage: each table's size on disk (pg_total_relation_size, indexes and TOAST included) and Postgres's row estimate (reltuples), largest first, the 15 largest by name and the rest summed, under the database's total size. Read from the catalog only, never by counting rows. - Last cleanup: when it ran, how long it took, and what each pass removed (each aged table, run log files, the metric and Docker rollups, the log ring), or "Nothing was past its window". run_cleanup now returns that summary and keeps it as the cleanup.last_run setting, as reports.last_sent_at does; cleanup_secs (#5467) is recorded from the same figure. - A hint links to where each retention window is set. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 14:29:55 -04:00
bvandeusenandClaude Opus 5.5	e98dd10556	fix(ui): a reading's age no longer puts a <time> element inside a title attribute (#5467) ... The `when` filter returns a <time> element, so title="{{ at|when }}" wrote raw markup into the attribute. That broke the hover text, and in the rule form's metric preview (#5475) it leaked a stray `">` into the page. `ago` already carries the exact time as its own tooltip, so both places drop the title. Also fixes #5467's page test, which needed the escaped apostrophe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 14:06:58 -04:00
bvandeusenandClaude Opus 5.5	c8dbe811f8	feat(health): Steward records its own health and Settings → System shows it (#5467) ... #5467 "Steward's own health: metrics, rules can watch them, a page that shows them". The self-monitor tick now records, under source "steward", resource "process": ingest_posts / ingest_failed / ingest_slowest_ms (the host-agent posts since the last tick, tallied in steward/core/health.py), db_roundtrip_ms (a timed SELECT 1), and unwatched_secs (the gap before this tick past watch.GAP_S, from Steward's own last sample). The hourly cleanup records cleanup_secs. The open-file pair is still recorded, and is now only skipped on its own where /proc is absent. All of these are in CORE_METRICS, so an alert rule can watch them under "Steward itself". Settings → System (/settings/system/, admin) shows a verdict first (failed posts, a gap in watching, open files near the limit), then each measure now and over the last day, with a sparkline scaled to its own peak. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 14:02:50 -04:00