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/decisions/031-crate-decomposition.md

@@ -140,4 +140,31 @@ The dead `irpc` / `irpc-derive` workspace deps and the `alknet-call` consumer
 dep were removed in commit `668d777`. See
 [ADR-014](014-irpc-never-integrated-hand-rolled-framing.md) for the full
 record (ADR-013, which accepted "irpc as the call protocol foundation," is
-superseded).
+superseded).
+### Amendment 4 (2026-10-13): post-extraction state — alkcall is the unified protocol crate; sibling names normalized
+
+The decomposition this ADR decided has been executed; this section
+records where the named crates now live, so the decision text's
+mono-repo framing reads as history:
+
+- **alkcall** (this crate) is the unified extraction of `alknet-call`
+  + `alknet-channels` + the vendored core types (the `alknet-core`
+  surfaces this crate's protocol depends on: `Connection`,
+  `BiStream`, `ProtocolHandler`, `AuthContext`, `IdentityProvider`,
+  `AuthToken`, `Capabilities`, `OwnershipProvider`, `HandlerError`,
+  `StreamError`). Two subsystems: `registry`/`protocol` (call) and the
+  channels subsystem (ADR-044's `channels-core`/`channels-call` split
+  landed as modules here).
+- **Sibling host crates** (now standalone, all depending on alkcall):
+  `alknet-http` → `alkhttp`; `alknet-tls` → `alktls`;
+  `alknet-tty` → `alktty`; `alknet-tunnels` → `alktunnels`;
+  `alknet-trader` → `alktrader`.
+- **The mono-repo (alknet) is being replaced** by thin glue over
+  alkcall and its siblings; its remaining roles (dial/accept helper
+  `AlknetClient`, endpoint layer, hub composition) move to the
+  composition layer — post-replacement owner and shape tracked as
+  OQ-43 in this crate's question tracker.
+- The protocol-foundation rule (Amendment 1) carries over unchanged
+  with current names: `alkhttp` depends on alkcall for operation
+  registry / adapter / client types; peer-handler crates (e.g.
+  `alktty`, `alktunnels`, `alktrader`) depend on alkcall only.