The companion holds one device route per contact and replaces it with every
path return, good or bad. MeshTerm can now write that route, keep it, and
make the routes follow the user from site to site.
- Device.set_route reads the radio's own record and writes it back with only
the route changed, at the radio's hash width. Device.discover_route sends one
path discovery and returns the route each way. The radio's PATH_UPDATE is a
new hub event, EventKind.ROUTE.
- The outbound store keeps device routes per site and per fixed device (kept),
and the routes a site learned (saved). Keep needs a site or a fixed device.
- services/device_routes.RouteKeeper (ctx.routes): forget, set, keep, unkeep,
discover, and the status the pages show. At each connection and after each
site change it reconciles: routes that start on another site's first hop are
saved for that site and cleared, the new site's saved routes come back, and
kept routes are written back. A silent first hop is skipped. A route change
that the radio pushes gets the kept route written back.
- A site change on the Outbound paths page, its suggestion, and
`meshterm outbound use` go through the reconcile and say what changed.
- New preference auto_route (off): before a DM, set the suggested route when
the radio has none, or one from another site.
Refs: #34
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>