1 Commits (8a8def7d3f6f4aed5aec24ab6f2d6f54e483f77e)

Author	SHA1	Message	Date
Strycher	31f850530b	fix(#115): decode multi-byte path hashes at the device width ... Packet Path mis-identified repeaters: a 2-byte path hash like 6A3D was sliced into two 1-byte hops (6A + 3D), so the first byte collided with an unrelated repeater (Freemasons 6A..) and the second matched nothing ("Unknown Repeater"). - meshcore_protocol: realHopCount() converts the firmware path BYTE length to true hops via the device hash width. - channel_message_path_screen: slice/count/match at the device pathHashByteWidth (not the unreliable per-message high-bits); bucket and match on the full w-byte hash (mirrors _pathMatchesContact), not hash[0]. - channel_chat_screen: same width fix on the per-message via-line + hop badge. - settings: show the build number alongside the version name. - bump 1.1.2-beta.4+36. - test: realHopCount regression coverage. Gemini review (llm-consult): fix-then-ship; 2 findings clarification-only (_formatHash is canonical hex used identically both sides; pathHashByteWidth is static per-connection). Part of epic #112. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago