Files
MeshTerm/tests
Jean-Pierre MartineauandClaude Opus 5.5 d3166170ff A trace to a companion turns at its last relay
A companion, a room server, or a sensor does not relay a trace with the
firmware defaults (allowPacketForward in Mesh.cpp: client repeat is off,
and allowed only on 433.000, 869.495, and 918.000 MHz; disable_fwd is on).
A walk that turned at one of them never came home: the history held 36
companion traces and no reply from a real one.

The route to such a node is the same. Only the walk changes: it turns at
the last relay of the route, and the node is not in the spec. The route
out of a walk that comes home is still the full route to the node, so
the Device route row can offer it for DMs and admin.

- relays_traces() in models states the rule. render_forced_spec takes
  relays=False, and forced_outbound reads the route back from a walk.
- services/trace_plan holds the route choice that the trace screen made
  inline (radio route, outbound paths, best observed, last trace,
  direct), so the CLI uses the same one.
- The trace screen names the relay where the walk turns, in a line under
  the route. With no relay to turn at, Trace is dim. A neighbour that
  does not relay gets "no relays" offered on the Device route row, with
  the packets heard directly as its proof.
- The trace session turns a caller's spec (node page, Message paths) at
  the last relay, so the callers do not need the rule. A sender that is
  not a contact gets its type from its stored adverts.
- The composer and Explore paths turn the walk at the last hop.
- `meshterm trace -t NAME` with no --path walks the menu's route and says
  on stderr where it turns. With no known relay, it is a usage error.
- The connection turns a device-routed trace at the last learned relay.
  The simulator now stops a walk at a node that does not relay, as the
  mesh does, and the tests that walked through Alice walk repeaters.

The picker keeps one list with no mark, sorted as before (JP's choice).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 03:42:56 -05:00
..
2026-10-14 00:18:59 -04:00
2026-10-14 23:08:27 -04:00
2026-10-14 23:21:24 -04:00
2026-10-14 23:08:27 -04:00