fix: MCP manageGateway/queryGateway 工具 envId 绑定失效，导致模型浪费大量轮次

[binggg]

Attribution issue

• issueId: issue_mojcryx3_5bwnmf
• category: tool
• canonicalTitle: MCP manageGateway/queryGateway 工具 envId 绑定失效，导致模型浪费大量轮次
• representativeRun: atomic-js-cloudbase-cli-routes-lifecycle/2026-04-29T00-52-22-ysuwfx

Automation summary

• root_cause: The manageGateway and queryGateway tools used a synchronous ensureGatewayEnvId() function that only checked cloudBaseOptions?.envId directly. When cloudBaseOptions.envId was not set at tool registration time (common when envId is auto-resolved via login state, cache, or env vars), the tools threw "当前网关操作需要已绑定 envId" instead of resolving the envId. Other tools like manageFunctions correctly use the async getEnvId() which auto-resolves from multiple sources (cloudBaseOptions, cached envId, CLOUDBASE_ENV_ID env var, login state, or EnvironmentManager). This mismatch caused the model to waste many turns retrying gateway operations that always failed.
• changes: In mcp/src/tools/gateway.ts, replaced the synchronous ensureGatewayEnvId() with the async getEnvId() from cloudbase-manager.js. Changed getGatewayEnvId() → resolveEnvId() (returns Promise<string>), and updated all 5 call sites to await resolveEnvId(). Updated mcp/src/tools/gateway.test.ts to mock getEnvId with mockGetEnvId.mockResolvedValue("env-test").
• validation: All 9 gateway unit tests pass. All 10 regression tests (build-skills-repo, build-compat-config, skill-quality-stan

Changed files

• mcp/src/tools/gateway.test.ts
• mcp/src/tools/gateway.ts

[binggg]

Attribution post-PR evaluation

• visibility: internal identifiers, run ids, and private links are intentionally omitted
• attempt: 1
• eval_scope: primary_only
• overall: PASSED
• summary: all planned evaluation cases passed
• updated_at: 2026-04-29T01:19:35.915Z

Cases

• [PASSED] — primary — evaluation passed

[binggg]

OK