Extend mesh node staleness window from 10 min to 72 h

[d3mocide]

Problem

Active mesh nodes — including the primary repeater that feeds the observer node — were rendering grey on the map with a STALE / OFFLINE tooltip despite being live.

A mesh node's last_seen is its last advert timestamp, and MeshCore nodes typically advert only once every 24–48 h. But buildMeshNodeLayer.ts flagged any node whose last advert was older than 10 minutes as stale (STALE_MS = 10 * 60 * 1000). So virtually every healthy-but-quiet node tripped the gate.

Note this threshold does not control map presence — nodes stay visible as long as the MeshCore repeater still lists them (the poller re-publishes the contact table every 60 s, refreshing the 120 s Redis TTL). It only drives the grey icon color and the tooltip label.

Change

• frontend/src/config.ts — new MESH_NODE_STALE_MS, default 72 h, overridable via VITE_MESH_NODE_STALE_HOURS. 72 h means a node is only marked stale after missing roughly two advert cycles.
• frontend/src/layers/buildMeshNodeLayer.ts — replace the hardcoded 10-minute constant with the shared config value. Both the grey/active icon color and the STALE / OFFLINE vs ACTIVE / ONLINE tooltip read the same picked object (MeshNodePoint.stale), so both update from this single source.
• .env.example — document VITE_MESH_NODE_STALE_HOURS=72.

Validation

• npx tsc --noEmit passes.

🤖 Generated with Claude Code

---

Generated by Claude Code