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/042-openapi-gateway-pattern.md

@@ -289,47 +289,3 @@ require it for the common case.
 - `http-adapters.md` (in this crate's `docs/architecture/`) — the spec
   that implements the gateway (alknet original:
   `crates/http/http-adapters.md`)
-
-## Port notes
-
-- Renames: "alknet" → alkhttp where the system/node being described is
-  meant; "alknet-call" (protocol-foundation crate) → alkcall.
-- `OperationType::Subscription` → `Sub` in the gateway endpoint table,
-  §2, and throughout (alkcall rename). alkcall ADR-046 added
-  `OperationType::Pub` (producer→consumer streaming, `HandlerKind::Sink`);
-  the original 5-endpoint table predates `Pub` and is preserved verbatim
-  as decision history — the `/publish` extension is marked as an alkhttp
-  addition (ADR-068), never silently rewritten.
-- **Gateway endpoint count**: the alknet record's "5 endpoints" is
-  preserved everywhere as the original decision; alkhttp's `/publish`
-  extension (ADR-068) is noted inline at each site where the count
-  matters (§1, §3, §4, Assumption 1, Context). "Never rewrite history"
-  framing: the published initial contract remains the 5-endpoint set;
-  `/publish` is an additive extension under the contract's own
-  additivity rule (§4, Assumption 1).
-- Producer/consumer terminology: "an admin sees admin operations, a
-  regular user sees a subset" and similar retain their names — no
-  call-protocol server/client role framing existed in the original
-  body. The external client roles (code generator, human developer,
-  `fetch`-based client, Gitea-style API consumers) are inherent-directionality
-  roles of the HTTP/OpenAPI surface and keep their names.
-- Cross-reference remappings: ADR-015/017/023 are ported to this crate
-  under the same numbers and linked; their alkcall record numbers are
-  noted alongside (015→alkcall ADR-017, 017→alkcall ADR-022,
-  023→alkcall ADR-016). ADR-041 is cited textually with its alknet
-  number (the MCP gateway pattern; not part of this port's 3 files —
-  verify the alkhttp port's existence when linking).
-- OQ references (OQ-14, OQ-39) are alknet OQ-tracker items, cited
-  textually; OQ-39 is resolved by [ADR-045](045-to-openapi-gateway-spec-versioning.md)
-  (ported to this crate under the same number).
-- Spec-document links converted per alkhttp conventions:
-  `crates/http/http-adapters.md` → `http-adapters.md` in this crate's
-  `docs/architecture/`; `websocket.md`/`webtransport.md` were alknet
-  mono-repo spec-tree documents — the WS path here is the native
-  call-protocol session (ADR-048) and no deferred WebTransport spec is
-  carried (ADR-044).
-- No decision content changed — the flat→structured problem, per-caller
-  surface problem, gateway pattern, the 5-endpoint table, the `subscribe`
-  SSE semantics, `POST`-not-`GET` rationale, compatibility-contract
-  clause, additive traditional projection, consequences, and assumptions
-  are verbatim from the alknet ADR modulo the adaptations above.