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/decisions/051-channel-relay-and-hub-leg.md

@@ -82,9 +82,12 @@ Consumer-side close → wrapper teardown → pump abort → send-half drop →
 EOF chunk → spoke handler exits → spoke's own wrapper decrements its
 ledger. Close propagates through the EOF cascade with correct ledger
 accounting on both legs; the hub never sees a `channel/close` to
-translate. Control stays per-leg (`channel/control` is not implemented
-upstream, OQ-39 — a hub wanting cross-leg control translation composes
-it downstream). This supersedes the ADR-042 §mapping bullet's
+translate. Control stays per-leg (ADR-052): the control surface is
+establisher-contributed (`Establishment::with_control`) on each leg's
+own allocation — the hub never relays a `channel/control` between legs;
+a hub wanting cross-leg control composes it with the per-leg control
+handles, not with a translation surface. This supersedes the ADR-042
+§mapping bullet's
 close-translation sentence as an implementation matter: the mapping
 entry the sentence's removal depended on does not exist.