release: v0.2.0 — the dependency-major (alkcall 0.9.0 / alktunnels 0.3.0)

- Cargo.toml: alkcall 0.8.1 -> 0.9.0 (crates.io, the stub-sweep
  release) and alktunnels 0.2.1 -> 0.3.0 (its dependency-major ride);
  0.1.0 -> 0.2.0 (semver-incompatible dep bumps + public alkcall
  re-exports -> minor, matching the alktunnels 0.2.1 -> 0.3.0 ride)
- fuzz/shared/Cargo.toml: alkcall 0.9.0 (one alkcall version across
  the path graph)
- No code change: zero contact with the 0.9.0 breaking surface (no
  marked-pub registration, no control-handle subscription, no
  resource enumerator use, no generic op/register announcements;
  Establishment::default() is the only Establishment contact, in the
  session gate)
- CHANGELOG: 0.2.0 section + compare links
- README: the 0.2.0 note
- docs/architecture/overview.md: dep tree + feature table alkcall
  0.9.0 / alktunnels 0.3.0
- AGENTS.md: alkcall refs — v0.8.x/0.8.0 pin -> v0.9.x/0.9.0

Verification: cargo test (145 default / 171 all-features), fuzz/shared
corpus replay (3/3), clippy --all-targets -D warnings (native +
wasm32-unknown-unknown), fmt --check, wasm32 check, cargo doc, and
cargo publish --dry-run --allow-dirty all green

CHANGELOG.md

@@ -6,6 +6,37 @@ this crate adheres to [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.2.0] - 2026-10-14
+
+The dependency-major release: the alkcall substrate bumped 0.8.1 →
+0.9.0 (the stub-sweep release) and the alktunnels sibling bumped
+0.2.1 → 0.3.0. No alksocks API change, no wire change; no code
+contact with the 0.9.0 breaking surface at all (compile + suite green
+unchanged), which is why this is a minor bump rather than a patch:
+the semver-incompatible dependency bumps plus this crate's public
+re-exports of alkcall types make it semver-visible to downstream
+consumers (matching the alktunnels 0.2.1 → 0.3.0 ride).
+
+### Changed
+
+- **alkcall 0.8.1 → 0.9.0** (crates.io). The stub-sweep release: the
+  marked-pub open contract (S-01), `channel/control` (S-02),
+  `channel/resources/subscribe` (S-03), and `op/register`
+  forward-through (S-04) replace the four always-failing stubs. None
+  of the four stubs were on this crate's paths (no marked-pub
+  registration, no control-handle subscription, no resource
+  enumerator use, no generic `op/register` announcements). The 0.9.0
+  breaking list (`ManagerError::InvalidAdopt` additive,
+  `RelayError::PubTypedOpen` removal, the
+  `register_imported`/`register_imported_all` return change,
+  `Establishment` dropping its `Debug` derive) is untouched by this
+  crate's API use — `Establishment::default()` is the only
+  `Establishment` contact, in the session gate. 145 default / 171
+  all-features tests pass; wasm-clean verified.
+- **alktunnels 0.2.1 → 0.3.0** (the dependency-major ride on alkcall
+  0.9.0). No alktunnels API/wire change; the composed providers see
+  none of it.
+
 ## [0.1.0] - 2026-09-27
 
 The initial release: SOCKS5 (RFC 1928) as a produced resource on
@@ -111,5 +142,6 @@ campaigns clean, no crate bugs.
 [`AssociateSession`]: https://docs.rs/alksocks/latest/alksocks/consumer/struct.AssociateSession.html
 [`BindSession`]: https://docs.rs/alksocks/latest/alksocks/consumer/struct.BindSession.html
 
-[Unreleased]: https://git.alk.dev/alkdev/alksocks/compare/v0.1.0...HEAD
+[Unreleased]: https://git.alk.dev/alkdev/alksocks/compare/v0.2.0...HEAD
+[0.2.0]: https://git.alk.dev/alkdev/alksocks/compare/v0.1.0...v0.2.0
 [0.1.0]: https://git.alk.dev/alkdev/alksocks/releases/tag/v0.1.0