fix(analytics): Hash Stats multi-byte adopters column sort reads the wrong column and has no state #226

Relates to #208, #214

Summary

In public/analytics.js (renderMultiByteAdopters, the [data-sort] click handler), colIdx is { name: 0, status: 1, hashSize: 2, packets: 3, lastSeen: 4 }. The table, however, has six columns: Node, Role, Status, Hash Size, Adverts and Last Seen. The Role column and this map were added together in 45623672. As a result:

• Role does nothing.
• Status reads the Role cell, so every row gets weight 2 and the order does not change.
• Hash Size reads the Status text.
• Adverts reads the Hash Size cell.
• Last Seen reads the Adverts cell, as a string.

Even with the right index, Last Seen would compare timeAgo text ("5m ago") as strings. The sort is ascending only, keeps no state or indicator, and is discarded by the next filter click.

Evidence

From the #214 review: on the E2E fixture, clicking Adverts leaves the Adverts column as 2, 1, 1, ….

Proposed fix

• Take the column from the header's cellIndex, or sort on per-cell data-sort-value attributes:
  • a numeric weight for Status;
  • a number for Hash Size and Adverts;
  • an ISO or epoch value for Last Seen.
• Add an asc/desc toggle with aria-sort.
• Deep-link the sort (e.g. mbsort=) only once that state exists, following the feat(analytics): deep-link Scopes sub-tabs and window (#205) #206/fix: P3 follow-ups from the #203/#204/#206 reviews (#208) #214 pattern: no selector read from the URL, and unknown values give the default.

Acceptance criteria

• A unit test per column asserts the order of that column's own cells.
• Last Seen is ordered by timestamp, not by text.
• The filter and mbf= behaviour are unchanged.