alkhttp 0.3.0

HTTP interface for the alk stack: serves HTTP/1.1 + HTTP/2 on standard ALPNs (with WebSocket upgrade carrying the channels protocol) and hosts the HTTP-backed call-protocol adapters
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91

# Changelog

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/).

## [Unreleased]

## [0.3.0] — 2026-09-07

### Changed

- **`alkcall` dependency bumped to 0.6.0** (review 007's
  establishment follow-ups sweep). One consumer-visible change: the
  `OpenHandler` signature gained a plan parameter —
  `Fn(Value, Option<ChannelPlan>, Connection, AuthContext) ->
  JoinHandle<()>` — so `OpenableAlpn::new` callers' handler closures
  gain a `_plan` argument (mechanical). With an establisher attached
  (ADR-049), its `Establishment.plan` (a typed-opaque
  `Arc<dyn Any + Send + Sync>`) is threaded process-locally to the
  handler's plan parameter: ALPN crates dial/allocate in the
  establisher and deliver the live handle without a side-channel
  handoff. This crate's WS ferry passes the `Option<OpenEstablisher>`
  through unchanged and constructs no `Establishment` itself, so the
  ride is otherwise additive — alkcall 0.6.0's `channels::pump_bidi`
  helper (ADR-050) is available to data-plane handlers this crate
  ferries. Docs updated (websocket.md, `OpenableAlpn` field docs,
  adapter.rs).

## [0.2.0] — 2026-09-06

### Changed

- **`alkcall` dependency bumped to 0.2** with the `gateway` feature
  enabled. The transport-neutral dispatch spine now comes from
  `alkcall::gateway` (promoted from this crate per alkcall ADR-048):
  `GatewayDispatch`, `schema_disclosure_denial`, and
  `DEFAULT_DEADLINE` are re-exported from `alkhttp::gateway`; the
  local copy (`gateway/dispatch.rs`) was deleted. The spine is used
  with the 30 s default deadline (identical behavior to the local
  version). alkcall 0.2 also carries the consumer-findings fixes
  CF-001..004 documented in
  `alkcall/docs/reviews/consumer-findings-ledger.md`.
- **`alkcall` dependency bumped to 0.4.1** (through 0.3, 0.4.0):
  - 0.3 — per-session fork, serving loop, and `op/register`
    (the WS op/register ACL surface in this crate builds on it);
    0.3.1 — `PeerCompositeEnv::peer_operations` so `list-peers`
    sees peer-announced ops (UP-03).
  - 0.4.0 — the registry enforces `input_schema` at call time
    (ADR-016 `INVALID_INPUT` leg); adapters no longer need to
    validate before dispatch.
  - 0.4.1 — early-arrival chunks are parked for un-adopted
    channels, closing the open/first-data race on the WS overlay.
  - 0.5.0 — the channels establisher phase (ADR-049):
    `OpenableAlpn` gains `establisher: Option<OpenEstablisher>` and
    `establisher_timeout: Option<Duration>` (both default `None` via
    `OpenableAlpn::new`, so existing constructions compile
    unchanged) plus a `with_establisher(establisher, timeout)`
    builder; the WS ferry calls
    `register_openable_with_establisher`, threading both fields
    through. With an establisher attached, the open op awaits the
    bounded establishment phase before the reply and resolves
    `channel:open_failed` with `details.reason` on failure — the
    channel never exists consumer-side. Without one, behavior is
    the pre-0.5 shape. The alkcall 0.5.0 `open_channel` error-type
    change needs no alkhttp change (this crate never calls
    `open_channel`; `from_wss` uses `ChannelClient::from_connection`
    only).
- **`/publish` chunk validation uses the registry-owned validator**
  (CF-003). The local compile-once `PublishSchemaCache`
  (`gateway/schema_cache.rs`) is removed — `publish_schema` is
  compiled at **registration time** by alkcall and exposed as
  `OperationRegistry::publish_validator`; an un-compilable schema is
  now a registration error, so the fail-open window this cache closed
  GW-side cannot exist upstream either. The `/publish` chunk stream
  resolves against the registry's cached validator.
- The from_wss drop monitor and the WS overlay tests use
  `CallError::connection_closed` (CF-001), and the
  review-001-ws-eof-signal race tests now assert retryable
  `CONNECTION_CLOSED` on **both** resolution paths (the drop monitor
  and the undelivered-request write failure) — the previously
  tolerated non-retryable `INTERNAL: failed to write request frame`
  outcome on the race path is gone.

### Notes

- **CF-004 convergence:** the alkhttp-local `services/schema`
  defense-in-depth guard remains, but its shared check
  (`schema_disclosure_denial`) is now alkcall's promoted
  implementation (ADR-048); the alkhttp-local copy is gone. See
  ADR-071 for the updated disposition.