Snapshot / Screenshot Testing

Background: Native [platform] app, [SwiftUI / Compose]. Components/screens
I want guarded against visual regressions: [list]. 

Use case: Set up snapshot testing so unintended visual changes fail CI.

Implementation details:
- iOS: a snapshot library (e.g., swift-snapshot-testing) capturing views
  in known states. Android: a screenshot approach (Paparazzi for
  JVM-side Compose render, or an instrumented screenshot tool).
- Capture each component across: light/dark, Dynamic Type/large font, and
  key states (loading/empty/error/loaded)
- A strategy for stable snapshots (fixed data, fixed locale, fixed device
  config) to avoid false diffs
- How references are stored, reviewed, and updated intentionally
- Keeping snapshot count manageable (cover components, not every screen
  permutation)

Deliverable: The snapshot-testing setup, the matrix of states/appearances
to capture per component, the stability rules to prevent flaky diffs, and
the workflow for reviewing and updating reference images.