chore: release 1.1.0

CHANGELOG.md

@@ -4,6 +4,41 @@ All notable changes to this crate are documented here. The format
 follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
 this project adheres to [Semantic Versioning](https://semver.org/).
 
+## 1.1.0 — 2026-04-22
+
+Spec-only release. No code change in the crate; `PROTOCOL.md`
+normative behavior is amended so `SET_CONFIG` no longer disrupts
+continuous RX.
+
+### Changed
+
+- `PROTOCOL.md` §3.5 ("Operations Spanning Reconfiguration") and
+  §6.3 ("Side effects on `APPLIED`"): a `SET_CONFIG` issued while
+  the radio is in continuous RX now **auto-re-arms RX** with the
+  new parameters once reconfiguration completes. The RX ring is
+  still cleared. The host does **not** need to re-issue `RX_START`
+  after `SET_CONFIG`.
+
+  Rationale: the previous "RX is stopped, re-issue RX_START
+  yourself" rule was hostile to scanner / time-division /
+  dynamic-modulation workflows and violated the principle of least
+  surprise. Scope of the change is strictly additive: hosts that
+  still issue a redundant `RX_START` after `SET_CONFIG` continue
+  to work (firmware replies `OK` with the radio already in
+  Receiving).
+
+- No wire-format, field-layout, or `type_id` changes. The CRC, COBS
+  framing, tag semantics, and every message shape are byte-for-byte
+  identical to 1.0.0.
+
+### Compatibility
+
+- Wire-compatible with 1.0.0 firmware and hosts.
+- Behavior-compatible with 1.0.0 hosts (old-style "always re-issue
+  RX_START" code paths are now no-ops but still correct).
+- New-style hosts that rely on auto-resume **require** firmware
+  `donglora 1.1.0` or later, which implements the new semantics.
+
 ## 1.0.0 — 2026-04-22
 
 The 1.0 wire-format rewrite. Every message shape, tag-correlation

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "donglora-protocol"
-version = "1.0.0"
+version = "1.1.0"
 edition = "2024"
 rust-version = "1.85"
 authors = ["Stephen Waits <steve@waits.net>"]