db-storage-bloat (M18)

Storage operability keeps a database fast and alive over time; it is a Performance & Scale (axis performance) concern, feeding relational Almacenamiento w12 (shared with M22/M20/M21) and the Tombstones category in the wide-column profile. The catastrophic case — TXID wraparound — can force a Postgres shutdown, so it is a severity:5 cap when imminent.

What it checks

1. VACUUM / autovacuum health — autovacuum disabled or mis-tuned on a high-churn table, dead tuples accumulating, bloated tables/indexes inflating size and slowing scans.
2. TXID wraparound — age(datfrozenxid) (or per-table relfrozenxid) approaching autovacuum_freeze_max_age / the 2-billion ceiling. Imminent wraparound is severity:5, fail (perf) — but only with live age evidence; statically it is at most a needs_api nudge.
3. Tombstones (wide-column) — Cassandra/Scylla heavy deletes / TTL churn producing tombstones that degrade reads (tombstone_warn_threshold territory).

Score / axis