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.
This commit is contained in:
2026-08-28 16:07:56 +00:00
parent bc99ec7188
commit 4a825d33e7
41 changed files with 700 additions and 1035 deletions
@@ -668,38 +668,3 @@ the fuzzer validates the implementation against the spec.
- Kernel/user mode analogy: `getaddrinfo` runs under kernel authority, not
the caller's `CAP_NET_RAW`; the curated entry point exists to do things
the user can't, on the user's behalf
## Port notes
- Renames: "alknet-http" → alkhttp; "alknet-core"/"alknet-call" → alkcall.
- Cross-reference remappings (verified alknet→alkcall ADR mapping): alknet
ADR-016 (abort cascade) → alkcall ADR-020; alknet ADR-024 (registry
layering) → alkcall ADR-019; alknet ADR-017 (adapter contract) → alkcall
ADR-022 (ported here as ADR-017). ADR-014 and ADR-015 are ported to this
crate under the same numbers and linked.
- `from_jsonschema` correction (per alkcall ADR-027 / this crate's ADR-066):
the `FromJsonSchema` enum-doc comment and the ADR-066 amendment block now
say the adapter lives in **alkhttp** (the original said `alknet-http`, which
is the same crate post-extraction — updated to the current name rather than
left as a stale reference). The superseded-ADR citation inside the
alkcall-crate copy of this ADR cites alkcall ADR-027; the alknet-record
original cited alknet ADR-066.
- "QUIC forwarding stub (from_call)" → "Call-protocol forwarding stub
(from_call)" — the call protocol is transport-agnostic (alkcall ADR-007);
the original wording predates the transport-agnostic connection model.
Assumption 5's "over HTTP, MCP, or QUIC" → "over HTTP, MCP, or the call
protocol".
- Review paths (`docs/reviews/...`) are alknet mono-repo artifacts; annotated
as such rather than converted to links (the reviews are not ported to
alkhttp).
- alknet OQ-19 is an alknet-record citation (alkcall's OQ numbering differs).
- alknet ADR-008 is cited textually (alknet mono-repo ADR; the vault is an
alkvault concern).
- The flowgraph references are kept as absolute workspace paths (the
directories still exist); "a dedicated `alknet-flowgraph` crate" → "a
dedicated flowgraph crate" (hypothetical crate name genericized, matching
the alkcall-crate copy of this ADR).
- No decision content changed — the provenance model, `CompositionAuthority`,
`ScopedOperationEnv`, the `HandlerRegistration` bundle, the dispatch-path
wiring, the no-intersection rule, and the ADR-066 amendment are verbatim
from the alknet ADR modulo the corrections logged above.