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/046-assembly-layer-custom-http-routes.md

@@ -250,19 +250,3 @@ deployment-specific addition on top, not a modification of it.
   as a custom route projection; this ADR §4 is the mechanism)
 - `http-server.md` — the `HttpAdapter` spec that gains the
   `extra_routes` constructor parameter (now in `docs/architecture/`)
-
-## Port notes
-
-- Link path fixes: `crates/http/http-server.md` → `http-server.md` in
-  `docs/architecture/` (referenced both in the Context and in the
-  References). Cross-ADR links (ADR-010, ADR-042, ADR-045, ADR-047)
-  point at `decisions/NNN-<slug>.md` with the alknet slugs; ADR-042,
-  ADR-045, and ADR-047 are being ported by other agents under the same
-  numbers and will exist. ADR-036 is referenced by number/text only
-  (its mapping decision is superseded by ADR-047).
-- `resolve_from_token` on a Bearer header is the `IdentityProvider`
-  path defined in ADR-004 (ported here under the same number);
-  `IdentityProvider` internals are alkcall-internal.
-- No decision content changed — the `extra_routes` mechanism, reserved
-  paths, auth middleware, and versioning rules are verbatim from the
-  alknet ADR.