BOT_FRAG_LEN was 72, chosen against the longest command name rather than the
longest answer, and it held only because !link had never been asked from
further than two hops away. An 11-hop request wanted 88 chars, so the reply
was cut at 71 -- and it cut off exactly the SNR and RSSI the command exists to
report: "... 209f:34fa:ed9c, SNR 4.0 ".
Two changes, because the size alone would not be enough:
* 100 bytes, sized against the real worst case. botFormatPath() caps the
path at 62 chars (21 hops at 1 B, 12 at 2 B, 9 at 3 B all land just under
BOT_PATH_STR_LEN) and the numbers in front add 36, so 98 + NUL.
* the path goes LAST. It is the only unbounded part of the reply -- and the
SENDER picks the hash width, so this node does not even control how long
it gets. With it at the tail, an overrun eats hops instead of eating the
link budget, and a partial path is still useful where a missing SNR is not.
Both bot envs (Xiao_x1_bot, Xiao_x3_obs) build.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>