From 522fd3cee5d9f4b4112493982f9604968f93de85 Mon Sep 17 00:00:00 2001 From: Shaojin Wen Date: Mon, 18 May 2026 13:54:38 +0800 Subject: [PATCH] fix(serve): add mcp_guardrails to E2E capabilities expectation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR #4247 (`feat(serve): MCP client guardrails`) added the always-on `mcp_guardrails` capability to `SERVE_CAPABILITY_REGISTRY` and updated the unit-level `EXPECTED_STAGE1_FEATURES` in `packages/cli/src/serve/server.test.ts`, but missed the matching integration-test expectation. The E2E `qwen serve — capabilities envelope > advertises all baseline capabilities` assertion has been failing on `main` since #4247 landed. Append `'mcp_guardrails'` to the expected `caps.features` array, in the same position as `SERVE_CAPABILITY_REGISTRY` and the unit-level constant (after `session_metadata`, before the conditional `require_auth`). No production code changes. --- integration-tests/cli/qwen-serve-routes.test.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/integration-tests/cli/qwen-serve-routes.test.ts b/integration-tests/cli/qwen-serve-routes.test.ts index 3eeca4edd..f8a1c02c0 100644 --- a/integration-tests/cli/qwen-serve-routes.test.ts +++ b/integration-tests/cli/qwen-serve-routes.test.ts @@ -214,6 +214,7 @@ describe('qwen serve — capabilities envelope', () => { 'session_supported_commands', 'session_close', 'session_metadata', + 'mcp_guardrails', ]); }); });