release: v0.4.1 — the dependency-patch (alkcall 0.10.1)

- Cargo.toml: alkcall 0.10.0 -> 0.10.1 (crates.io, the
  adoption-window ordering fix — review 013, routed from alkgit's
  wave-2 gate; install + park-drain are one atomic section so a
  demux-routed chunk can no longer overtake earlier-parked early
  arrivals, plus the parked-forever loss variant closed) and
  0.4.0 -> 0.4.1 (no alktunnels API change, no wire change, backwards-
  compatible dep bump -> patch)
- CHANGELOG: Unreleased cut to 0.4.1 (the alkcall 0.10.1 ride + the
  compare links updated)
- README: the 0.4.1 note (alkcall 0.10.1 adoption-window ordering fix)
- docs/architecture/overview.md: dep tree alkcall 0.10.1

Verification: cargo test (136 pass, default + all-features),
clippy --all-targets -D warnings (default, all-features,
wasm32-unknown-unknown), fmt --check, doc, wasm32 check, and cargo
publish --dry-run --allow-dirty all green

CHANGELOG.md

@@ -6,6 +6,32 @@ this crate adheres to [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.4.1] - 2026-10-22
+
+The dependency-patch release: the alkcall substrate bumped 0.10.0 →
+0.10.1 (the adoption-window ordering fix). No alktunnels API change,
+no wire change — the only file-level contacts with the bump are
+`Cargo.toml`/`Cargo.lock`.
+
+### Changed
+
+- **alkcall 0.10.0 → 0.10.1** (crates.io). The bug-fix release
+  (review 013, routed from alkgit's wave-2 gate): the
+  `adopt_channel` install→drain window is now one atomic section, so
+  a chunk routed by the demux inside the window can no longer be
+  delivered ahead of earlier-parked early arrivals (the observed
+  downstream shape was pkt-line desync in alkgit's open-op
+  integration test under multi-process load), and a related loss
+  variant (a chunk parked after the drain removed the queue, parked
+  forever) is closed. Relevant in principle to this crate's
+  reverse-path adopt flow (the bind-first establisher surfaces
+  channels through the same adopt path), though no change in this
+  crate's own surfaces was needed. No API, wire-format
+  (`EventEnvelope`, the 8-byte chunk header), or documented-cap
+  behavior change upstream — the fix surface is private; the behavior
+  only strengthens. 136 tests pass; wasm-clean verified (check +
+  clippy on `wasm32-unknown-unknown`).
+
 ## [0.4.0] - 2026-10-19
 
 The dependency-major release: the alkcall substrate bumped 0.9.0 →
@@ -332,7 +358,8 @@ complete (Phase 2, review 001 findings remediated).
   matrix). Wasm-clean default crate verified (`wasm32-unknown-unknown`
   check + clippy).
 
-[Unreleased]: https://git.alk.dev/alkdev/alktunnels/compare/v0.4.0...HEAD
+[Unreleased]: https://git.alk.dev/alkdev/alktunnels/compare/v0.4.1...HEAD
+[0.4.1]: https://git.alk.dev/alkdev/alktunnels/compare/v0.4.0...v0.4.1
 [0.4.0]: https://git.alk.dev/alkdev/alktunnels/compare/v0.3.0...v0.4.0
 [0.3.0]: https://git.alk.dev/alkdev/alktunnels/compare/v0.2.1...v0.3.0
 [0.2.1]: https://git.alk.dev/alkdev/alktunnels/compare/v0.2.0...v0.2.1

Cargo.lock

@@ -27,9 +27,9 @@ dependencies = [
 
 [[package]]
 name = "alkcall"
-version = "0.10.0"
+version = "0.10.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "6b8ef0591beff0e3fe64b7277a67d8e7caeccf71c27538b4b7aced028d22ca44"
+checksum = "690d747f42baf385dc22cd120f79d43cf1ea239bc426675e0e1e225b57fc031a"
 dependencies = [
  "async-trait",
  "bytes",
@@ -48,7 +48,7 @@ dependencies = [
 
 [[package]]
 name = "alktunnels"
-version = "0.4.0"
+version = "0.4.1"
 dependencies = [
  "alkcall",
  "bytes",

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "alktunnels"
-version = "0.4.0"
+version = "0.4.1"
 edition = "2021"
 rust-version = "1.88"
 license = "MIT OR Apache-2.0"
@@ -23,7 +23,7 @@ default = []
 local = ["tokio/net"]
 
 [dependencies]
-alkcall = "0.10.0"
+alkcall = "0.10.1"
 tokio = { version = "1", default-features = false, features = ["rt", "sync", "io-util", "macros", "time"] }
 bytes = "1"
 futures = "0.3"

README.md

@@ -321,7 +321,13 @@ ownership-seam release — the loud ownership-wiring default on the
 `GatewayDispatch` spine, behind the opt-in `gateway` feature; none of
 it is on this crate's paths, which serve via
 `ChannelCore::register_openable*` dispatch). No alktunnels API
-change, no wire change; same minor-not-patch reasoning as 0.3.0.
+  change, no wire change; same minor-not-patch reasoning as 0.3.0.
+
+0.4.1 rides the alkcall bump 0.10.0 → 0.10.1 (the adoption-window
+ordering fix — a chunk routed inside the `adopt_channel` install→drain
+window can no longer overtake earlier-parked early arrivals). No
+alktunnels API change, no wire change; patch because the dependency
+bump is backwards-compatible.
 
 ## Features
 

docs/architecture/overview.md

@@ -109,7 +109,7 @@ establisher + the forwarded op (ADR-008).
 
 ```
 alktunnels (default — wasm-clean)
-├── alkcall 0.10.0  (core types, channels: ChannelCore/ChannelClient/manager,
+├── alkcall 0.10.1  (core types, channels: ChannelCore/ChannelClient/manager,
 │                    pump_bidi, ServingConfig identity seam — CF-005/006,
 │                    establisher reply projection + flavor-form discovery
 │                    derivation + ChannelRelay/HubLegTemplate — review 008/ADR-051)