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)

src/lib.rs

@@ -1,17 +1,19 @@
 //! alkcall: Call + channels RPC — operations, streaming, service discovery,
 //! and N-channel multiplexing over one transport stream.
 //!
-//! This crate unifies `alknet-call` (structured JSON RPC: operations,
-//! streaming subscriptions, service discovery) and `alknet-channels`
-//! (multiplexing proxy: N logical channels over one transport stream,
-//! channel 0 pre-negotiated as `alknet/call`).
+//! This crate is the unification of the call protocol (structured JSON RPC:
+//! operations, streaming subscriptions, service discovery) and the channels
+//! protocol (multiplexing proxy: N logical channels over one transport
+//! stream, channel 0 pre-negotiated as `alknet/call`). Both halves share
+//! the vendored core types and the call protocol's `OperationRegistry` —
+//! channel lifecycle is orchestrated by call operations on channel 0.
 //!
 //! ## Architecture
 //!
 //! - **Vendored core types** ([`core`]): `Connection`, `ProtocolHandler`,
 //!   `BiStream`, `BidiStreamSource`, `AuthContext`, `IdentityProvider`,
-//!   `Capabilities`, `OwnershipProvider` — the home for the former
-//!   `alknet-core` surface.
+//!   `Capabilities`, `OwnershipProvider` — the home for these types
+//!   going forward.
 //! - **Registry** ([`registry`]): operation specs, context, dispatch, and
 //!   the operation registry — the call half's dispatch core.
 //! - **Protocol** ([`protocol`]): wire format, streams, adapter, dispatch