docs(roadmap): rewrap the Wear OS note

Refs #27

docs/ROADMAP.md

@@ -617,13 +617,14 @@ Deferred deliberately, in rough priority order:
   notification surface is known (`PLAN.md` §3).
 - **Migrate Calendula and Agendula onto `core-prefs` + `core-di`**: tracked in
   the kit's roadmap, not here.
-- **Wear OS companion** ([#27](https://codeberg.org/jlmakiola/clockula/issues/27)):
-  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 `PRIVACY.md` §2 rules out, and with no product flavours it
-  would be in every APK, so F-Droid would refuse or flag the app. Any channel
-  of our own would need new permissions (`PRIVACY.md` §7) and would be a new
-  data path: §5 calls crash reports the only one, and §4 covers Auto Backup. A standalone watch app
-  with its own timers and alarms needs neither, but doesn't control the phone
-  and has no F-Droid route onto a watch.
+- **Wear OS companion**
+  ([#27](https://codeberg.org/jlmakiola/clockula/issues/27)): 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
+  `PRIVACY.md` §2 rules out, and with no product flavours it would be in every
+  APK, so official F-Droid would refuse to build it. Any channel of our own
+  would need new permissions (`PRIVACY.md` §7) and would be a new data path: §5
+  calls crash reports the only one, and §4 covers Auto Backup. A standalone
+  watch app with its own timers and alarms needs neither, but doesn't control
+  the phone and has no F-Droid route onto a watch.