ci: address review feedback on PR #2243

- Remove debug RUST_LOG configuration from CI that was inadvertently included
- Replace named `_upstream` with anonymous `_` in try_to_broadcast since it's unused
- Add comment explaining intentional ordering of network message vs client notification

[AI-assisted - Claude]

Author: sanity

.github/workflows/ci.yml

@@ -96,9 +96,6 @@ jobs:
 
     env:
       FREENET_LOG: error
-      # Enable debug logging for transport layer to diagnose packet delivery issues
-      # Also allow info level for test_utils so logger capture tests work
-      RUST_LOG: "error,freenet::transport::peer_connection=debug,freenet_core::transport::peer_connection=debug,freenet::test_utils=info,freenet_core::test_utils=info"
       CARGO_TARGET_DIR: ${{ github.workspace }}/target
 
     steps:

crates/core/src/operations/update.rs

@@ -514,7 +514,7 @@ async fn try_to_broadcast(
     last_hop: bool,
     _op_manager: &OpManager,
     state: Option<UpdateState>,
-    (broadcast_to, _upstream): (Vec<PeerKeyLocation>, PeerKeyLocation),
+    (broadcast_to, _): (Vec<PeerKeyLocation>, PeerKeyLocation),
     key: ContractKey,
     new_value: WrappedState,
     is_from_a_broadcasted_to_peer: bool,
@@ -1114,6 +1114,12 @@ pub(crate) async fn request_update(
     // NOTE: We do NOT call op_manager.completed() here because the operation
     // needs to remain in the state map until peek_target_addr can route it.
     // The operation will be marked complete later when the message is processed.
+    //
+    // The ordering here (network message sent before client notification) is intentional:
+    // we want to ensure the message is queued for transmission before we report success
+    // to the host. Both operations use async channels, so the actual execution order
+    // depends on the runtime, but this ordering provides the best-effort guarantee that
+    // network propagation has started when the client receives success.
     let op = UpdateOp {
         id,
         state: Some(UpdateState::Finished {