docs(readme): drop the redundant version-history section

The graduation and 0.2.1 through 0.4.1 release notes duplicate
CHANGELOG.md; the README now flows from the WASM target section
straight into Features.

README.md

@@ -283,52 +283,6 @@ the protocol layer for a sandboxed TS/Python adapter. The `local`
 feature (real sockets) needs a real OS and is non-wasm by design;
 enabling it on wasm is a compile error.
 
-## Version 0.2: the graduation
-
-0.2 rides alkcall 0.8.0 and graduates the proxy surface
-(`docs/research/tunnels-graduation.md`, ADRs 007/008):
-
-- **The direct op** (`channels/tunnel/direct`, scope `tunnel:direct`),
-  dynamic-target egress; `TunnelSession::open_direct`.
-- **The bind-first establisher + the forwarded op**
-  (`channels/tunnel/forwarded`, scope `tunnel:forwarded`), the
-  composed `-R` metadata flow: `bound` + correlation token in the
-  listen reply, `{listen, substrate, peer}` per accept;
-  `TunnelListener` + `parse_listen_reply`/`listen_reply_fields`.
-- **alkcall 0.7.1 → 0.8.0** brings `Establishment::with_reply_field` +
-  `open_channel_with_reply` (the bind-first carriers) and
-  flavor-form op ids in discovery (hub relay wraps them as channels);
-  bonus: in-tree `ChannelRelay`/`HubLegTemplate` (alkcall ADR-051).
-
-0.2.1 is the hardening release: the `fuzz/` workspace (three
-cargo-fuzz targets over the datagram codec, the params parsers, and a
-stateful session-pump target; corpora replay as plain `cargo test`,
-documented in `docs/research/fuzzing.md`) and the alkcall bump 0.8.0 → 0.8.1
-(duplicate adopt/open no longer destroys the live channel, relevant
-to the reverse-path adopt flow). Two additive diagnostics:
-`TunnelSession::datagram_backlog()` and
-`DatagramReader::retained_bytes()`. No API break, no wire change.
-
-0.3.0 rides the alkcall bump 0.8.1 → 0.9.0 (the stub-sweep release:
-the four registered-but-always-failing stubs became real
-implementations; none were on this crate's paths). No alktunnels API
-change, no wire change; minor rather than patch because the
-semver-incompatible dependency bump + this crate's alkcall type
-re-exports make it semver-visible downstream.
-
-0.4.0 rides the alkcall bump 0.9.0 → 0.10.0 (the gateway
-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.
-
-0.4.1 rides the alkcall bump 0.10.0 → 0.10.1 (the adoption-window
-ordering fix, where 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
 
 | Feature | Contents | wasm |