docs(architecture): remove removed-thing remnants from spec docs

Spec docs should describe WHAT IS, not WHAT WAS. ADRs and OQ files are
historical records by design and are left alone; the ADR-index Status
column records ADR status (stable fact). What changed in the specs:

- API code blocks no longer list removed methods. ChannelClient::connect_quic
  (channel-client.md) and CallClient::connect (client-and-adapters.md) are
  gone from the impl blocks; surrounding prose describes the current
  from_connection / spawn_dispatch primary + AlknetClient dial shape.
- Amendment (ADR-093): stream_types field is removed blockquotes dropped
  from channel-client.md and channel-operations.md (the code already
  reflects the current state).
- Historical is-removed / reversed-by / amended-by prose rewritten to
  current state across channels crate, call crate, hub, tls, core,
  endpoint, client READMEs, and the top-level README/overview.
- Dropped the EndpointError — removed subsection from endpoint/README.md
  (the type doesn't exist anymore, so it shouldn't have a subsection).
- Replaced stale connect() references in flow descriptions with the dial
  (in AlknetClient) since connect() is no longer a method.
- Removed strikethrough ADR-028 / from_jsonschema-clause rows from
  client-and-adapters.md and operation-registry.md ADR tables.
- Rewrote the ADR-066 update blockquote in operation-registry.md to
  describe FromJsonSchema's current shape.

19 files modified, net -116 lines. No ADRs or OQ files touched.

docs/architecture/crates/tls/README.md

@@ -165,9 +165,9 @@ copies in `alknet-tls`, used by both `TlsServerConfig::new` and
 across the server (in core's endpoint module) and the client (in call's
 client module); the extraction consolidated them.
 
-`CallClient::connect` is removed (ADR-089 §5) — the dial is in
-`AlknetClient` (`alknet-client`); `CallClient` keeps only
-`spawn_dispatch`, and `alknet-call` has no TLS/transport deps.
+The dial is in `AlknetClient` (`alknet-client`, ADR-089);
+`CallClient` keeps only `spawn_dispatch`, and `alknet-call` has no
+TLS/transport deps.
 
 ### `TlsServerConfig`
 
@@ -645,9 +645,8 @@ arrive asynchronously and are logged (ADR-082 §"Behavior-preservation
 invariants").
 
 **Ownership.** `TlsError` lives in `alknet-tls`, owned by the crate
-that produces it. It is not re-exported from `alknet-core`; there is no
-`EndpointError` (removed per ADR-083 — both variants were vestigial),
-so core has no endpoint error type and does not need to know about
+that produces it. It is not re-exported from `alknet-core`; core has
+no endpoint error type, so core does not need to know about
 `TlsError`. The assembly layer (hub/worker) depends on `alknet-tls`
 directly and gets `TlsError` from that dependency.
 
@@ -662,8 +661,7 @@ alknet-core (lightweight — types + auth + config + fingerprint + credentials)
 
 alknet-call (pure protocol crate — no TLS/transport deps per ADR-089 §5)
 └── alknet-core (ProtocolHandler, Connection, types; ConnectionCredentials/
-    RemoteIdentity from core per ADR-091; CallCredentials removed per
-    ADR-091 Am. 2026-07-17)
+    RemoteIdentity from core per ADR-091)
 
 alknet-hub (multi-transport endpoint)
 ├── alknet-tls (TlsServerConfig — shared across quinn + TCP)
@@ -762,12 +760,10 @@ ALPNs via channel 0). Both consume `TlsClientConfig` through the dial
 for TCP+TLS); iroh is the exception (shares the key, not the config).
 `AlknetClient` is the dial that feeds them — it produces a `Connection`
 and the protocol take-overs (`spawn_dispatch`, `from_connection`)
-consume it. The per-protocol QUIC convenience constructors
-(`CallClient::connect` / `ChannelClient::connect_quic`) are removed
-per ADR-089 §5 — the dial is centralized in `AlknetClient`, and the
+consume it. The dial is centralized in `AlknetClient` (ADR-089); the
 protocol crates have no TLS/transport deps. The `alknet/register` ALPN
-(native registration entry point, parallel to HTTP registration in
-OQ-58) is named by ADR-089; its wire protocol is deferred (OQ-66).
+(named by ADR-089; wire protocol deferred, OQ-66) is the native
+registration entry point, parallel to HTTP registration in OQ-58.
 
 ## References