docs(cli,readme): broaden scope to all Thytronic relays + add Compatibility/License (#26)

Replace the informal "talks to PROX/PRON/XMR the way ThyVisor does,
but smarter" tagline with a neutral one-liner. Empirical scan of all
847 vendor templates confirms IDENTIFICATION=num=5183 is universal
across families (not PROX/PRON/XMR-specific as the connection.go
comment claimed); broaden that comment too. README opens generically,
adds a Compatibility section declaring only XV10P/NV10P as tested
and inviting issues for other families, and a License section that
points at the MIT LICENSE, restates the as-is disclaimer, and notes
non-affiliation with Thytronic.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ale-rinaldi

README.md

@@ -2,12 +2,12 @@
 
 ![mythy logo](logo.png)
 
-A command-line client for **Thytronic** protection relays (XV10P, NV10P,
-NA10, …). `mythy` speaks the same wire protocol as the vendor's ThyVisor
-Windows app — Modbus TCP and Modbus RTU — so you can identify a device,
-browse its parameter catalog, read measurements, change settings,
-snapshot configurations to YAML, and invoke device commands without
-leaving the terminal.
+A command-line client for **Thytronic** protection relays. `mythy`
+speaks the same wire protocol as the vendor's ThyVisor Windows app —
+Modbus TCP and Modbus RTU — so you can identify a device, browse its
+parameter catalog, read measurements, change settings, snapshot
+configurations to YAML, and invoke device commands without leaving
+the terminal.
 
 ## What it does
 
@@ -24,6 +24,27 @@ leaving the terminal.
 | Transports | Modbus TCP (default port 502) and Modbus RTU on serial / USB-CDC |
 | Safety rails | `--force` gate on destructive operations; client-side validation (RANGE bounds, ENUM membership, STRING length) before any write |
 
+## Compatibility
+
+Thytronic relay templates share the same on-the-wire data layout
+across families: every product in the vendor's `Codifica.xml`
+exposes its parameter catalog through the same `<message>` /
+`<part>` / `<TIPO>` schema, and the IDENTIFICATION register lives
+at the same Modbus address on every family that declares it. In
+principle `mythy` should work against any device the vendor
+catalog covers.
+
+In practice it has been exercised end-to-end only on the two
+devices we have on hand:
+
+- **XV10P** (PROX family)
+- **NV10P** (PRON family)
+
+Other products (NA10, XMR, DMC*, SME*, CCI, NTG, iBU, …) are
+expected to work but are **untested**. If you try one and hit a
+mismatch, please open an issue with the device's `identify`
+output and a description of what failed.
+
 ## Getting started
 
 ### 1. Install mythy
@@ -350,3 +371,12 @@ pkg/session/    High-level API: Connect, Identify, Read, Set, Command, …
 pkg/configio/   YAML export / import / diff / apply
 testdata/       Synthetic catalog fixture for tests
 ```
+
+## License
+
+Released under the MIT License — see [LICENSE](LICENSE) for the
+full text. `mythy` is provided **as-is**, without warranty of any
+kind: you are responsible for verifying its behavior before using
+it against production relays. The authors are not affiliated with
+Thytronic; "Thytronic", "ThyVisor", and product names are
+trademarks of their respective owners.

cmd/mythy/connection.go

@@ -119,9 +119,9 @@ func (c *connFlags) build(ctx context.Context, cf *catalogFlags) (*session.Sessi
 	} else {
 		// Look up IDENTIFICATION's wire address from the catalog instead
 		// of hardcoding 0x143E (audit I11). We need a template for that
-		// lookup, which we don't have yet — but every PROX/PRON/XMR
-		// template puts IDENTIFICATION at num=5183, and that's the only
-		// register guaranteed at a fixed address across families. So
+		// lookup, which we don't have yet — but every Thytronic relay
+		// template that declares IDENTIFICATION puts it at num=5183
+		// (empirically verified across the full vendor catalog), so
 		// hardcoding 0x143E here is structurally fine; this comment
 		// records the deliberate choice.
 		regs, err := t.ReadInputRegisters(ctx, 0x143E, 5)

cmd/mythy/main.go

@@ -20,7 +20,7 @@ func newRootCmd() *cobra.Command {
 	root := &cobra.Command{
 		Use:     "mythy",
 		Short:   "CLI for Thytronic protection relays",
-		Long:    "mythy talks to Thytronic Pro-X / Pro-N / XMR protection relays the way ThyVisor does, but smarter.",
+		Long:    "Command-line tool to configure, monitor, and manage Thytronic protection relays.",
 		Version: strings.TrimPrefix(version, "v"),
 	}
 	cf := &catalogFlags{}