glm-5.3-flash
ad63507124
Ride the alkcall 0.10 gateway ownership seam (review 012, ADR-048 amendment) into the door layer: - HttpAdapter::with_ownership_provider / HttpAdapter::with_static_ownership_fallback mirror alkcall's builder shape; OwnershipProvider re-exported next to GatewayDispatch - RouterState carries the wiring; GatewayState::dispatch is the single spine builder for both the gateway routes and the MCP nest - loud default passes through: a resource_type-gated op on an unwired spine is refused (FORBIDDEN envelope -> 403/401) on HTTP exactly as on the native wire - WS native-session path untouched (consults ownership natively) fix: with_ws_max_sessions never stored the fresh session-slot semaphore; later builder calls silently reverted the cap. Builder state now assembled through one router_state() helper. infra: fuzz/shared follows to alkcall 0.10 (two alkcall copies in one build would type-clash); alkhttp 0.8.0 per the dep-wave convention. Verification: cargo test (444 pass, incl. 3 new call_resource_gated_* HTTP-surface pins), clippy --all-targets -D warnings, fmt --check, test --all-features (520), fuzz corpus replay (21/21), doc.
alkhttp fuzzing
cargo-fuzz targets for the HTTP surface's hand-rolled parse paths. The
design and operating rules live in docs/plans/fuzzing.md (adopted
from alkcall's docs/research/fuzzing.md); this README is the
operational cheat-sheet.
Layout
fuzz_targets/— nightly-onlyfuzz_target!binaries (thin wrappers).shared/— stable-toolchain library holding the invariant logic; the corpus replay tests run here on plaincargo test.corpus/<target>/— committed seeds (regenerate withpython3 fuzz/gen_fuzz_seeds.py).artifacts/— gitignored crash/oom/timeout artifacts + campaign logs.
Targets
| Target | Drives |
|---|---|
sse_parser |
SseParser::feed + the FWD-17 envelope mapping (src/adapters/forward.rs) — the SSE frame parser every subscription forwards through |
ws_chunk_framing |
WriteChunkWalk (the write pump's chunk walk) (src/websocket/byte_adapter.rs) |
spec_import |
OpenAPISpec::from_str/from_yaml/from_json, the YAML normalization boundary, CompiledInputSchema compile/harden/validate, FromMCP::build_spec (src/adapters/openapi_spec.rs, input_validation.rs, from_mcp/mod.rs) |
ws_session_opseq |
stateful op sequences over the WS byte adapter's generic pumps (run_read_pump/run_write_pump over the mock socket flavor) — interleavings, close timing, loud-gate mapping, backpressure |
retry_throttle |
the inlined RetryAfterMiddleware's throttle map: capacity bound, eviction policy, ceiling clamp, refresh contraction, Retry-After parse partition |
Running a campaign — always detached
Agent sessions must never run fuzzing in the foreground (an OOM in a target can take down the session host; see docs/plans/fuzzing.md §2). Use the detached runner:
fuzz/run-detached.sh sse_parser
# poll:
tail -n 50 fuzz/artifacts/sse_parser-*.log
ls fuzz/artifacts/sse_parser/
pgrep -f "cargo fuzz run sse_parser"
FUZZ_RUNTIME_SECS=1800 fuzz/run-detached.sh sse_parser for a longer
campaign. The runner pins -fork=1 -rss_limit_mb=2048 -malloc_limit_mb=2048 -timeout=25 and detaches via setsid + nohup.
Corpus replay (the standing fuzz gate)
cargo test --manifest-path fuzz/shared/Cargo.toml
Replays every committed seed through the same invariant functions the fuzzer runs, on stable, no nightly needed. Part of the release verification checklist (AGENTS.md).
Toolchain notes
rust-toolchain.toml pins nightly for this subtree only (llvm-tools
required by cargo-fuzz); the crate itself stays on stable at MSRV 1.88.
cargo fuzz build must be run with the fuzz dir as CWD or trust the
toolchain file (rustup resolves per directory).
Run campaigns before releases and after touching src/adapters/forward.rs
(the SSE parser), src/websocket/byte_adapter.rs (the WS chunk walk),
or the import adapters (src/adapters/openapi_spec.rs,
input_validation.rs, from_mcp/).