feat: alkcall 0.8.0 adoption — bump to 0.5.0

- BREAKING (ecosystem-coordination): alkcall bumped to 0.8.0. No type
  alktty touches changed shape (ChannelCore/openable machinery,
  OpenEstablisher/OpenHandler/Establishment/ChannelPlan,
  ChannelClient::open_channel, ChannelOpenError::CallFailed are
  identical to 0.7.1); the new reply-projection / relay / hub-leg
  surfaces are additive and alktty exercises none of them. alktty's own
  open op is the standard-shape name channels/tty/sub, so the new
  flavor-form discovery path stays on the byte-stable standard
  derivation, and with no establisher reply-fields configured the open
  reply is byte-identical to pre-0.8.0. The minor bump is for
  downstream lockstep, since alktty's public signatures reference
  alkcall types.
- Verification counts unchanged from the 0.7.1 baseline (113 default /
  156 all-features); the adoption required no source change in alktty.

Verification:
- cargo test: 113 passed (default), 156 passed (--all-features)
- cargo clippy --all-targets -- -D warnings: clean
- cargo fmt --check: clean
- cargo doc --no-deps: clean
- cargo check/clippy --target wasm32-unknown-unknown -D warnings: clean
- cargo publish --dry-run --allow-dirty: clean

CHANGELOG.md

@@ -4,6 +4,39 @@ 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.5.0] - 2026-09-18
+
+The alkcall 0.8.0 adoption: a dependency bump only — no source change
+in alktty. alkcall 0.8.0 landed review 008's remediation (the
+establisher reply projection, flavor-form open-op ids in discovery, the
+in-tree `ChannelRelay` + `HubLegImports`/`HubLegTemplate`) plus a
+post-landing hardening sweep; all new surfaces are additive on the
+call-plane JSON and the registry seams, and the channels data plane is
+untouched. The wire format, the direct-ALPN path, the `TtyBackend`
+trait, and alktty's public API surface are unchanged.
+
+### Changed
+
+- **BREAKING (ecosystem-coordination) — `alkcall` bumped to 0.8.0.**
+  alkcall 0.8.0 changed no type that alktty touches: the open-op
+  machinery alktty registers through (`ChannelCore`/
+  `register_openable_with_establisher`/`OpenEstablisher`/`OpenHandler`
+  /`Establishment`/`ChannelPlan`, `ChannelClient::open_channel`,
+  `ChannelOpenError::CallFailed`) is shape-identical to 0.7.1 — the
+  new `open_channel_with_reply` / reply-field / relay / hub-leg
+  surfaces are additive and alktty exercises none of them. alktty's
+  own open op is the standard-shape name `channels/tty/sub`, so the
+  new flavor-form `channel_open_alpn` discovery path stays on the
+  byte-stable standard derivation, and with no establisher
+  reply-fields configured the open reply is byte-identical to
+  pre-0.8.0. alktty's public signatures reference alkcall types, so
+  downstream crates must now unify on alkcall 0.8.0. Minor bump per
+  the 0.x ecosystem-coordination rule.
+- **`alkcall` requirement updated to `0.8.0`; lockfile bumped from
+  0.7.1 to 0.8.0.** Verification counts are unchanged from the 0.7.1
+  baseline (113 default / 156 all-features) — the adoption required no
+  source change in alktty.
+
 ## [0.4.1] - 2026-09-10
 
 The MSRV floor becomes honest: `rust-version` raises from 1.85 to
@@ -288,6 +321,7 @@ alknet mono-repo.
   the client→backend pump is aborted at session end instead of
   lingering until the client disconnects.
 
+[0.5.0]: https://git.alk.dev/alkdev/alktty/releases/tag/v0.5.0
 [0.4.1]: https://git.alk.dev/alkdev/alktty/releases/tag/v0.4.1
 [0.4.0]: https://git.alk.dev/alkdev/alktty/releases/tag/v0.4.0
 [0.3.0]: https://git.alk.dev/alkdev/alktty/releases/tag/v0.3.0

Cargo.lock

@@ -27,9 +27,9 @@ dependencies = [
 
 [[package]]
 name = "alkcall"
-version = "0.7.1"
+version = "0.8.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "ac26db919a1db9d72910ead8741af683bedefc625631028194b5f5e1dbd63cb6"
+checksum = "8695d47cee5b5a5fe68471f04a505bc257a7e7ed9e64d827de33ff83adf4db12"
 dependencies = [
  "async-trait",
  "bytes",
@@ -48,7 +48,7 @@ dependencies = [
 
 [[package]]
 name = "alktty"
-version = "0.4.1"
+version = "0.5.0"
 dependencies = [
  "alkcall",
  "async-trait",

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "alktty"
-version = "0.4.1"
+version = "0.5.0"
 edition = "2021"
 rust-version = "1.88"
 license = "MIT OR Apache-2.0"
@@ -25,7 +25,7 @@ default = []
 local = ["dep:portable-pty", "dep:tokio-util", "tokio/process", "tokio/rt-multi-thread"]
 
 [dependencies]
-alkcall = "0.7.0"
+alkcall = "0.8.0"
 # Minimal, wasm-clean tokio features. `local` adds `process` +
 # `rt-multi-thread` (non-wasm). Do NOT use `features = ["full"]` — it
 # pulls in `signal`/`fs`/`net` which break `wasm32-unknown-unknown`.