chore: release alkhttp 0.7.0

- version bump 0.6.0 -> 0.7.0 (minor per the dep-wave convention:
  0.5.0 rode alkcall 0.8.0; see the preceding consume commit)
- README usage snippet 0.5.0 -> 0.7.0
- changelog: cut [0.7.0] with the alkcall 0.9.0 consumption under
  Changed (the stub-sweep audit: no ManagerError/RelayError matching,
  no Establishment construction, no marked-pub surface reached through
  the HTTP API) and the two ride-through fixes under Fixed
  (register_imported Result in the WS overlay tests, fuzz/shared spec
  alignment)

Verification: cargo test/clippy/fmt/doc green in the preceding deps
commit; no source change in this commit

CHANGELOG.md

@@ -4,6 +4,44 @@ All notable changes to this crate are documented here. The format is
 based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 this crate adheres to [Semantic Versioning](https://semver.org/).
 
+## [0.7.0] — 2026-10-14
+
+### Changed
+
+- **`alkcall` dependency bumped to 0.9.0** (the stub-sweep release: the
+  four registered-but-always-failing stubs across nine published
+  versions are replaced with real implementations — the marked-pub
+  open contract (S-01), `channel/control` (S-02),
+  `channel/resources/subscribe` (S-03), and `op/register`
+  forward-through (S-04)). No code change in this crate — none of the
+  0.9.0 breaking surfaces are constructed or pattern-matched here: no
+  `ManagerError` match arms (the new `InvalidAdopt` variant changes
+  nothing), no `RelayError` matching (the removed `PubTypedOpen`
+  variant is unreachable from this crate), no `Establishment`
+  construction or `Debug` dependence (the WS ferry passes
+  `Option<OpenEstablisher>` through unchanged), and the
+  `op/register` forward-through refactor does not touch the
+  `from_wss` import filter or the adapter-registered leaf bundles.
+  The S-01 marked-pub machinery is consumer-side assembly, not an
+  HTTP-surface concern; the four gateway operations and the WS
+  session shape are unchanged.
+
+### Fixed
+
+- `tests/ws_overlay_ops.rs` now expects `register_imported`'s new
+  `Result<(), String>` return (alkcall 0.9.0 API change): the eight
+  connection-overlay registration sites assert success instead of
+  discarding the value. Test-only.
+- `fuzz/shared` follows the main crate to alkcall 0.9 (the harness
+  replay previously resolved alkcall 0.8.1 alongside alkhttp's 0.9.0,
+  two incompatible copies in one build). Infra-only.
+
+Minor bump 0.6.0 → 0.7.0 per the dep-wave convention (0.3.0 rode
+alkcall 0.6.0, 0.4.0 rode 0.7.0, 0.5.0 rode 0.8.0): this crate's
+public API carries alkcall types through re-exports and the
+`ProtocolHandler` impl, so a semver-breaking upstream is
+semver-relevant here.
+
 ## [0.6.0] — 2026-09-29
 
 ### Added

Cargo.lock

@@ -48,7 +48,7 @@ dependencies = [
 
 [[package]]
 name = "alkhttp"
-version = "0.6.0"
+version = "0.7.0"
 dependencies = [
  "alkcall",
  "arc-swap",

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "alkhttp"
-version = "0.6.0"
+version = "0.7.0"
 edition = "2021"
 rust-version = "1.88"
 license = "MIT OR Apache-2.0"

README.md

@@ -161,7 +161,7 @@ A lean single-side build takes `default-features = false` plus the side
 it needs:
 
 ```toml
-alkhttp = { version = "0.5.0", default-features = false, features = ["server"] }
+alkhttp = { version = "0.7.0", default-features = false, features = ["server"] }
 ```
 
 ## Security posture