[0.1] Further backports and draft release notes

[TheBlueMatt]

Backports #4667, #4684, #4697, #4707, and #4709. Did not include #4673 as its not as trivial and I'm not really sure UTXO lokup implementors should ever return a dup result.

[ldk-reviews-bot]

I've assigned @wpaulino as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[ldk-claude-review-bot]

I've already reviewed this PR in a prior pass and verified all the core fixes. The diff is unchanged — the production code changes (payment.rs:525 checked_sub, channelmanager.rs [2; 33] pubkey, lib.rs Ok(None), offer.rs quantity check, channel.rs monitor_pending_revoke_and_ack clearing) are all correct, and the remaining additions are tests and CHANGELOG notes.

No issues found.

[tnull]

Reviewed release notes, LGTM

[TheBlueMatt]

Updated release notes with feedback incl from #4706:

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4d259c7a23..5fb5c9b157 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,3 +9,4 @@
    payers rely on today (#4647).
- * Explicit `amount_msats` of 0 is rejected in BOLT 12 `OfferBuilder` (#4324).
+ * Explicit `amount_msats` of 0 is rejected in `Bolt12Offer`s, `OfferBuidler`
+   now maps 0-amounts to an amount of `None` (#4324).

@@ -20,3 +21,4 @@
    could have become stuck (#4520).
- * The electrum sync client now properly skips unconfirmed transactions (#4590).
+ * The presence of unconfirmed transactions actually no longer causes
+   `ElectrumSyncClient` to spuriously fail to sync (#4590).
  * `FilesystemStore::list_all_keys` will no longer fail if there are stale

[TheBlueMatt]

Fixed a typo and named the release:

$ git diff-tree -U1 e2c8d21de 5cac547d1
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5fb5c9b157..a6fd5bfb18 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,2 +1,2 @@
-# 0.1.10 - XXX - "XXX"
+# 0.1.10 - Jun 18, 2026 - "An Older Loupe"

@@ -9,3 +9,3 @@
    payers rely on today (#4647).
- * Explicit `amount_msats` of 0 is rejected in `Bolt12Offer`s, `OfferBuidler`
+ * Explicit `amount_msats` of 0 is rejected in `Bolt12Offer`s, `OfferBuilder`
    now maps 0-amounts to an amount of `None` (#4324).

[TheBlueMatt]

Fixed further typos from #4706

diff --git a/CHANGELOG.md b/CHANGELOG.md
index a6fd5bfb18..67e929a5fc 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -3,9 +3,9 @@
 ## API Updates
- * `DefaultMessageRouter` will now always generate blinded message paths which
+ * `DefaultMessageRouter` will now always generate blinded message paths that
    provide no privacy (where our node is the introduction node) for nodes with
    public channels. This works around an issue which will appear for any nodes
-   with LND peers which enable onion messaging - such peers will refuse to
+   with LND peers that enable onion messaging - such peers will refuse to
    forward BOLT 12 messages from unknown third parties, which most BOLT 12
    payers rely on today (#4647).
- * Explicit `amount_msats` of 0 is rejected in `Bolt12Offer`s, `OfferBuilder`
+ * Explicit `amount_msats` of 0 is rejected in BOLT 12 `Offer`s; `OfferBuilder`
    now maps 0-amounts to an amount of `None` (#4324).
@@ -31,3 +31,3 @@
    `ChannelManager::abandon_payment` was called before the payment ultimately
-   completing anyway (#4651).
+   completes anyway (#4651).
  * Syncing a `ChainMonitor` using the `Confirm` trait will no longer write some
@@ -44,4 +44,4 @@
  * `InvoiceRequestBuilder` will no longer accept a `quantity` of `0` for a
-   `Bolt12Offer` allowing any quantity up to a bound (#4667).
- * `lightning-custom-message` handlers which return `Ok(None)` when asked to
+   BOLT 12 `Offer`, allowing any quantity up to a bound (#4667).
+ * `lightning-custom-message` handlers that return `Ok(None)` when asked to
    deserialize a message in their defined range no longer cause panics (#4709).