Ionic Storage and Capacitor Filesystem backup restore verification boundary

Goal is to define a reliable backup and restore process for app data persisted via Ionic Storage using Capacitor Filesystem access to the app sandbox.

Constraints include that Ionic Storage abstracts SQLite on native and IndexedDB on web, with data stored in the app sandbox. Capacitor Filesystem provides read/write access to the data directory for export and import. Ionic Secure Storage keys reside in the platform keychain or keystore and are outside file-system scope. Schema changes between app versions may affect readability of restored database files.

Uncertainty remains about the interoperability boundary between the two components and what verification is meaningful without original values.

What data is covered when the underlying SQLite file is copied via Capacitor Filesystem and later restored?

Does Ionic Storage automatically pick up a restored database file on next launch, or is additional initialization required?

What verification scope is appropriate given Secure Storage keys are not included in file-system backups?