[SaladDay]

Claude Code's native WebSearch and WebFetch are live search, and a workspace placement already keeps them unless web_search is disabled. Until now the declaration rejected an explicit live tool, so an Agent that asked for the official default could not run on Claude Code.

• The Claude declaration admits web_search modes disabled and live. Native search has no cached mode and no settings, so cached and non-default context_size, allowed_domains or location stay rejected through the shared validation.
• environment: none runs no native tools, so live there is rejected: Core admission refuses it with a typed message, and the Runtime refuses a live control without a dedicated workspace instead of dropping it.
• The execution-tools table, the Harness capability table and the public guide's tool list are updated in English and Chinese.

Checks

• go test for apps/daemon/internal/agent/claudesdk, internal/harnessconfig/..., services/core/internal/execution and services/core/internal/api; go vet on the touched modules. The two new tests fail without the change.
• make check-docs, make check-harness-catalog, website translation tests.
• Live run through the Claude workspace adapter with MiniMax-M3 on the Anthropic-compatible endpoint: with live, the model called native WebSearch and WebFetch, both completed, and the Runtime reported them as web_search observations with search and open_page actions. With disabled, the model reported no search tool. This ran on the Runtime adapter, not through the official client on a hosted placement, so the capability table lists live as admitted.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}