mirror of
https://github.com/agessaman/meshcore-bot.git
synced 2026-08-02 00:39:28 +00:00
agessamanandClaude Fable 5
89651b01db
Single-byte repeater identity guessing has been persistently unreliable, and mesh_connections flattens away evidence provenance (confirmed_2byte never persists). observed_paths retains it: bytes_per_hop marks which paths carry unambiguous multi-byte hops. - /api/mesh/edges?evidence=multibyte derives edges purely from unique multi-byte path observations (consecutive hop pairs, aggregated with a distinct-path count); 2-byte edges coalesce into a 3-byte edge only on a unique prefix match, mirroring MeshGraph.add_edge - default mode tags each edge evidence=multibyte|singlebyte by key length - Evidence filter on the mesh page (persisted with the other filters); single-byte edges render dashed in map and graph views, with an evidence line in tooltips and a legend entry - client-side haversine fallback for edges without a stored distance - prefix-compatible edge/node matching so degree sizing and node details work when edge and node prefixes differ in resolution - /api/mesh/stats reports multibyte_edges; shown on the Edges stat card Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>