chore(deps): cut over to published ADR-0004 crates

Strip the temporary [patch.crates-io] git branches and repin ant-node
from the grumbach ADR-0004 branch to the published 0.14.3, now that the
coordinated ADR-0004 cutover crates are published in order
evmlib 0.9.0 -> ant-protocol 2.3.0 -> ant-node 0.14.3. ant-protocol was
already pinned to 2.3.0.

Lockfile regenerated to registry sources; the workspace resolves a
single saorsa-core 0.26.2 and `cargo check` builds clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: jacderida

Cargo.lock

@@ -1,21 +1,3 @@
 [workspace]
 members = ["ant-core", "ant-cli"]
 resolver = "2"
-
-# ─── TEMPORARY: STRIP BEFORE MERGE — ADR-0004 coordinated cutover ───
-# ant-protocol/evmlib's ADR-0004 commitment-bound-quote types (the signed
-# `committed_key_count`/`commitment_pin` fields, the commitment sidecar, and
-# `BadQuoteCommitment`) are not yet published to crates.io, so this workspace
-# cannot build against the published `ant-protocol`/`evmlib`. These git patches
-# point those deps at their PR branches so CI can build the coordinated change.
-#
-# AT RELEASE (once the ADR-0004 versions are published, in order
-# evmlib → ant-protocol):
-#   1. delete this entire [patch.crates-io] block, AND
-#   2. bump the `ant-protocol` pin in ant-core/Cargo.toml to the published
-#      version (evmlib is re-exported through ant-protocol, no direct pin):
-#        ant-protocol = "2.3.0"   # <- published ADR-0004 ant-protocol
-#        # (which in turn depends on the published evmlib = "0.9.0")
-[patch.crates-io]
-evmlib = { git = "https://github.com/WithAutonomi/evmlib", branch = "adr-0003-signed-quote-fields" }
-ant-protocol = { git = "https://github.com/WithAutonomi/ant-protocol", branch = "adr-0003-commitment-bound-pricing" }

Cargo.toml

@@ -62,10 +62,10 @@ sysinfo = { version = "0.32", default-features = false, features = ["system"] }
 # `ant-protocol` pin above — a version skew pulls a second copy of
 # `saorsa-core` into the graph and makes `ant_node`'s and `ant_protocol`'s
 # `MultiAddr` mutually incompatible in `node/devnet.rs`. While the runtime
-# `ant-protocol` pin above points at a git branch, this ant-node must point at
-# the matching ant-node branch carrying the same saorsa-core / ant-protocol
-# lineage rather than a released version.
-ant-node = { git = "https://github.com/grumbach/ant-node", branch = "adr-0003-commitment-bound-pricing", optional = true }
+# `ant-protocol` pin above points at a released version, this ant-node must
+# track the matching released version carrying the same saorsa-core /
+# ant-protocol lineage.
+ant-node = { version = "0.14.3", optional = true }
 tracing-subscriber = { version = "0.3", features = ["env-filter"] }
 
 [target.'cfg(unix)'.dependencies]
@@ -96,7 +96,7 @@ test-utils = []
 # always compile even without the `devnet` feature. Pinned to the same
 # version as the runtime dep so there is a single ant-node /
 # saorsa-core version across the whole graph.
-ant-node = { git = "https://github.com/grumbach/ant-node", branch = "adr-0003-commitment-bound-pricing", features = ["test-utils"] }
+ant-node = { version = "0.14.3", features = ["test-utils"] }
 serial_test = "3"
 anyhow = "1"
 alloy = { version = "1.6", features = ["node-bindings"] }