feat(app): optionally push after each change

Changes made in the app could sit unpushed and collide with a later desktop change. The new setting, off by default, pushes after a save, move, rename or delete. It pushes rather than syncs because a rejected push changes nothing, while a pull can stop in a rebase. A failed push only shows a snackbar: the commit stays local and promptOnErrorHandler would delete saved credentials over a missing network.

Autofill saves are left out: AutofillSaveActivity closes right after saving, which would cancel the push. TODO.md tracks that.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 2 insertions, 3 deletions

diff --git a/TODO.md b/TODO.md
index 610fa028..286ffa40 100644
--- a/TODO.md
+++ b/TODO.md
@@ -4,9 +4,8 @@ Open work after 0.2.0. Remove an item in the commit that finishes it.
 
 ## Features and UI
 
-- Push after save: saves, edits, moves and deletes commit locally but do not push, so a change can
-  sit unpushed and collide with a later desktop change (a modify/delete conflict leaves the store
-  in a stopped rebase). Push after each commit, or at least warn about unpushed commits.
+- Push after autofill saves: the "Push after each change" setting skips them, because
+  `AutofillSaveActivity` closes right after saving and would cancel the push.
 - AppCompat out of the APK: `zxing-android-embedded` (`CaptureManager`, `zxing_CaptureTheme`) needs
   it at runtime, so the QR scanner must be replaced. That alone is not enough: `androidx.biometric`
   depends on it too, for a fingerprint dialog unused at minSdk 31, so it must be excluded or