Files
meshcore-analyzer/cmd/server
dborupandClaude Sonnet 5 8144b46136 feat: CoreScope-only "ping" bot reply in Channels view
A channel message whose text is exactly "ping" (mention-prefix like
"@MeshviewBot ping" stripped first) now gets a synthesized "pong" reply
showing hop count, SNR, and hearing observer -- computed at read time
from that message's own already-stored data, no new table.

Deliberately NOT transmitted back onto the mesh: CoreScope has no publish
path to a MeshCore broker/radio (confirmed: it only ever subscribes to
MQTT, never publishes). The reply is visible only in CoreScope's own
Channels view, rendered as a visually distinct dashed-border bubble with
an explicit "Not sent to the mesh" caveat so it's never mistaken for a
real bot reply the sender's own radio received.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 13:47:28 +02:00
..