docs: re-key architecture docs off the alknet mono-repo — speak as alkcall

The ported docs still framed alknet siblings (alknet-core/-call/-channels/
-http/-tls/-client) as live load-bearing context of this crate. With the
extraction complete and alknet headed for glue-level replacement, the docs
now speak as alkcall and cite the real sibling crates (alkhttp, alktls,
alktty, alktunnels, alktrader).

- ADR-054 (new): re-own the verifier-selection rule in-crate — three
  remote roles (public X.509 endpoint / transport relay / hub),
  ServerCertVerifier by PeerEntry presence, RemoteIdentity None
  load-bearing. Provenance: alknet ADR-034 (never ported), demoted to
  footnote. Resolves OQ-21's cross-repo authority gap.
- OQ-43 (new, deferred(scope)): composition-layer ownership and shape
  after the alknet replacement — the named receiver for the
  downstream-side deferrals (OQ-33 endpoint layer, OQ-41 QUIC-native
  substrate, OQ-42 hub broker, OQ-19 persistence adapters, ADR-045 dial
  seam). README layering diagram redrawn with the composition layer as
  TBD-ownership instead of "alknet / alknode" in concrete.
- Spec docs reframed: titles, self-references, dial/TLS/from_jsonschema
  homes, malformed legacy cite rows removed; dead relative research
  paths qualified as source-repo paths.
- ADR amendments (append-only): 027 (alknet-http -> alkhttp), 031 (post-
  extraction state), 044 (split landed as modules in alkcall), 045
  (name normalization; citation-space note).
- Citation hygiene: unprefixed/colliding source-repo cites prefixed
  ("alknet ADR-NNN (provenance)") across 009/011/022/034/035/038/040/
  043/044/045; stale OQ cites corrected (session registries OQ-04, batch
  semantics OQ-03, verifier rule ADR-054); stale anchors fixed.
- README provenance note consolidated; citation conventions documented.

Verification: markdown link check (all local links resolve, all in-crate
ADR cites point at existing decisions/ files); table integrity check
(uniform row widths across open-questions.md and edited tables); residual
alknet-mention sweep (only provenance/historical/intentional framing
remains); architecture review subagent pass with zero remaining criticals.
Docs-only change — no code paths touched.

docs/architecture/channel-operations.md

@@ -1,6 +1,6 @@
 ---
 status: current
-last_updated: 2026-10-13
+last_updated: 2026-10-13 (alkcall reframing)
 ---
 
 # channel-operations.md — Channel Lifecycle on the Call Protocol
@@ -217,7 +217,7 @@ decrement.
 chunks MUST be written and flushed before the `channel/close` operation
 is sent on channel 0. The side closing must observe the data-channel
 pump complete before issuing the call operation. For TTY this is the
-exit-chunk-is-last invariant (ADR-055) carried forward — the exit
+exit-chunk-is-last invariant (alknet ADR-055, provenance) carried forward — the exit
 control message rides on TTY's `STREAM_CTRL_OUT` (stream_type 4, inside
 TTY's 5-byte payload format); for tunnels it is the last data byte
 before close. This invariant crosses two channels (the data channel and
@@ -327,7 +327,7 @@ would pressure consumers toward the stale-poll path.
 | Call operations on channel 0 (`channel/control`, `channel/close`) | Control that doesn't need ordering relative to data, or lifecycle events | resize, signal, keepalive, close |
 | Data-ordered bytes on the data channel's `BiStream` (handler-internal framing) | Control that MUST be ordered relative to data | EOF before exit, flush before close |
 
-The TTY crate's exit-chunk-is-last invariant (ADR-055) is the canonical
+The TTY crate's exit-chunk-is-last invariant (alknet ADR-055, provenance) is the canonical
 example of data-ordered control — it rides on TTY's `STREAM_CTRL_OUT`
 (stream_type 4, inside TTY's 5-byte payload format) because it must
 arrive after the last data on TTY's stdout stream_type, guaranteed by