feat(infra): full-surface integration suite + docs sync + publish prep

Full-surface integration suite (tests/full_surface.rs, mcp feature):
- one HttpAdapter over real TCP (ProtocolHandler::handle path) serving
  gateway endpoints, /openapi.json, /mcp, and the WS channels session
- gateway: search/schema/call/subscribe/batch/publish presence,
  envelope shapes, error fidelity end-to-end
- from_openapi import -> Internal-by-default invisible from the wire ->
  External facade composes it via env.invoke -> upstream HTTP API
  called end-to-end (ADR-015 composition model exercised)
- to_openapi 6-path doc validated against openapiv3 over the wire
- to_mcp: MCP client connects to /mcp on the served adapter, lists the
  4 gateway tools, search returns ACL-filtered ops (Sub excluded)

Production fix: the WS upgrade route was reserved but never wired into
HttpAdapter's router (the ws-upgrade-session tests built their own
router). Now wired with ws_bearer_auth (401 without a resolvable
token) around ws_upgrade_handler.

Docs sync: all 28 'Port notes' sections/blockquotes stripped from
ported ADRs/specs; OQ-01/OQ-02 statuses corrected to resolved in
overview.md, websocket.md, and the README table (open-questions.md was
already current).

Publish prep: cargo publish --dry-run --allow-dirty succeeds;
cargo doc --no-deps warning-free (ADR link targets fixed); feature
combinations (default / test-support / mcp / wss / all) compile
warning-free under clippy -D warnings.

Verified: cargo test (182 lib default), --all-features (227 lib + 29
integration), clippy -D warnings x3 feature sets, fmt, doc,
publish --dry-run.

docs/architecture/decisions/051-yaml-input-for-from-openapi.md

@@ -221,21 +221,3 @@ additive (a new endpoint, no breaking change to the JSON path). The
   `docs/architecture/`)
 - `yaml_serde` crate (https://github.com/yaml/yaml-serde) — the maintained
   official-YAML-org fork of the deprecated `serde_yaml`
-
-## Port notes
-
-- Renames: "alknet-http" → alkhttp throughout (§3's "the dependency is not
-  feature-gated" paragraphs, Consequences, §3's "alknet-http uses the direct
-  form" → "alkhttp uses the direct form").
-- Link path fixes: `../crates/http/http-adapters.md` → `../http-adapters.md`
-  (the spec now lives in this crate's `docs/architecture/`). Cross-ADR links
-  (ADR-017, ADR-023, ADR-039) point at `decisions/NNN-<slug>.md` with the
-  alknet slugs; ADR-017 and ADR-023 are ported here under the same numbers
-  (their decision records live in alkcall as ADR-022 and ADR-016
-  respectively — noted inline).
-- No producer/consumer or `Sub`/`Pub` terminology appears in the original —
-  nothing to retarget on those axes.
-- No decision content changed — the constructor set, the JSON-first
-  YAML-fallback rule, the `yaml_serde` dependency choice and its
-  non-feature-gating, the 2026-07-06 rationale amendment, and the
-  `to_openapi`-stays-JSON scope boundary are verbatim from the alknet ADR.