1 Commits (2f1048e7be8250b8ac74af44c1a016d95dc59f36)

Author	SHA1	Message	Date
Strycher	2f1048e7be	fix(#495): send routed paths at the contact's width, not width 1 ... resolvePathSelection returned no width and, on the override branch, a byte count in place of a hop count. preparePathForContactSend then called setContactPath without a width, so encodePathLen packed mode bits 00 and a 2-byte route went out as twice as many 1-byte hops (path_len 0x06 for a 6-hop 2-byte route instead of 0x46). The radio routed on wrong 1-byte prefixes, confirmed on Bandit's 2026-08-01 log and via CoreScope. Direct and flood were immune because neither uses the path bytes. PathSelection now carries hashWidth and a true hop count on every branch, using the contact's pathHashWidth as the single width authority. Both setContactPath call sites thread it. Also addresses the override timeout inflation half of #299 (hopCount was a byte count feeding calculateTimeout). Gemini review found two override/history width edge cases -> split to #494. Refs #299 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2 months ago