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/client/call_client.rs

@@ -12,10 +12,10 @@
 //! `abort()`) and a callee (dispatches incoming calls against its registry).
 //!
 //! Transport-level connection establishment (QUIC dial, TCP+TLS, iroh) is
-//! handled by `alknet-client`; `CallClient::spawn_dispatch` takes a
+//! handled by the consumer; `CallClient::spawn_dispatch` takes a
 //! pre-established `Connection` and runs the call protocol over it.
 //!
-//! See `docs/architecture/crates/call/client-and-adapters.md` for the spec.
+//! See `docs/architecture/` for the spec.
 
 use std::sync::Arc;
 

src/client/from_call.rs

@@ -7,7 +7,7 @@
 //! implemented in `registry/discovery.rs`; `from_call` is the client-side
 //! consumer of that API.
 //!
-//! See `docs/architecture/crates/call/client-and-adapters.md` §from_call for
+//! See `docs/architecture/` §from_call for
 //! the spec and the v1 defaults (auto-on-reconnect, error-on-collision).
 
 use std::collections::HashSet;

src/client/mod.rs

@@ -1,10 +1,8 @@
 //! Client adapters: turn external operation sources (JSON Schema, OpenAPI,
 //! MCP, remote `from_call` peers) into `HandlerRegistration` bundles.
 //!
-//! See `docs/architecture/crates/call/client-and-adapters.md` for the
-//! OperationAdapter trait and the Adapter Location Map, and
-//! `docs/architecture/decisions/017-call-protocol-client-and-adapter-contract.md`
-//! §5 for the trait contract.
+//! See `docs/architecture/` for the OperationAdapter trait and the Adapter
+//! Location Map, and ADR-017 §5 for the trait contract.
 
 mod call_client;
 mod from_call;
@@ -55,8 +53,7 @@ pub enum AdapterError {
 /// `from_openapi` reading a static spec) trivially satisfy
 /// an async trait — their `import()` bodies contain no `.await` points.
 ///
-/// See ADR-017 §5 (`docs/architecture/decisions/017-call-protocol-client-and-adapter-contract.md`)
-/// and `docs/architecture/crates/call/client-and-adapters.md`.
+/// See ADR-017 §5 and `docs/architecture/`.
 #[async_trait::async_trait]
 pub trait OperationAdapter: Send + Sync {
     async fn import(&self) -> Result<Vec<HandlerRegistration>, AdapterError>;

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

src/protocol/adapter.rs

@@ -2,8 +2,7 @@
 //!
 //! Accepts bidirectional streams, reads `EventEnvelope` frames, and
 //! dispatches `call.requested` events to the operation registry. See
-//! `docs/architecture/crates/call/call-protocol.md` for the full
-//! specification.
+//! `docs/architecture/` for the full specification.
 //!
 //! The dispatch loop is shared with [`crate::client::CallClient`] via
 //! [`super::dispatch::Dispatcher`] (ADR-017 §1): `CallAdapter` is the

src/protocol/connection.rs

@@ -2,8 +2,7 @@
 //! direction — accepted or opened). Holds the connection's Layer 2 overlay
 //! (imported ops).
 //!
-//! See `docs/architecture/crates/call/call-protocol.md` for the full
-//! specification.
+//! See `docs/architecture/` for the full specification.
 
 use std::collections::HashMap;
 use std::pin::Pin;

src/protocol/dispatch.rs

@@ -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;

src/protocol/mod.rs

@@ -1,8 +1,7 @@
 //! Call protocol: wire format, streams, and the call adapter.
 //!
 //! Implements `ProtocolHandler` for ALPN `alknet/call` on top of the
-//! operation registry. See `docs/architecture/crates/call/call-protocol.md`
-//! for the full specification.
+//! operation registry. See `docs/architecture/` for the full specification.
 
 pub mod abort;
 pub mod adapter;

src/protocol/wire.rs

@@ -1,8 +1,7 @@
 //! Wire format: `EventEnvelope`, `ResponseEnvelope`, `CallError`, and
 //! length-prefixed JSON framing.
 //!
-//! See `docs/architecture/crates/call/call-protocol.md` for the full
-//! specification.
+//! See `docs/architecture/` for the full specification.
 
 use std::io;
 

src/registry/spec.rs

@@ -1,8 +1,7 @@
 //! Operation specifications: `OperationSpec`, `OperationType`, `Visibility`,
 //! `ErrorDefinition`, and `AccessControl`.
 //!
-//! See `docs/architecture/crates/call/operation-registry.md` for the full
-//! specification.
+//! See `docs/architecture/` for the full specification.
 
 use crate::core::auth::Identity;
 use crate::core::ownership::OwnershipProvider;