feat(route): Discover - path discovery from the device, 1/3/5 tries 20 s apart, the routes found to use in the route editor

MyMesh::sendPathDiscovery() shares the request with the app's
CMD_SEND_PATH_DISCOVERY_REQ and hands the reply (the way there and back)
to the UI; PathEditor keeps up to 4 distinct routes with how often each
came. L2: Find the route under Route; L1: Discover row in Path / trace.
Docs: Discover, message routes on the map, Ask status and discovery.

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

docs/solo/contacts.md

@@ -87,6 +87,23 @@ With no reply, **Find break** traces to the first repeater, then the second,
 and so on, and shows where it stops. If every repeater answers, the node
 itself didn't.
 
+**Discover** finds the route for you. It asks the node by flood, and the
+reply says which repeaters the flood went through to reach it, and which the
+reply took back. These come from the mesh itself, not from anyone's position
+on the map. On the **Discover** row, **Left / Right** sets 1, 3 or 5 tries
+and **Enter** starts it (or stops it). Each try waits for its reply or its
+timeout, then 20 seconds more, so the floods don't come all at once. Each
+route found is listed under it with how many times it came; **Enter** on one
+puts it in the list, ready to **Trace** and save. A repeater you don't have
+as a contact shows as its hash (`?8D`). Nothing is saved until you save it.
+
+Only a node that answers requests can be asked: a companion whose
+Settings › Privacy › **Ask status** lets you (**Everyone**, or **Allowed**
+with Telem given to you), or a repeater or room you're logged in to (a guest
+login is enough). Your own Ask status decides the same for others finding a
+route to you. Not to be confused with **Discover scan** in the node options,
+which looks for nodes in direct range.
+
 **Save path** makes the list the contact's route; saved empty, messages go
 straight to the node. The route a node sends back usually replaces it again;
 **Keep path** stops that, and keeps the route after failed sends too.
@@ -99,6 +116,10 @@ straight to the node. The route a node sends back usually replaces it again;
 > the node to trace to it or stop at the last repeater. **Keep** is in the
 > header, **Find where** appears next to a "No reply". The repeaters can also
 > be tapped on the map, in order (**Map**); **Undo** takes the last one out.
+> **Discover** is under the route, in **Find the route**, with the number of
+> tries beside it and where it is (the try waiting for its reply, or the
+> seconds to the next one). Tap a route found to use it; the way back is under
+> it.
 
 ## Your own contact
 

docs/solo/messages.md

@@ -30,10 +30,20 @@ older and newer one.
   contains a location (see [Navigation](./navigation.md)).
 - **Path** on a received message: the repeaters it came through.
   **Relayed by** on your own channel post: the repeaters heard repeating it.
+- **Show route**: when the message has a route written in it, such as a
+  bot's `!path` reply (`3f:a1:c8`, see [Remote bot](./tools.md#remote-bot)).
+  It draws the route on a small map: you, each repeater numbered in order,
+  and the sender, with how many of the hops could be placed (a repeater
+  needs a position). In a direct message the route starts from you, because
+  it's the way your message went; on a channel it's someone else's, so it
+  doesn't. **Back** closes it.
 
 > [!NOTE]
 > **Wio Tracker L2:** hold a bubble. The card shows when it was sent, the hop
-> count, the path as a diagram, and **Reply** / **Set target**.
+> count, the path as a diagram, and **Reply** / **Set target**, plus **Route**
+> when the message has a route in it: the nodes map opens with the route drawn
+> and its hops numbered, and the names along the bottom; **Done** goes back to
+> the conversation.
 
 ### How much is kept
 

docs/solo/settings.md

@@ -68,7 +68,10 @@ nodes aren't added until you make room.
   **Allowed** (the contacts you gave that permission: **Telem** in a node's
   options in [Nodes](./contacts.md#nearby-nodes), or the phone app) or
   **Everyone**. Status is the battery; a request for location or
-  sensors is answered only where status is allowed too.
+  sensors is answered only where status is allowed too. Status also lets
+  others find a route to you (**Discover** in
+  [Path and trace](./contacts.md#path-and-trace), or the phone app's path
+  discovery).
 - **BT PIN**: the six-digit Bluetooth pairing PIN. Leave it empty for a new
   random one at each start, shown on screen. A new PIN is used from the next
   start; the phone pairs again after that.