docs(readme): drop the Version 0.1 section

Per-version release notes (0.1 through 0.3.2) duplicated the
changelog; that section was also stale-titled. The section is
removed; the changelog stays the release-history home.

README.md

@@ -213,60 +213,6 @@ default build is wasm-clean by construction.
 | `local` | the socket-backed seam providers ([`tcp_dial`](https://docs.rs/alksocks/latest/alksocks/local/fn.tcp_dial.html) / [`udp_egress`](https://docs.rs/alksocks/latest/alksocks/local/fn.udp_egress.html) / [`bind_accept`](https://docs.rs/alksocks/latest/alksocks/local/fn.bind_accept.html)), the front doors ([`FrontDoor`](https://docs.rs/alksocks/latest/alksocks/door/struct.FrontDoor.html) + [`UdpFrontDoor`](https://docs.rs/alksocks/latest/alksocks/door/struct.UdpFrontDoor.html), the consumer-side exposure; [`ProducerDoor`](https://docs.rs/alksocks/latest/alksocks/local/producer_door/struct.ProducerDoor.html), the producer-side listener) | no |
 | `composed` | the alktunnels-composed providers: [`direct_egress`](https://docs.rs/alksocks/latest/alksocks/composed/fn.direct_egress.html) (the direct-op egress, a lazy destination→tunnel table) + [`bindfirst_accept`](https://docs.rs/alksocks/latest/alksocks/composed/fn.bindfirst_accept.html) (the BIND accept whose listener lives on a bind-first listen resource) | yes |
 
-## Version 0.1
-
-The first release rides alkcall 0.8.1 (the establisher reply
-projection is not consumed yet; the open op's params are trivial;
-the 0.8.1 duplicate-adopt fix is directly relevant to the consumer
-open/adopt paths) and alktunnels 0.2.1 (the direct op + the
-bind-first/forwarded flow power the composed providers). The
-`fuzz/` workspace (excluded from the published package) fuzzes the
-two attacker-reachable parser classes: the ASSOCIATE datagram codec
-and the RFC 1928 handshake state machine. Wire-stable surface: the
-`alk/socks5` ALPN, the `channels/socks5/sub` open op with `{}` params,
-and the two scope constants, all pinned by ADRs 001–014.
-
-0.2.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) and the alktunnels
-bump 0.2.1 → 0.3.0. No alksocks API change, no wire change, zero code
-contact with the 0.9.0 breaking surface; minor rather than patch
-contact with the 0.9.0 breaking surface; minor rather than patch
-because the semver-incompatible dependency bumps + this crate's
-alkcall type re-exports make it semver-visible downstream.
-
-0.3.0 rides the alkcall bump 0.9.0 → 0.10.0 (the gateway
-ownership-seam release: `GatewayDispatch` ownership-provider
-threading and the loud unwired-spine default; the gateway module
-isn't on this crate's paths, registry dispatch on the native wire is
-untouched) and the alktunnels bump 0.3.0 → 0.4.0 (the dependency-major
-ride on alkcall 0.10.0). No alksocks API change, no wire change, zero
-code contact with the 0.10.0 breaking surface (the only contact is the
-fuzz/shared harness's own alkcall pin (a mechanical lockstep bump);
-minor rather than patch for the same semver-visible-dependency reason
-as 0.2.0.
-
-0.3.1 rides the alkcall bump 0.10.0 → 0.10.1 (the
-adoption-window ordering fix: a chunk routed inside the demux's
-install→drain window could be delivered ahead of earlier-parked
-early arrivals, inverting byte-stream order; relevant in principle
-to the bind-first adopt flow) and the alktunnels bump 0.4.0 → 0.4.1
-(its dependency-patch ride). The fix surface is private upstream, so
-there is no change on this crate's paths; patch rather than minor
-because both dependency bumps are semver-compatible.
-
-0.3.2 rides the alktunnels bump 0.4.1 → 0.5.0 (the correlation-gate
-release: the forwarded op's serving half gains an establishment
-phase, `register_tunnel_forwarded_openable_with_establisher` +
-`ForwardedGate`: a stale/missing `listen` token fails the open as a
-typed `channel:open_failed` instead of success-then-silent-birth-
-teardown). Additive API only, no wire change, no alkcall bump
-(0.10.1 rides on); the composed accept stays on the base
-`register_tunnel_forwarded_openable` (kept byte-for-byte upstream),
-so there is no change on this crate's paths. Patch rather than minor:
-semver-compatible additive dependency bump, matching the 0.3.1
-precedent.
-
 ## Verification
 
 ```bash