build(deps): bump dig-rewards-coin to 0.11 (dig_ecosystem#3450)

crates/dig-node-service/Cargo.toml

@@ -102,12 +102,12 @@ dig-node-control-interface = "0.33"
 # money-path understatement, and a lane has already been refused for putting exactly that
 # formula in a SPEC. Every figure this node reports for `control.collateral.requirement`
 # comes out of this crate so that a second derivation cannot drift from the consensus one.
-dig-mirror-collateral = "0.3"
+dig-mirror-collateral = "0.3.1"
 
 # The chain half of the same model: `census` counts the collateralised network at a block height
 # and hands `dig-mirror-collateral` the three integers its controller consumes (dig-node#400).
 # Without it a node could only ever record epoch 1, which is derivable from nothing.
-dig-mirror-coin = "0.9"
+dig-mirror-coin = "0.9.1"
 
 # The agreement rule this node believes a reflexive address BY (dig-node#566): `establish` combines
 # several untrusted readings into a per-family verdict (unanimous IP, >=2 independent source
@@ -126,7 +126,7 @@ ring = "0.17"
 # implemented: `chia-query` already provides the implementation this node uses
 # (`ChiaQueryProvider`), reached through `dig-wallet`'s one shared chain transport. Caret-matched
 # to the line `chia-query` and `dig-mirror-coin` compiled against, so all three unify on one crate.
-dig-chainsource-interface = "0.3"
+dig-chainsource-interface = "0.3.3"
 
 # The chia types that reach `mirror::spends`' PUBLIC signatures: `dig_mirror_coin::create` takes
 # `Vec<Cat>`, a `PublicKey`, `Coin` fee inputs and a `BigInt` epoch, and `build_create`/
@@ -217,7 +217,7 @@ dig-wallet = { path = "../dig-wallet" }
 # is what makes `RealClaimChainPort::own_entry` and `submit_initiate_payout` real instead of
 # refusals. Still the same chia 0.36 line (chia-sdk-driver `=0.36.0`, chia-protocol 0.36.1) every
 # other dependency in this crate is already pinned to.
-dig-rewards-coin = "0.10"
+dig-rewards-coin = "0.11"
 
 # HTTP stack: the same axum/tokio the node itself uses, so there is one async runtime
 # and one server framework across the node and the service shell. `ws` enables
@@ -242,7 +242,7 @@ axum-server = { version = "0.7", features = ["tls-rustls"] }
 # dig-cert is a leaf crate — no DIG dependencies and no `[patch.crates-io]` section — so the published
 # artifact cannot differ from the git-sourced one. That is the property dig-gossip lacks, which is why
 # this dep could be repointed and that one is a permanent carve-out (see dig-node-core, #2647).
-dig-cert = "0.1.2"
+dig-cert = "0.1.3"
 # The serving TLS stack — pinned byte-identical to dig-cert / dig-node-core / dig-dns (0.23,
 # default-features off, ring + std + tls12 + logging) so a build installs exactly ONE
 # `CryptoProvider` (ring) and never hits the "multiple CryptoProviders" install panic (#622 §7).
@@ -267,7 +267,7 @@ unicode-width = "0.2"
 # reusable `logs` CLI verbs + the bundle-time redaction engine. Every DIG service binary
 # gets logging from HERE rather than hand-rolling a subscriber. Sourced from crates.io (no
 # git/path dep) per the ecosystem crates.io policy (#681).
-dig-logging = "0.2"
+dig-logging = "0.2.2"
 # The logging facade the shell emits through. dig-node-core already depends on `tracing`;
 # the service shell now emits its own bring-up/lifecycle events through it, captured by the
 # `dig-logging` subscriber installed at the serve entrypoints.
@@ -294,13 +294,13 @@ reqwest = { version = "0.12", default-features = false, features = ["json", "rus
 # in the SERVICE shell's open-command path ONLY — NEVER in dig-node-core (the server
 # engine), where it would be the real dependency cycle. Depends on the PUBLISHED crates.io
 # version (no git dep, #681); native feature (reqwest transport + blocking convenience).
-dig-urn-resolver = "0.5.3"
+dig-urn-resolver = "0.5.4"
 
 # `dig_constants::DIG_NODE_PORT` (§5.3) — the single-sourced canonical default localhost port
 # for client→node connections; `config.rs`'s DEFAULT_PORT reads it rather than re-declaring the
 # literal. Held in lockstep with dig-node-core's pin (#2072) — 0.11.2, on dig-node's chia 0.36.1
 # line (dig_ecosystem#3161) — so the two node crates can never disagree about a canonical value.
-dig-constants = "0.13.0"
+dig-constants = "0.13.1"
 
 # Filesystem notification, for the §25 mirror pass's disk-event accelerant (dig-node#465). The
 # watcher is strictly an ACCELERANT: the round timer and the start-up reconcile remain the
@@ -400,7 +400,7 @@ chia-sdk-test = { version = "0.36.0", features = ["peer-simulator"] }
 # `ChainSource` double `dig-rewards-coin`'s own upstream simulator tests use for the identical
 # substitution (replace the network transport, not the reader) -- reused here rather than
 # hand-rolled, so the A3 test's double is the ecosystem's one sanctioned mock, not a second one.
-dig-chainsource-interface = { version = "0.3", features = ["testing"] }
+dig-chainsource-interface = { version = "0.3.3", features = ["testing"] }
 # `chia-consensus`/`chia-puzzles`/`clvm-traits` for the A3 test's own launch bundle: the exact
 # `RewardDistributorConstants`/`Offer`/CAT-issuance calls `dig-rewards-coin`'s own upstream
 # simulator tests use, at the SAME 0.36.1/0.20.3 lines `chia-sdk-driver`/`chia-sdk-types` (both