Greptile Summary

This PR adds per-platform metadata coverage and region breakdown statistics to the server stats page, alongside a visual redesign of the platform cards (tabular detail layout, size bar, expandable region chips). The backend adds two efficient queries — a single GROUP BY for metadata counts and Python-side region aggregation — and the frontend consumes them via new props passed through the stats view.

Key changes and observations:

• Backend: _METADATA_SOURCE_COLUMNS is correctly placed at module scope. get_metadata_coverage_by_platform uses a single efficient GROUP BY query. get_region_breakdown_by_platform does Python-side aggregation (acknowledged tradeoff for DB-dialect agnosticism, flagged in previous review threads).
• Python type annotation mismatch: StatsReturn declares dict[int, ...] for the new fields, but JSON always serializes object keys as strings; the TypeScript side correctly uses Record<string, ...>. This is a minor annotation misleadingness already raised in prior review threads.
• Frontend — store mutation fix: The prior allPlatforms.value.sort() mutation bug is now correctly fixed with [...allPlatforms.value].sort(...) spread copies.
• orderedCoverageByPlatform computed: The double-call pattern previously flagged for metadata coverage has been resolved; however, getVisibleRegions(platform.id) is still called twice per platform in the template (once for v-if, once for v-for), representing the same pattern for regions.
• i18n: The "Games" row label uses t("setup.games") — a key from the setup wizard namespace — rather than a dedicated common.games entry. CSS uppercasing masks the mismatch today, but the borrowing is fragile.
• Locale files: platforms-size is correctly removed from all 15 locale files. No new translation keys were added, as the new labels reuse existing keys from rom, platform, and setup namespaces.

Confidence Score: 4/5

• This PR is safe to merge; the changes are additive, well-scoped, and the most significant previously flagged issues have been addressed.
• The backend queries are efficient and correct. The frontend fixes the prior store-mutation and double-sort bugs. Remaining issues are minor style/performance concerns (double getVisibleRegions call, borrowed i18n namespace) that do not affect correctness or user-facing functionality.
• frontend/src/components/Settings/ServerStats/PlatformsStats.vue — the getVisibleRegions double call and the setup.games namespace borrowing are both minor but worth a quick look before merge.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Browser
    participant ServerStats.vue
    participant PlatformsStats.vue
    participant StatsAPI as GET /stats
    participant DBStatsHandler
    participant DB as Database (Rom table)

    Browser->>ServerStats.vue: onBeforeMount
    ServerStats.vue->>StatsAPI: api.get("/stats")
    StatsAPI->>DBStatsHandler: get_metadata_coverage_by_platform()
    DBStatsHandler->>DB: SELECT platform_id, COUNT(igdb_id), COUNT(ss_id), ... GROUP BY platform_id
    DB-->>DBStatsHandler: rows[]
    DBStatsHandler-->>StatsAPI: dict[int, list[MetadataCoverageItem]]

    StatsAPI->>DBStatsHandler: get_region_breakdown_by_platform()
    DBStatsHandler->>DB: SELECT platform_id, regions WHERE regions IS NOT NULL
    DB-->>DBStatsHandler: rows[]
    Note over DBStatsHandler: Python-side aggregation per region per platform
    DBStatsHandler-->>StatsAPI: dict[int, list[RegionBreakdownItem]]

    StatsAPI-->>ServerStats.vue: StatsReturn (JSON, int keys serialized as strings)
    ServerStats.vue->>PlatformsStats.vue: :metadata-coverage="stats.METADATA_COVERAGE"
    ServerStats.vue->>PlatformsStats.vue: :region-breakdown="stats.REGION_BREAKDOWN"
    Note over PlatformsStats.vue: orderedCoverageByPlatform computed<br/>sorts by SCAN_METADATA_PRIORITY
    PlatformsStats.vue-->>Browser: Render platform cards with coverage chips + region chips

_{Last reviewed commit: f8a9740}

i18n should be fixed 🤞