Merge remote-tracking branch 'origin/release/v1.0.0' into feat/caldav-sync

# Conflicts:
#	app/build.gradle.kts
#	app/src/main/java/de/jeanlucmakiola/agendula/data/di/DataModule.kt
#	app/src/main/java/de/jeanlucmakiola/agendula/data/di/Qualifiers.kt
#	app/src/main/java/de/jeanlucmakiola/agendula/ui/export/ExportScreen.kt
#	app/src/main/java/de/jeanlucmakiola/agendula/ui/settings/SettingsScreen.kt
#	docs/PRIVACY.md
#	gradle/libs.versions.toml

README.md

@@ -38,6 +38,12 @@ apps, so there is no authority to clash over and no permission to grant. It
 the other, and if you already sync through a provider, that keeps working exactly
 as it did.
 
+Switching between the two moves nothing — each store keeps its own tasks — so
+Settings → Storage asks before it switches, and offers to **copy** a provider's
+tasks into Agendula's own store when you want to move over. The copy is taken
+once and the originals stay where they are; it is not an ongoing sync in either
+direction.
+
 Recurring tasks are expanded per RFC 5545, and everything the schema does not
 model is round-tripped verbatim rather than dropped — so passing your tasks
 through Agendula does not quietly lose fields a server sent.