docs: spec-level sync with the single-publish fix + port-debt repair

The spec docs had not caught up with the stub-sweep fix commits
(4eae18f..3317ea0), and the ported docs still carried alknet
numbering that now collides with alkcall's own ADR range.

Spec sync with the landed code:
- call-protocol.md: register_imported/register_imported_all return
  Result and refuse marked specs; marked-spec registration refusal
  contract spelled out (ADR-047 am. 4 §4.8, ADR-022 am. 2026-10-13)
- client-and-adapters.md: from_call flow gains the Pub sink-forwarding
  branch and the marked-op refusal (resolves OQ-37 — no from_call
  relay wrapper; sanctioned compositions are
  ChannelRelay::register_relay_openable / ChannelClient)
- ADR-051: "channel/control is not implemented" stale sentence
  replaced with the ADR-052 per-leg control contract
- OQ-37 resolved; OQ-22 split (primitive resolved; broker placement
  out of scope) with new OQ-42 for the downstream hub broker
  (deferred(scope), concretely blocked); OQ-24 resolved by the shipped
  add/strip surface; OQ-41 → deferred(scope) with blocking condition
- README: OQ bullets renumbered to tracker IDs; alknet-collision note
  rewritten (range 001..053, alknet prefix convention); new principle
  11 (implement-or-stop-advertising); AGENTS.md ADR range 001..053

Port-debt repair:
- 149 broken decision links across 17 docs — ported with alknet
  numbers/paths, most now remapped to alkcall files by slug; the
  rest link the alknet repo per the README convention
- stale OQ numbering rewritten to tracker IDs in call-protocol.md,
  call-README.md, operation-registry.md, client-and-adapters.md,
  ADR-025, channels-overview/README/wire, channel-client
- unambiguous "alknet ADR-NNN" labels where an alknet number collides
  with an alkcall ADR (052 TTY vs channel/control, 033 storage vs
  rust-canonical, 025/026/027+020 vault vs PeerEntry/auth ADRs)

Verified: cargo test (697 + guard), fmt, clippy --all-targets -D
warnings; full markdown link scan clean.

docs/architecture/channels-overview.md

@@ -89,7 +89,7 @@ on the `BiStream` the channels layer gives them (ADR-035).
   inner layer's framing byte, carried transparently in the payload.
 - **The control channel is handler-internal.** TTY sub-demuxes control
   from its io `BiStream` using its 5-byte format (`STREAM_CTRL_IN` /
-  `STREAM_CTRL_OUT` — ADR-052 amended by Phase 7). The channels layer
+  `STREAM_CTRL_OUT` — alknet ADR-052 amended by Phase 7). The channels layer
   doesn't carry control.
 - **Recursive composition is literal.** A channel with ALPN
   `alk/channels` runs another channels demux on its `BiStream`. The
@@ -270,18 +270,19 @@ All design decisions are documented as ADRs in [decisions/](decisions/).
 Open questions are tracked in [open-questions.md](open-questions.md).
 Key questions affecting this crate:
 
-- **OQ-55** (resolved by ADR-045): `AlknetClient` core **dial+TLS seam**
+- **alknet OQ-55** (resolved by ADR-045): `AlknetClient` core **dial+TLS seam**
   — extracted as `alknet-client` with three dial methods.
   `ChannelClient`'s API is transport-agnostic (`from_connection`); the
   dial is the shared seam, now extracted. See
   [ADR-045](decisions/045-alknetclient-native-dial-seam.md).
-- **OQ-56** (deferred(scope)): Full channel-level flow-control windowing —
+- **OQ-23** (tracker; alknet OQ-56) (deferred(scope)): Full channel-level flow-control windowing —
   bounded-buffer is decided (ADR-040); full windowing is an extension
   blocked on a real HOL-blocking deployment observation.
-- **OQ-57** (deferred(scope)): Two-pump helper extraction to alknet-core —
-  the *contract* is decided (ADR-078); the *helper* is blocked on a second
-  two-pump handler existing.
-- **OQ-68** (open): Add/strip API shape — whether the 8-byte header
+- **alknet OQ-57** (deferred(scope)): Two-pump helper extraction to alknet-core —
+  the *contract* is decided (the in-tree helper landed as
+  `channels::pump_bidi`, ADR-050); any extraction to alknet-core is
+  alknet-scope.
+- **OQ-24** (tracker; alknet OQ-68) (resolved): Add/strip API shape — whether the 8-byte header
   add/strip is built into the channels read/write path or exposed as a
   standalone utility. The *contract* (channels strips, handler parses
   payload) is decided (ADR-035); the *function surface* is not.