docs(roadmap): drop the AlarmClock route from the Wear OS note

AlarmClock intents only reach apps on the same device and can't read
state, so they are no route for a watch. Cite PRIVACY.md §4 and §5
together and say "no product flavours" precisely.

Refs #27

docs/ROADMAP.md

@@ -621,12 +621,10 @@ Deferred deliberately, in rough priority order:
   blocked on a privacy and distribution decision. A watch that shows and
   controls the phone's timers and next alarm needs a phone-to-watch channel.
   The usual one, Google Play Services' Wearable Data Layer, is a "third-party
-  service" that `docs/PRIVACY.md` §2 rules out, and with one build and no
-  flavours it would also be a non-free dependency in the build F-Droid makes.
-  A channel of our own (Bluetooth, since there is no INTERNET permission)
-  avoids the dependency but adds permissions and a new way for data to leave
-  the phone, which `PRIVACY.md` §5 currently says only crash reports do.
-  Two routes need no channel in Clockula: a third-party watch app can already
-  drive Clockula through the `AlarmClock` intents (ARCHITECTURE §17), and a
-  standalone watch app with its own timers and alarms doesn't touch the phone,
-  though it has no F-Droid route onto a watch.
+  service" that `docs/PRIVACY.md` §2 rules out, and with no product flavours it
+  would also be a non-free dependency in the build F-Droid makes. A channel of
+  our own (Bluetooth, since there is no INTERNET permission) avoids the
+  dependency but needs Bluetooth permissions and is a new way for data to leave
+  the phone, beside Auto Backup and crash reports (`PRIVACY.md` §4 and §5). A
+  standalone watch app with its own timers and alarms avoids all of this but
+  doesn't control the phone.