meshsat 1.0.3

meshsat 1.0.3: an SOS on every route that is set up

• An SOS takes every route that is set up, as MeshSat Android does, not only the routes up that minute. A satellite modem this phone has had, a node it paired that is reconnecting, and the Hub while it is offline all count. A leg on a route that is down waits in the Bridge's queue and goes out when the route is back, and it keeps trying until you cancel. The SOS screen shows each leg as "Waiting to send" until it goes, then "Sent", or "Sent, and the Hub has it".
• The Bridge carries the legs (Bridge change MESHSAT-1447, carried in this package):
  • the text on the mesh;
  • the SOS frame by satellite, on whichever modem the phone or kit has (the 9704 as well);
  • the Hub told over the internet, under the same alert id as the satellite frame, so the Hub pages once.
    A cancelled SOS never goes out on a route it had not reached yet. The mesh and the Hub are told it is over. The SOS survives a restart of the Bridge.
• A blank SOS name takes the Hub callsign, as on Android: in the SOS, in the alarm test and in the cancellation. Safety's name field shows the callsign as its placeholder; "A MeshSat user" only without one.
• Tested: 424 unit tests. On the bench phone, the whole suite against the installed package: 221 cases (197 against a scripted Bridge, 17 against a second, real Bridge, 7 live). 218 passed. The 3 that failed were test expectations that the new rule made wrong: a modem the phone had seen earlier in a module now counts as a route. They were fixed, and their modules (16 cases) reran with all passed. The live alarm test's text was heard by the T-Deck. No real SOS has ever been sent; the Bridge's legs are proven in its Go tests and against the scripted Bridge.

Install on a Mobian phone: wget https://github.com/meshsat/meshsat-linux/releases/download/v1.0.3/meshsat_1.0.3_arm64.deb && sudo apt install ./meshsat_1.0.3_arm64.deb (docs/INSTALL.md).