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/045-alknetclient-native-dial-seam.md

@@ -21,7 +21,7 @@ reader); `auth_token` is a per-request payload field; the `from_call`
 OQ-55 deferred `AlknetClient::dial()` — the transport-polymorphic client
 dial seam — blocked on "a second transport's real dial existing." The
 reasoning (recorded in the OQ-55 file and in
-[channel-client.md](../crates/channels/channel-client.md) §"Relationship
+[channel-client.md](../channel-client.md) §"Relationship
 to `AlknetClient`") was sound at the time: extracting a QUIC-shaped
 connector and naming it `AlknetClient` would bake QUIC in as *the*
 establishment shape — the same welding ADR-007 unwound on the server
@@ -528,24 +528,24 @@ dedicated ADR lands.
 
 - OQ-55 (resolved by this ADR) — `AlknetClient` / client establishment
   extraction
-- [ADR-083](083-endpoint-as-accept-loop-runner.md) — `AlknetEndpoint`
+- [ADR-083](/workspace/@alkdev/alknet/docs/architecture/decisions/083-endpoint-as-accept-loop-runner.md) — `AlknetEndpoint`
   as multi-transport accept-loop runner; the server-side shape this
   ADR mirrors on the client side
-- [ADR-086](086-endpoint-types-and-entry-points.md) — endpoint types
+- [ADR-086](/workspace/@alkdev/alknet/docs/architecture/decisions/086-endpoint-types-and-entry-points.md) — endpoint types
   (native has QUIC + TCP+TLS + iroh); entry-point vs. endpoint ALPN
   distinction (§2)
-- [ADR-087](087-tlsclientconfig-not-blocked-on-dial.md) —
+- [ADR-087](/workspace/@alkdev/alknet/docs/architecture/decisions/087-tlsclientconfig-not-blocked-on-dial.md) —
   `TlsClientConfig` not blocked on the dial seam; breaks the circular
   hedge; the TLS config is a prerequisite for the dial
-- [ADR-082](082-alknet-tls-extraction.md) — `TlsServerConfig` /
+- [ADR-082](/workspace/@alkdev/alknet/docs/architecture/decisions/082-alknet-tls-extraction.md) — `TlsServerConfig` /
   `TlsClientConfig` in `alknet-tls`; "iroh shares the key, not the
   config"
 - [ADR-007](007-connection-from-stream-generic-single-stream.md) —
   `Connection::from_stream` / `from_bidi`; the server-side
   generalization whose client-side analogue this ADR completes
-- [ADR-034](034-outgoing-only-x509-and-three-peer-roles.md) —
+- [ADR-034](/workspace/@alkdev/alknet/docs/architecture/decisions/034-outgoing-only-x509-and-three-peer-roles.md) —
   client-side verifier selection (fingerprint pin vs CA vs fail-closed)
-- [ADR-084](084-aws-lc-rs-crypto-provider.md) — aws-lc-rs crypto
+- [ADR-084](/workspace/@alkdev/alknet/docs/architecture/decisions/084-aws-lc-rs-crypto-provider.md) — aws-lc-rs crypto
   provider on all paths
 - [ADR-043](043-channelclient.md) — `ChannelClient::from_connection`
   (the take-over `AlknetClient` feeds)