bugbot run

@cursor review

Hey, nice feature! Path tracing will be super useful. A few things I noticed while reviewing:

Quick wins

Typo (line 31): _failed2Loaded → _failedToLoad

Trailing space (line 34): Uint8List(0) ; → Uint8List(0);

Misleading variable name (line 81): timeoutSeconds is actually milliseconds (based on the frame format in meshcore_connector.dart). The logic is correct, just the name is confusing:

final timeoutMs = frameBuffer.readUInt32LE();

Simplification

Lines 123-126 - comparing single bytes via listEquals is overkill:

// Current
if (listEquals(
  repeater.publicKey.sublist(0, 1),
  Uint8List.fromList([neighbourData]),
))

// Simpler
if (repeater.publicKey[0] == neighbourData)

Performance (optional)

Lines 119-130 - the nested loop is O(contacts × pathLength). For large meshes this could be optimized with a lookup map:

// Build lookup once
final contactsByFirstByte = <int, Contact>{};
for (final c in connector.contacts.where((c) => c.type != advTypeChat)) {
  contactsByFirstByte[c.publicKey[0]] = c;
}

// Match path
for (final neighbourData in pathData) {
  final contact = contactsByFirstByte[neighbourData];
  if (contact != null) pathContacts[neighbourData] = contact;
}

Question

Lines 196-198 - is the empty onTap handler intentional (future feature) or should it be removed?

onTap: () {
  // Handle item tap
},

Overall looks good! The trace UI with SNR indicators is a nice touch.