docs: rename pass — update crate refs from alknet-* to alkcall

Update doc comments referencing the old alknet-* crate names and
spec paths to reflect the alkcall home. ALPN strings (alknet/call,
alknet/test) are wire-stable and unchanged. Sibling crate refs
(alknet-http, alknet-core historical context) kept as-is — those are
accurate references to crates that still exist or will be reworked
later.

Also fixes the pre-existing broken intra-doc link [`CallAdapter`] in
dispatch.rs (now [`super::adapter::CallAdapter`]) — the only doc
warning carried over from the extraction.

Verification:
- cargo test: 343 passed (0 failed)
- cargo clippy --all-targets -- -D warnings: clean
- cargo fmt --check: clean
- cargo doc --no-deps: clean (0 warnings, was 1)
This commit is contained in:
glm-5.2 committed 2026-08-12 05:58:59 +00:00
1 parent 4bc7a19695
commit 1ceb9b785d
10 files changed
+27 -34

No files matched your search

+8 -9
View File
@@ -1,15 +1,14 @@
//! Shared dispatch loop for `alknet/call` connections.
//!
//! Both [`CallAdapter`]'s accept path and [`crate::client::CallClient`]'s
//! connect path produce a [`CallConnection`] and hand it to the same dispatch
//! loop here (ADR-017 §1): the loop reads `EventEnvelope` frames off accepted
//! bidirectional streams, dispatches `call.requested` events against the
//! operation registry, and writes the response back on the same stream. The
//! connection-establishment half differs (accept vs dial); the dispatch half
//! is shared.
//! Both [`super::adapter::CallAdapter`]'s accept path and
//! [`crate::client::CallClient`]'s connect path produce a [`CallConnection`]
//! and hand it to the same dispatch loop here (ADR-017 §1): the loop reads
//! `EventEnvelope` frames off accepted bidirectional streams, dispatches
//! `call.requested` events against the operation registry, and writes the
//! response back on the same stream. The connection-establishment half
//! differs (accept vs dial); the dispatch half is shared.
//!
//! See `docs/architecture/crates/call/call-protocol.md` and
//! `docs/architecture/crates/call/client-and-adapters.md` for the spec.
//! See `docs/architecture/` for the spec.
use std::collections::HashMap;
use std::sync::Arc;