Fix docs lint blockers for deployment

Author: jiayuqi7813

benchmark_reports/zcp_mcp_tool_call_benchmark.md

@@ -18,4 +18,4 @@
 | warmer_city_delta | 2821.0 | 4579.5 | 1758.5 | 1.62x | 100.0% | 100.0% |
 | shanghai_temp_f_and_humidity | 2565.0 | 3834.5 | 1269.5 | 1.49x | 100.0% | 100.0% |
 | average_three_city_temperature | 3116.0 | 5237.5 | 2121.5 | 1.68x | 100.0% | 100.0% |
-| more_humid_city_delta | 2830.0 | 4364.0 | 1534.0 | 1.54x | 100.0% | 100.0% |
+| more_humid_city_delta | 2830.0 | 4364.0 | 1534.0 | 1.54x | 100.0% | 100.0% |

docs/core_concepts_sampling_elicitation_roots_logging_tasks.md

@@ -52,7 +52,7 @@ Examples:
 - a backend asks the host to summarize retrieved context
 - a workflow uses a client-owned model to draft output before human review
 
-### Design Guidance
+### Sampling Design Guidance
 
 Prefer sampling for bounded, explicit decisions. Do not use it as a vague
 "think for a while" escape hatch. The server should still own workflow state
@@ -79,7 +79,7 @@ Use elicitation for:
 - URL handoff flows
 - interrupted task flows that later resume
 
-### Design Guidance
+### Elicitation Design Guidance
 
 Use elicitation only when the server genuinely lacks required input. Do not use
 it to offload validation or to patch over poor tool schemas.
@@ -120,7 +120,7 @@ Logging is useful for:
 - troubleshooting integration issues
 - explaining why a task paused or failed
 
-### Design Guidance
+### Logging Design Guidance
 
 Keep logs operational. They should help clients and operators understand server
 behavior, not duplicate business output that belongs in tool or task results.

docs/core_concepts_sampling_elicitation_roots_logging_tasks.zh.md

@@ -48,7 +48,7 @@ Sampling 指的是服务端请求客户端运行时生成一条模型消息。
 - 某个后端要求 host 总结已检索到的上下文
 - 某个工作流在人工审核前，先用客户端拥有的模型生成草稿
 
-### 设计建议
+### Sampling 设计建议
 
 更推荐把 sampling 用于边界清晰、目标明确的决策，而不是把它当作模糊的“先想一会儿”逃生口。工作流状态和校验仍然应该由服务端负责。
 
@@ -70,7 +70,7 @@ Elicitation 指的是服务端向客户端或用户请求更多信息。在 MCP
 - URL 跳转流程
 - 被中断后可恢复的 task 流
 
-### 设计建议
+### Elicitation 设计建议
 
 只有当服务端确实缺少必要输入时，才应使用 elicitation。不要用它来转移校验责任，也不要用它来掩盖糟糕的 tool schema。
 
@@ -105,7 +105,7 @@ Logging 适合用来传递：
 - 集成问题排查信息
 - 为什么某个 task 被暂停或失败
 
-### 设计建议
+### Logging 设计建议
 
 日志应保持“运维语义”，它应该帮助客户端和操作者理解服务端行为，而不是重复那些本该属于 tool 或 task 结果里的业务输出。