feat(logs): expose searchClsLog-compatible log query entry

[binggg]

Signal

• Attribution: issue_mnt9nu7f_yh77wx
• Run: atomic-js-cloudbase-cli-log-query-by-request-id/2026-04-11T00-48-39-nszg86
• Score / failure: overall 0.924; only failed check is API verification for searchClsLog compatibility

Why this is actionable

• Relevant module: mcp/src/tools/logs.ts, mcp/src/server.ts
• Current behavior: MCP exposes queryLogs(action="searchLogs"), but the canonical CloudBase manager API name searchClsLog is not exposed as a direct tool entry. In the representative trace the model never discovered queryLogs; it fell back to queryFunctions log listing/detail calls instead.
• Expected behavior: models and evaluators that already know the canonical searchClsLog concept should be able to find and use a direct MCP entry without translating through queryLogs(action="searchLogs").

Proposed direction

• Add a direct read-only searchClsLog tool alias that maps to the existing log search handler
• Keep queryLogs for higher-level entry, but clarify in tool metadata/docs that queryLogs(action="searchLogs") is the same underlying capability as searchClsLog
• Regenerate tool docs/artifacts and add focused tests for the alias

[github-actions]

🤖 AI Fix Attempt

I created a PR for this bug: #519

Please review the generated changes before merging.