v1.3.1
Traces & Pings
Single-hop traces are now classified as pings and tagged accordingly. The /traces list response now includes the path and SNR values from the most complete observation of each trace, making it possible to assess signal quality and hop progression at a glance without opening the detail view. A new type query parameter allows filtering traces by TRACE or PING.
Routes
Single-hop routes are no longer stored — direct links are already captured by neighbor relationships, making them redundant.
Nodes
knownNeighborCount added to node summaries, and publicKey added to node neighbor responses.
Database Migrations
Migrations are now embedded in the binary and applied automatically on startup, removing the dependency on external tooling or container entrypoints. Existing deployments will bootstrap cleanly on first run.
Full Changelog: v1.3.0...v1.3.1