docs(changelog): record the alkcall 0.3 -> 0.4.1 consumption waves

The [Unreleased] section still led with the alkcall 0.2 bump; the
0.3 (per-session fork, op/register, UP-03), 0.4.0 (registry
input_schema enforcement), and 0.4.1 (early-arrival chunk parking)
waves were unrecorded. Also removes a copy-paste duplication in the
CF-003 entry.

Verification: cargo test, clippy (both feature sets), fmt, doc,
publish --dry-run — all green.

CHANGELOG.md

@@ -18,15 +18,22 @@ this crate adheres to [Semantic Versioning](https://semver.org/).
   version). alkcall 0.2 also carries the consumer-findings fixes
   CF-001..004 documented in
   `alkcall/docs/reviews/consumer-findings-ledger.md`.
+- **`alkcall` dependency bumped to 0.4.1** (through 0.3, 0.4.0):
+  - 0.3 — per-session fork, serving loop, and `op/register`
+    (the WS op/register ACL surface in this crate builds on it);
+    0.3.1 — `PeerCompositeEnv::peer_operations` so `list-peers`
+    sees peer-announced ops (UP-03).
+  - 0.4.0 — the registry enforces `input_schema` at call time
+    (ADR-016 `INVALID_INPUT` leg); adapters no longer need to
+    validate before dispatch.
+  - 0.4.1 — early-arrival chunks are parked for un-adopted
+    channels, closing the open/first-data race on the WS overlay.
 - **`/publish` chunk validation uses the registry-owned validator**
   (CF-003). The local compile-once `PublishSchemaCache`
   (`gateway/schema_cache.rs`) is removed — `publish_schema` is
   compiled at **registration time** by alkcall and exposed as
   `OperationRegistry::publish_validator`; an un-compilable schema is
   now a registration error, so the fail-open window this cache closed
-  compiled at **registration time** by alkcall and exposed as
-  `OperationRegistry::publish_validator`; an un-compilable schema is
-  now a registration error, so the fail-open window this cache closed
   GW-side cannot exist upstream either. The `/publish` chunk stream
   resolves against the registry's cached validator.
 - The from_wss drop monitor and the WS overlay tests use