chore(release): v0.262.0 -- reward wire can say not recoverable

CHANGELOG.md

@@ -4,6 +4,27 @@ All notable changes to this project are documented here.
 This project adheres to [Semantic Versioning](https://semver.org) and
 [Conventional Commits](https://www.conventionalcommits.org).
 
+## [0.262.0] - 2026-10-02
+
+### BREAKING
+- `dig.listRewardDistributorCommitments`: `recoverable_base_units` is now `null` (key present) when a commitment is
+  not recoverable; `0` remains a real zero. Clients that decode it as a plain integer must accept `null`; dig-app
+  `nightly-20261002` or later is required to render it. Cascades dig-rpc-protocol 0.15, dig-peer 0.17,
+  dig-download 0.26, dig-peer-selector 0.15 (#631, dig_ecosystem#3442)
+
+### Features
+- **rewards:** `recoverable_base_units` can say "not recoverable" instead of collapsing to 0 (#631)
+
+### Bug Fixes
+- **rewards:** Install FundedDistributorRegistry at startup; refuse a malformed launcher_id (#626, dig_ecosystem#3292)
+- **rewards:** Fold observed_at to the oldest report; log IoFailed (#628, dig_ecosystem#3323, dig_ecosystem#3324)
+
+### Documentation
+- **spec:** Section 26 prover loop spawn, four controls, kill switch (#627, dig_ecosystem#3265)
+
+### Chores
+- **deps:** Bump the dig-rpc-protocol cascade to 0.14.0 (#629, dig_ecosystem#3329)
+
 ## [0.255.0] - 2026-09-07
 
 ### Chores

Cargo.toml

@@ -33,7 +33,7 @@ edition = "2021"
 # release to fire (§3.6). The library crates (dig-node-core/dig-runtime/dig-wallet)
 # keep their own independent versions — only the released binary tracks the workspace version.
 
-version = "0.261.0"
+version = "0.262.0"
 # Release hardening, matching digstore: keep integer-overflow checks ON in release.
 # The node parses untrusted serialized input and does offset/length arithmetic over
 # it, so silent wrapping in release would turn a length bug into a memory/logic hazard.

crates/dig-node-core/Cargo.toml

@@ -198,7 +198,8 @@ serde_json = "1"
 # (0.15.0), `dig-download` (0.24.0) and `dig-peer-selector` (0.13.0) below all moved onto this line
 # in the same batch, so exactly one `dig-rpc-protocol` still resolves (asserted by
 # `crates/dig-node-core/tests/dependency_tree.rs`).
-dig-rpc-protocol = "0.12"
+# Moved to 0.15 (dig_ecosystem#3442): recoverable_base_units becomes Option<u64>.
+dig-rpc-protocol = "0.15"
 # The directed-message base protocol (epic #793/#796): the e2e seal/open pipeline + the typed envelope
 # the chat subsystem seals into. dig-node is the TRANSPORT — it seals an app-supplied opaque DIGCHAT1
 # envelope to the recipient's 0x0010 BLS identity key and dig-gossip directed-sends the sealed bytes.
@@ -471,7 +472,8 @@ dig-pex = "0.1.1"
 #
 # Moved to 0.24 (dig_ecosystem#3269, final leg): 0.24.0 is on `dig-rpc-protocol` 0.12, matching this
 # crate's own move to 0.12 above.
-dig-download = "0.24"
+# Moved to 0.26 (dig_ecosystem#3442): recoverable_base_units becomes Option<u64>.
+dig-download = "0.26"
 # -- The shared peer client (#1283/#1576) -------------------------------------------------------------
 # `DigPeer` — the ONE DIG Network peer client: peer_id-pinned mTLS over the full NAT ladder plus typed
 # RPC. Depended on DIRECTLY (not only transitively through dig-download) because dig-node supplies the
@@ -489,7 +491,8 @@ dig-download = "0.24"
 #
 # Moved to 0.15 (dig_ecosystem#3269, final leg): 0.15.0 is on `dig-rpc-protocol` 0.12, matching this
 # crate's own move to 0.12 above.
-dig-peer = "0.15"
+# Moved to 0.17 (dig_ecosystem#3442): recoverable_base_units becomes Option<u64>.
+dig-peer = "0.17"
 # -- Self-optimizing peer selection (#178) ------------------------------------------------------------
 # The decision + learning layer between dig-dht discovery and dig-download execution: it ranks the
 # providers `find_providers` returns (learning throughput/rtt/reliability + a per-class saturation
@@ -525,7 +528,8 @@ dig-peer = "0.15"
 #
 # Moved to 0.13 (dig_ecosystem#3269, final leg): 0.13.0 is on `dig-peer ^0.15`, matching this crate's
 # own move to `dig-peer = "0.15"` above and closing the cascade at `dig-rpc-protocol` 0.12.
-dig-peer-selector = "0.13"
+# Moved to 0.15 (dig_ecosystem#3442): recoverable_base_units becomes Option<u64>.
+dig-peer-selector = "0.15"
 # The canonical DIG mTLS certificate crate (L00, crates.io). The node's PERSISTENT machine identity
 # is a CA-signed `dig_tls::NodeCert` minted from the node's own BLS identity key and persisted 0600 in
 # the data dir (#908 identity boundary: this is the MACHINE key, never a user key). Replaces the
@@ -609,7 +613,7 @@ rcgen = "0.13"
 #
 # Pinned by the `the_fail_open_anchor_verifier_is_not_reachable_from_a_production_build` test, which
 # fails if `testkit` ever appears on the production entry.
-dig-download = { version = "0.24", features = ["testkit"] }
+dig-download = { version = "0.26", features = ["testkit"] }
 # Captures the peer-facing serve's real emitted tracing records into an in-memory buffer, so the
 # serve-observability tests (#1595) assert what an operator would actually see in the node log —
 # and that no payload byte or proof ever reaches it.