Connection Monitor Phase 3: Remote probe / lightweight agent

[itsDNNS]

Summary

Add optional remote measurement capability to the Connection Monitor, allowing latency probes from a specific host in the LAN rather than only from the DOCSight container.

This extends #194 (Phase 1) for users who want measurement from a different network perspective, e.g. a desktop PC, a Raspberry Pi, or a second container.

Use cases

• Measure from a wired LAN client to rule out Wi-Fi issues
• Run probes from a device closer to the modem
• Compare latency from multiple points in the home network

Possible implementations

• Lightweight probe container - small Docker sidecar that reports samples back to DOCSight
• Linux agent - minimal Python/shell script for Raspberry Pi or similar
• Windows helper - small background service or script

Architecture

• Probe agent collects samples locally and pushes to DOCSight via API
• DOCSight stores remote samples alongside local ones, tagged by probe source
• Detail view shows local vs remote probe comparison
• Shared target configuration (push targets to agents, or agents pull config)

Requirements

• Minimal resource footprint on the probe host
• Simple setup (one command or container)
• Secure communication (API token auth)
• Graceful handling of agent disconnects

Depends on

• Add DOCSight-native always-on latency monitor for PingPlotter-style evidence gathering #194 (Phase 1 - merged)
• Traceroute support (Connection Monitor Phase 2: Traceroute burst capture #196) is independent but complementary