Fix acks never updating message status, reorder nav

sendText() never assigned a packet id, so it defaulted to 0 and was
sent to the radio as-is. The radio then assigns its own real id on
receipt and echoes that real id back as requestId on the Routing ack
- which never matches the (always-0) id the UI was told to track, so
incoming acks could never be matched to their message and the status
line was stuck on 'Waiting to be acknowledged...' forever, no matter
how many acks actually arrived. Fixed by generating the packet id
client-side before sending, same as sendAdmin() already did correctly.

Nav order is now Peers, Channels, Messages, Map, Config.

Author: claude

index.html

@@ -61,6 +61,14 @@
     <!-- Navigation group -->
     <div class="nav-group">
       <div class="nav-group-title">Navigation</div>
+      <button class="nav-item" id="navBtnPeers" onclick="navigate('peers')">
+        <span class="icon">group</span><span class="nav-item-label">Peers</span>
+        <span class="nav-item-count" id="navPeerCount">0</span>
+      </button>
+      <button class="nav-item" id="tabBtnChannels" onclick="navigate('channels')">
+        <span class="icon">hub</span><span class="nav-item-label">Channels</span>
+        <span class="tab-badge" id="tabBadgeChannels" style="display:none">0</span>
+      </button>
       <button class="nav-item active" id="tabBtnMessages" onclick="navigate('messages')">
         <span class="icon">chat</span><span class="nav-item-label">Messages</span>
         <span class="tab-badge" id="tabBadgeMessages" style="display:none">0</span>
@@ -71,14 +79,6 @@
       <button class="nav-item" id="navBtnConfig" onclick="navigate('config')">
         <span class="icon">settings</span><span class="nav-item-label">Config</span>
       </button>
-      <button class="nav-item" id="tabBtnChannels" onclick="navigate('channels')">
-        <span class="icon">hub</span><span class="nav-item-label">Channels</span>
-        <span class="tab-badge" id="tabBadgeChannels" style="display:none">0</span>
-      </button>
-      <button class="nav-item" id="navBtnPeers" onclick="navigate('peers')">
-        <span class="icon">group</span><span class="nav-item-label">Peers</span>
-        <span class="nav-item-count" id="navPeerCount">0</span>
-      </button>
     </div>
 
     <!-- Bottom rail -->

server/server.js

@@ -282,9 +282,15 @@ async function sendText(text, destNum, channelIndex) {
   if (typeof text !== 'string' || text.length === 0 || text.length > 237) {
     throw new Error('Message must be 1-237 characters (Meshtastic limit)');
   }
-  const mp = create(MeshPacketSchema, { to: destNum ?? 0xFFFFFFFF, channel: channelIndex ?? 0, decoded: { payload: new TextEncoder().encode(text), portnum: PortNum.TEXT_MESSAGE_APP }, wantAck: true, hopLimit: 3 });
+  // The packet id must be assigned here, client-side — leaving it unset defaults
+  // to 0, so the node silently assigns its own real id on receipt. That real id
+  // is what comes back as `requestId` on the Routing ack, which then never
+  // matches the (always-0) id we told the UI to track, so ack status can never
+  // update no matter how many acks actually arrive.
+  const packetId = Math.floor(Math.random() * 0x7ffffffe) + 1;
+  const mp = create(MeshPacketSchema, { id: packetId, to: destNum ?? 0xFFFFFFFF, channel: channelIndex ?? 0, decoded: { payload: new TextEncoder().encode(text), portnum: PortNum.TEXT_MESSAGE_APP }, wantAck: true, hopLimit: 3 });
   await httpPut(`${nodeBaseUrl()}/api/v1/toradio`, toBinary(ToRadioSchema, create(ToRadioSchema, { payloadVariant: { case: 'packet', value: mp } })));
-  return Number(mp.id);
+  return packetId;
 }
 
 async function doConnect(ip, port) {