CI / UI Checks (pull_request) Successful in 11s
CI / Rust Checks (pull_request) Successful in 9m2s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
The Story 3.18 logging arm pushed `crates/crank-community-mcp/src/app/endpoint.rs` to 1058 lines, so `scripts/check-rust-code-health.sh` failed the Required CI (Rust Checks, run 870 / job 2408) at the pinned 1000-line default. Move the whole legacy-era dispatch of `mcp_post_response` verbatim into `app/legacy_dispatch.rs` (`handle_legacy_request`), leaving the endpoint as the transport/admission layer it documents itself to be. endpoint.rs is now 381 lines and the new module 731, both inside the limit; no baseline pin and no check was touched. Behaviour is unchanged: the moved match keeps every arm, envelope, status code and safe detail as-is (legacy-only logging/setLevel, -32602 INVALID_LEVEL, EVENT_LEVEL_APPLIED Notice acknowledgment, per-session level isolation), the pre-dispatch legacy level read stays in `mcp_post_response`, and the only edits to the moved text are the mechanical `&credential` -> `credential` (the credential now arrives as a reference) and `protocol_version` already being `Option<&str>`.