Merge pull request 'Release v0.31.0 — report parity + the inverted rescue (0.29.0 → 0.31.0)' (#40 ) from dev into main

Reviewed-on: #40
chore(release): v0.31.0 — report parity + the inverted rescue
2026-09-18 16:46:41 -04:00 · 2026-09-18 20:40:48 +00:00 · 2026-09-07 15:57:37 -04:00 · 2026-08-29 15:48:33 -04:00 · 2026-08-28 22:40:34 -04:00 · 2026-08-27 13:43:00 -04:00
4 changed files with 27 additions and 4 deletions
@@ -4,7 +4,30 @@ All notable changes to seismo-relay are documented here.

 ---

-## Unreleased
+## v0.31.0 — 2026-09-18
+
+**Report parity, and a second way to rescue a runaway unit.**  Two threads.
+
+The first closes out Blastware Event/FFT-Report parity: the FFT, the USBM
+RI8507 compliance chart and the sensor self-check now render on the event
+report, reverse-engineered against BE12844 (MiniMate Plus) and UM (Thor)
+events.  The sensor check is decoded for **both** series and standardized into
+the `.h5` (schema **v2**, a new `/sensor_check` group), so SFM serves it
+device-agnostically rather than decoding at report time.  The Inspector — an
+annotated hex reader for series-3 binaries — is what made the trailing-block
+structure findable, and it earned its keep by *ruling out* a stored FFT block
+and proving Blastware computes it from the samples.
+
+The second came out of a field emergency.  BE12599's connector fault drove its
+Tran channel to its trigger level, so the unit recorded back-to-back and dialed
+the office ACH server every ~75 s, unreachable the whole time.
+`bridges/ach_server.py` gained `--stop-monitoring` / `--disable-ach` /
+`--rescue`, which **invert** the recovery: instead of racing a Stop into the
+gaps between dial-outs, point the modem's Destination at our own ACH server and
+answer the call.  Proven in production the same night — the stop landed on the
+first call-in and held.  See `docs/runbooks/wedged_unit_recovery.md`.
+
+⚠ **This release owes prod a backfill** — see Migration below.

 ### Added
 - **Rescue-on-connect for `bridges/ach_server.py`** — `--stop-monitoring`
@@ -2,7 +2,7 @@

 Ground-up Python replacement for **Blastware**, Instantel's Windows-only software for
 managing MiniMate Plus seismographs. Connects over direct RS-232 or cellular modem
-(Sierra Wireless RV50 / RV55). Current version: **v0.30.0**.
+(Sierra Wireless RV50 / RV55). Current version: **v0.31.0**.

 Stack-level context — which repo owns what, and how the three project versions
 pair — lives in `../terra-view/docs/tmi-stack.md`, which is also loaded as
@@ -1,4 +1,4 @@
-# seismo-relay  `v0.30.0`
+# seismo-relay  `v0.31.0`

 A ground-up replacement for **Blastware** — Instantel's aging Windows-only
 software for managing seismographs.  Supports both the **MiniMate Plus
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"

 [project]
 name = "seismo-relay"
-version = "0.30.0"
+version = "0.31.0"
 description = "Python client and REST server for MiniMate Plus seismographs"
 requires-python = ">=3.10"
 dependencies = [
Author	SHA1	Message	Date
serversdown	d2258dad4e	Merge pull request 'Release v0.31.0 — report parity + the inverted rescue (0.29.0 → 0.31.0)' (#40 ) from dev into main Reviewed-on: #40	2026-09-18 16:46:41 -04:00
serversdownandClaude Opus 5	0b58415fe2	chore(release): v0.31.0 — report parity + the inverted rescue Cuts Unreleased to v0.31.0 and writes the theme now that the whole release is visible, per the convention adopted today. Two threads landed. Blastware Event/FFT-Report parity — the FFT, the USBM RI8507 compliance chart, and the sensor self-check decoded for both series and standardized into the .h5 (schema v2, /sensor_check). And the ach_server rescue flags out of the BE12599 field emergency, which invert the wedged-unit recovery: answer the unit's call instead of racing a Stop into the gaps between its dial-outs. Version stamped in pyproject.toml, CLAUDE.md and README.md. TOOL_VERSION was already at 0.31.0 — it came in with the sensor-check work, and it is what makes the backfill pick up the new /sensor_check group without --force. ⚠ This release owes prod a backfill: .h5 schema v1 -> v2, ~2 h on the NAS. Stated in the Migration block. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qcu9ByJfuKBQxmrWb8rSrN	2026-09-18 20:40:48 +00:00
serversdown	e050e602c2	Merge pull request 'Release v0.29.0 — offset detector + false_trigger_reason + BlastMate serials (0.27.0→0.29.0)' (#36 ) from dev into main Reviewed-on: #36	2026-09-07 15:57:37 -04:00
serversdown	fc1c7c7936	Merge pull request 'Docs/claude.md corrections' (#35 ) from dev into main Reviewed-on: #35	2026-08-29 15:48:33 -04:00
serversdown	7d0d12079b	Merge pull request 'v0.27.0 Decoder fixes, offset exploration and testing.' (#34 ) from dev into main Reviewed-on: #34	2026-08-28 22:40:34 -04:00
serversdown	5203aab849	Merge pull request 'update to 0.26.0. Big chonking update including 0.23, 0.24, and 0.25 as well.' (#33 ) from dev into main Reviewed-on: #33	2026-08-27 13:43:00 -04:00
serversdown	5b65718b72	Merge pull request 'v0.23.0 - ZC freq in events store' (#31 ) from dev into main Reviewed-on: #31	2026-08-06 12:12:19 -04:00
serversdown	483762607e	Merge pull request 'Update to v0.22.0' (#30 ) from dev into main Reviewed-on: #30	2026-07-03 15:35:20 -04:00
serversdown	d0b66368d5	Merge pull request 'update to v0.21.1, thor data import successful' (#29 ) from dev into main Reviewed-on: #29	2026-06-01 16:54:23 -04:00
serversdown	2eb1d25028	Merge pull request 'v0.20.0 -- Full s3 event parse and PDF creation.' (#28 ) from dev into main Reviewed-on: #28	2026-05-28 17:54:31 -04:00
claude	cc821f9ee3	hotfix: fix dockerfile on main to fix import bug on prod	2026-05-21 20:42:15 +00:00