Changes on 2026-05-05

1. **Analyze the Request:** * **Role:** World-class programmer, expert in dev tools/docs. * **Task:** Analyze a batch of documentation changes (21 pages total) as a single batch. * **Output Format:** Markdown, concise, insightful, focusing on what matters to developers. * **Language:** Chinese (as requested: "请用中文回复"). * **Structure Required:** 1. Overall Summary (1-2 sentences). 2. Key Themes (bullets). 3. Impact Level (Low/Medium/High/Breaking) with reasoning. 4. Action Items (bullets, max 5). 2. **Analyze the Diff Data:** * *Page 1: `about-claude/pricing.md`* * Change: Path updates. `build-with-claude/data-residency` -> `manage-claude/data-residency`. * *Page 2: `api/overview.md`* * Change: Path updates. `build-with-claude/workload-identity-federation` -> `manage-claude/workload-identity-federation`, `api/authentication/overview` -> `manage-claude/authentication`. * *Page 3: `api/messages.md`* * Change: Added extensive documentation for citation fields (`cited_text`, `document_index`, `end_block_index`, `start_block_index`, `search_result_index`). * Details: Explains what these fields represent (indices, concatenated text), and crucially states `cited_text` is "Not counted toward output tokens, and not counted toward input tokens when sent back in subsequent turns." Also clarifies `search_result_index` behavior. * *Page 4: `api/messages/count_tokens.md`* * Change: Same citation field documentation additions as Page 3. * *Page 5: `api/messages/batches/create.md`* * Change: Same citation field documentation additions as Page 3. * *Page 6: `api/models/list.md`* * Change: "21 more" instead of "20 more" in UnionMember1 description. * New Capability: Added `"managed-agents-2026-04-01"` capability string. * *Page 7: `api/beta/files/upload.md`* * Change: "21 more" instead of "20 more" in UnionMember1 description. * New Capability: Added `"managed-agents-2026-04-01"` capability string. * *Page 8: `api/rate-limits.md`* * Change: Path updates. `build-with-claude/rate-limits-api` -> `manage-claude/rate-limits-api`, `build-with-claude/workspaces` -> `manage-claude/workspaces`. * *Page 9: `api/service-tiers.md`* * Change: Path updates. `build-with-claude/data-residency` -> `manage-claude/data-residency`. * *Page 10: `build-with-claude/overview.md`* * Change: Path update for "Data residency". Also updates the footnote link at the bottom for ZDR details. * *Page 11: `build-with-claude/text-generation.md`* * Change: Same path updates as Page 10. * *Page 12-21 (various)*: * `build-with-claude/prompt-caching.md` * `build-with-claude/batch-processing.md` * `build-with-claude/structured-outputs.md` * `build-with-claude/files.md` * `agents-and-tools/tool-use/computer-use-tool.md` * `agents-and-tools/tool-use/code-execution-tool.md` * `agents-and-tools/tool-use/programmatic-tool-calling.md` * `agents-and-tools/agent-skills/overview.md` * `agents-and-tools/mcp-connector.md` * `CHANGELOG.md.md` * Changes: All of these update the link for "API and data retention" from `build-with-claude/api-and-data-retention` to `manage-claude/api-and-data-retention`. * *Page 21: `CHANGELOG.md.md`* * Change: Added version `2.1.129` changelog. * Key Features: Plugin URL fetching, env vars for sync output and package updates, Gateway model discovery opt-in, Ctrl+R history search behavior change (defaults to all projects), skill overrides setting, bug fixes (clear, context, branch, bold headers, OAuth, prompt cache TTL, bash rules, MCP server patterns, VSCode clear). 3. **Synthesize and Categorize:** * **Theme 1: Documentation Restructuring (Path Changes).** * There is a massive move from `build-with-claude/...` to `manage-claude/...` for infrastructure/management topics like Data Residency, Workload Identity Federation, Rate Limits API, Workspaces, and API/Data Retention. * *Developer Impact:* Bookmarks or hardcoded links in code/docs might break. It suggests a conceptual separation between "Building features" (Prompts, Tools, Agents) and "Managing Platform" (Auth, Limits, Billing, Compliance). * **Theme 2: API Clarification - Citations.** * Significant detail added to `api/messages.md`, `count_tokens.md`, and `batches/create.md` regarding citation fields (`start_block_index`, `end_block_index`, `cited_text`, `search_result_index`). * *Crucial Detail:* `cited_text` is **not counted towards tokens** (output or input in subsequent turns). This is a huge win for cost calculation and transparency. * **Theme 3: New Capability Flag.** * Addition of `"managed-agents-2026-04-01"` in model lists and file uploads. Teases a future feature (Managed Agents). * **Theme 4: CLI Tool Updates (Changelog).** * `CHANGELOG.md` shows extensive updates to the Claude Code CLI (v2.1.129). * Behavioral changes: `Ctrl+R` now searches all prompts by default. * Fixes: Prompt cache TTL enforcement, `clear` command issues, path matching improvements. 4. **Drafting the Content (in Chinese):** * *Summary:* The changes involve a major documentation restructuring moving management topics to a new path, detailed clarification on the token-free nature of citation text in the API, and a significant CLI update with new features and bug fixes. * *Themes:* 1. **Documentation Restructuring:** Systematic migration of "management" related docs (auth, rate limits, data residency) from `build-with-claude/` to `manage-claude/`. 2. **Citations Clarification:** Added detailed descriptions for citation fields, explicitly stating that `cited_text` is not counted towards token usage. 3. **New Capability Flags:** Introduced a new `managed-agents-2026-04-01` capability flag. 4. **CLI Enhancements:** Version 2.1.129 update brings plugin URL fetching, refined search behavior, and multiple bug fixes. * *Impact:* **Medium**. The path changes break existing links, which is annoying but not code-breaking. The citation token clarification is beneficial knowledge but doesn't change existing behavior. The CLI changes are behavioral but backwards compatible enough (mostly fixes). * *Action Items:* 1. Update any hardcoded documentation links in your internal wikis or code comments pointing to `build-with-claude/data-residency`, `rate-limits-api`, etc. 2. Review the `cited_text` field implementation in your citation logic; note that it effectively provides free context. 3. If using the Claude Code CLI, be aware of the `Ctrl+R` search behavior change (now global by default). 4. Check the new `CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE` environment variable if auto-updating the CLI is a concern. 5. **Refining the Output (Self-Correction/Translation Check):** * *Chinese Translation Check:* * "Restructuring" -> 文档结构重组 / 路径迁移. * "Citations" -> 引用. * "Token-free" -> 不计入 Token. * "Capability Flag" -> 能力标志 / 功能标记. * "CLI" -> 命令行工具. * *Formatting:* Ensure markdown syntax is correct. 6. **Final Polish:** * Make sure the summary is punchy. * Ensure the distinction between `build-with-claude` (development) and `manage-claude` (ops/management) is clear in the themes. * Highlight the `cited_text` token cost benefit clearly. *(Self-Correction during drafting)*: The prompt asks for "concise, insightful analysis". Don't just list every changed file. Group them. *Drafting Action Items:* 1. Update bookmarked links for Data Residency, Rate Limits, and Auth docs. 2. Utilize the `cited_text` field knowing it doesn't incur token costs. 3. Adapt to the new `Ctrl+R` default search behavior in the CLI. 4. Monitor for the upcoming `managed-agents-2026-04-01` feature. 7. **Final Output Generation** (matches the thought process above).

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Input:** A batch of 9 documentation page diffs. * **Output Format:** Markdown, Chinese, concise, insightful. * **Structure:** Overall Summary, Key Themes, Impact Level, Action Items. 2. **Analyze the Diffs:** * **Page 1: `claude-code-on-the-web.md`** * *Change:* Added advice to keep setup scripts under ~5 minutes to allow environment caching. Suggests parallel execution (`&`) or moving long tasks to `SessionStart` hooks. * *Dev Relevance:* Performance optimization for cloud sessions, avoiding timeouts. * **Page 2: `desktop.md`** * *Change:* New feature: Split view/sessions. Instructions on how to view two sessions at once (Cmd/Ctrl + click) and close the split (Cmd/Ctrl + \). * *Dev Relevance:* Improved workflow for multi-tasking or comparing code. * **Page 3: `hooks.md`** * *Change:* Updated table for `ok` field in validation objects. Refined descriptions. * *Dev Relevance:* Clarity on validation logic, specifically noting "See the per-event behavior below". * *Note:* Looks mostly like a copy-edit/clarification, but worth noting if writing hooks. * **Page 4: `interactive-mode.md`** * *Change:* Added `Space` key to "Move right" in interactive mode. * *Dev Relevance:* Minor usability improvement. * **Page 5: `network-config.md`** * *Change:* Removed a note about Node.js runtime CA store integration (implies maybe native binary is the default/only supported way now, or the note is obsolete). Added `raw.githubusercontent.com` to the URL allowlist (required for changelog/release notes). * *Dev Relevance:* Enterprise config (network/firewall rules) needs updating. * **Page 6: `plugin-marketplaces.md`** * *Change:* Corrected how to invoke skills. Changed `/quality-review` to `/quality-review-plugin:quality-review` to emphasize namespacing. * *Dev Relevance:* *Breaking/Corrective*. Developers using the old syntax will need to update documentation or commands. * **Page 7: `plugins-reference.md`** * *Change:* Renamed `rust-lsp` plugin to `rust-analyzer-lsp`. * *Dev Relevance:* *Breaking/Corrective*. If referencing the plugin name, it needs updating. * **Page 8: `security.md`** * *Change:* Refined definition of "Accept Edits mode" to be more specific about which bash commands are auto-approved (`mkdir`, `touch`, `rm`, `mv`, `cp`, `sed`). * *Dev Relevance:* Security/Prompting behavior clarity. * **Page 9: `settings.md`** * *Change:* 1. Added `autoMemoryEnabled` setting. 2. Updated `extraKnownMarketplaces` JSON structure (nested `source` object). 3. Added `pathPattern` matching for marketplace allowlisting (regex for filesystem paths). * *Dev Relevance:* New configuration options, structural changes in JSON config. 3. **Synthesize and Structure:** * **Overall Summary:** * This update introduces significant workflow enhancements (split view, parallel session setup), clarifies security behaviors, refines plugin management (namespacing, marketplaces), and updates network requirements for enterprise environments. * **Key Themes:** * **Productivity & UX:** New split view feature and optimized setup script guidance for cloud environments. * **Configuration & Security:** Expanded marketplace allowlist options (`pathPattern`), new `autoMemory` toggle, and specific details on "Accept Edits" mode. * **Plugin Ecosystem:** Clarified skill invocation syntax (namespacing) and renamed the Rust LSP plugin. * **Networking:** Updated firewall requirements to include `raw.githubusercontent.com`. * **Impact Level:** * *Medium/High*. While many changes are enhancements, the structural change in `extraKnownMarketplaces` config and the correction of plugin command syntax are technically "breaking" for existing implementations or scripts relying on the previous schema/naming. * **Action Items:** * Update firewall/proxy allowlists to include `raw.githubusercontent.com`. * Update plugin skill command documentation/scripts to use the new namespaced format (`/plugin-name:skill-name`). * Adjust `managed-settings.json` if using custom marketplace sources due to the schema change. * Optimize web setup scripts to run under 5 minutes for better caching. * Update references to the Rust LSP plugin name (`rust-analyzer-lsp`). 4. **Drafting the Response (in Chinese):** * *Drafting Summary:* 此次更新引入了多项生产力增强功能（如分屏视图、云环境脚本优化），细化了配置与安全策略，并修正了插件生态系统的命名规范。 * *Drafting Themes:* * 生产力与体验：桌面端新增分屏会话功能；云端环境强调脚本并行执行与缓存优化。 * 插件与配置：修正了插件技能调用语法（需加命名空间前缀），重命名了 Rust LSP 插件；新增 Marketplace 的 `pathPattern` 匹配和 `autoMemoryEnabled` 设置。 * 网络与安全：更新了网络白名单（需包含 GitHub raw 域名），细化了“接受编辑”模式的具体行为。 * *Drafting Impact:* Medium/High. Reasoning: 主要影响在于配置文件结构的变更和插件命令语法的修正，若未及时更新可能导致功能失效。 * *Drafting Actions:* * 企业网络配置需增加 `raw.githubusercontent.com` 白名单。 * 检查并更新插件技能调用命令（如 `/plugin:skill`）。 * 更新 `managed-settings.json` 中的 Marketplace 源配置结构。 * 将云端 Setup 脚本控制在 5 分钟内以利用缓存。 * 更新 Rust LSP 插件名称引用。 5. **Review and Refine:** * Ensure markdown formatting is clean. * Check translation accuracy (e.g., "namespaced" -> 命名空间). * Verify the logic matches the diffs. *(Self-Correction during drafting)*: For `hooks.md`, it's just table formatting changes, not a huge impact. I'll group it under clarity. The `network-config.md` removal of the Node.js note is interesting but the actionable part is the new URL allowlist. I will focus on the URL. *Final Polish of the Chinese text.* **Overall Summary:** 本次文档更新主要集中在提升开发效率、强化配置管理能力以及修正插件生态规范。主要亮点包括引入桌面端分屏视图、云端脚本性能优化建议、新增 Marketplace 路径匹配功能，以及对插件命令语法的纠正。 **Key Themes:** * **用户体验增强**: 桌面端新增分屏会话功能，支持并行工作；云端环境建议将 Setup 脚本控制在 5 分钟内以优化缓存构建。 * **配置与安全细化**: 新增 `pathPattern` 用于本地 Marketplace 路径匹配；新增 `autoMemoryEnabled` 设置；明确“Accept Edits”模式自动批准的 Bash 命令列表。 * **网络要求更新**: 企业网络白名单需新增 `raw.githubusercontent.com` 以支持更新日志和插件市场数据。 * **插件生态规范**: 强化了插件技能的命名空间语法（需使用 `/plugin-name:skill-name` 格式），并重命名了 Rust LSP 插件。 **Impact Level:** **Medium/High** * **Reasoning**: 虽然大部分为增强功能，但 Marketplace 配置文件结构的变更（`extraKnownMarketplaces`）以及插件命令语法的纠正属于破坏性变更，若不更新现有配置或脚本，功能将失效或报错。 **Action items:** * 更新防火墙或代理规则，将 `raw.githubusercontent.com` 加入允许列表。 * 修正所有自定义插件技能的调用命令，确保使用完整的命名空间格式（例如 `/quality-review-plugin:quality-review`）。 * 检查并更新 `managed-settings.json`，适配新的 Marketplace 源配置结构（`source` 字段变为对象）。 * 优化云端 Setup 脚本，通过 `&` 并行执行或将耗时任务移至 `SessionStart` hook，确保运行时间在 5 分钟以内。 * 更新文档或脚本中对 Rust LSP 插件的引用，名称改为 `rust-analyzer-lsp`。 6. **Final Output Generation** (matches the polished draft).

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Input:** Two diff pages (`build-with-claude/files.md` and `agents-and-tools/tool-use/code-execution-tool.md`). * **Output Format:** Markdown (Concise, insightful, Chinese). * **Structure:** 1. Overall Summary, 2. Key Themes, 3. Impact Level, 4. Action Items. 2. **Analyze the Diffs:** * **Page 1: `build-with-claude/files.md`** * *Diff 1 (Upload):* PHP code example change. * *Old:* Included `Client` instantiation, used `fopen('/path...', 'r')`, passed parameter named `file`. Code block syntax changed to ````php ... ````. * *New:* Removed boilerplate (`use`, `new Client`), uses `FileParam::fromResource(fopen(..., 'rb'), contentType: 'application/pdf')`, passed parameter looks slightly different or simplified (no named argument `file:` explicitly shown, just the object). * *Observation:* The significant shift here is the usage of `FileParam::fromResource` and `'rb'` mode instead of `'r'`, plus removal of boilerplate. * *Diff 2 (Retrieve Metadata):* PHP code example change. * *Old:* Named argument `fileID: $fileId`. * *New:* Positional argument `$fileId`. * *Diff 3 (Delete):* PHP code example change. * *Old:* Named argument `fileID: $fileId`. * *New:* Positional argument `$fileId`. * *Diff 4 (Download):* PHP code example change. * *Old:* Full boilerplate (`use`, `new Client`), named argument `fileID: ...`. * *New:* Removed boilerplate, positional argument `$fileId`. Also changed code block syntax to ````php ... ````. * **Page 2: `agents-and-tools/tool-use/code-execution-tool.md`** * *Diff 1 (Client instantiation):* PHP code example change. * *Old:* `hidelines={1..3,5}`. Hides lines 1, 2, 3, and 5. * *New:* `hidelines={1..3}`. Hides lines 1, 2, 3. * *Observation:* Likely revealing the `$client` instantiation or part of the setup. Looking at context, it's just a visibility adjustment in the doc renderer. * *Diff 2 (File operations):* PHP code example change. * *Old:* `retrieveMetadata(fileID: $fileId)` and `download(fileID: $fileId)`. * *New:* `retrieveMetadata($fileId)` and `download($fileId)`. * *Observation:* Changed from named arguments to positional arguments. 3. **Synthesize Findings:** * **Target Language:** PHP SDK. * **Primary Change:** Consistently moving from **named arguments** (`fileID: $var`) to **positional arguments** (`$var`) for file operations (`retrieveMetadata`, `delete`, `download`). * **Secondary Change:** Removal of boilerplate setup code (`use`, `new Client`) in file examples to make them more concise and focused on the specific API call. * **Tertiary Change:** Specific update to `upload` using `FileParam::fromResource` with `'rb'` (read-binary) mode, which is technically more correct for files like PDFs than just `'r'`. 4. **Draft the Response (Internal Monologue/Rough Draft):** * *Summary:* The docs were updated for the PHP SDK, specifically focusing on how file operations are called. They removed named parameters and cleaned up code snippets. * *Themes:* * PHP API modernization/cleanup. * Switch from named to positional arguments. * Conciseness (removing setup code). * *Impact:* Medium? Low? It's documentation. If the SDK didn't change, this is just correcting docs. If the SDK *forces* positional now, it's higher. Given the consistency, it implies the SDK API might favor positional, or they are just standardizing the docs. It's likely "Low" to "Medium" impact. Let's go with "Low" to "Medium" because it represents a syntax preference change in the examples. * *Action Items:* * Check existing PHP code for named arguments usage. * Update copy-pasted examples. * Use `'rb'` for binary file uploads. 5. **Refine for "World-Class Programmer" Persona (Chinese):** * *Summary:* 本次更新主要集中在 PHP SDK 的文档代码示例上，将文件操作相关的调用从命名参数改为位置参数，并精简了样板代码。 * *Themes:* * **PHP SDK 调用方式变更**：`retrieveMetadata`、`download`、`delete` 等方法弃用 `fileID:` 命名参数，改用位置参数。 * **文档示例精简**：移除了重复的 `use` 和 `Client` 实例化代码，使示例更聚焦于功能本身。 * **文件上传优化**：上传示例增加了 `FileParam::fromResource` 并建议使用 `'rb'` 二进制读取模式。 * *Impact:* **Medium**。虽然主要是文档调整，但这种大规模的参数风格变更暗示了 SDK 推荐的最佳实践发生了变化。如果开发者严格照搬旧文档的命名参数写法，虽然 PHP 通常兼容（取决于 SDK 版本），但建议跟进以保持代码一致性。 * *Action Items:* * 检查现有 PHP 代码中的文件操作调用，将 `fileID: $id` 改为 `$id`。 * 更新内部文档或代码生成模板中的 PHP 示例。 * 确保文件上传操作使用 `FileParam::fromResource` 并以 `'rb'` 模式打开文件。 6. **Final Polish (Markdown formatting):** * Ensure headers are correct. * Ensure tone is professional and concise. 7. **Final Review of the "Upload" change:** * Old: `$client->beta->files->upload(file: fopen(..., 'r'))` * New: `$client->beta->files->upload(FileParam::fromResource(fopen(..., 'rb'), contentType: 'application/pdf'))` * This is a significant API surface change in the example (wrapping in `FileParam`). I must highlight this. 8. **Final Output Generation** (Proceeding to generate output based on step 5 & 7).

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Input:** A batch of 13 documentation diff files (markdown). * **Output Language:** Chinese. * **Format:** Markdown (Concise, insightful). * **Structure:** 1. Overall Summary (1-2 sentences). 2. Key Themes (bullets). 3. Impact Level (Low/Medium/High/Breaking) with reasoning. 4. Action Items for Developers (bullets, max 5). 2. **Analyze the Diffs (Page by Page):** * **`cli-reference.md`**: `--plugin-dir` now supports loading from a `.zip` archive, not just a directory. * **`data-usage.md`**: Telemetry service moved from "Statsig" to "Anthropic". Removed specific encryption details (TLS/AES mentions removed in text, though maybe implied/kept elsewhere?). Updated table references. Updated text regarding provider-managed metrics. * **`headless.md`**: Added note about `stdin` capped at 10MB (v2.1.128). Updated description of `plugin_errors` in `system/init` event to include `--plugin-dir` load failures (missing path, invalid archive). * **`hooks.md`**: Clarified behavior of `PostToolUse` hooks. Specifically, if `decision` is "block", it adds reason *next* to the result, Claude still sees original output. Previously it implied Claude saw the reason instead? Or just clarified. Also clarified `decision: block` doesn't replace output; use `updatedToolOutput` for that. * **`iam.md`**: Clarified credential storage locations (split macOS/Linux/Windows clearly). Added Windows specific path `%USERPROFILE%`. Mentioned `CLAUDE_CONFIG_DIR` override. * **`mcp.md`**: `/mcp` panel now shows tool counts. Flags servers with no tools. "workspace" name is reserved. `alwaysLoad: true` now blocks startup (5s timeout) even if `MCP_CONNECTION_NONBLOCKING=1` is set. * **`monitoring-usage.md`**: Claude Code *does not* pass `OTEL_*` vars to subprocesses (Bash, hooks, etc.). Removed specific vars `OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY`/`CERTIFICATE` from the main table and moved them into a new "mTLS authentication" section, distinguishing between `http` and `grpc` protocols. * **`plugin-marketplaces.md`**: Clarified `strictKnownMarketplaces` URL matching (exact match doesn't normalize URLs). * **`plugins-reference.md`**: Clarified `${CLAUDE_PLUGIN_ROOT}` is ephemeral (doesn't survive updates). Note on lifecycle: hooks/monitors keep using old path until reload/restart. Added note: `CLAUDE.md` at plugin root is *not* loaded as context. * **`settings.md`**: Added note on Windows paths (`~/.claude` -> `%USERPROFILE%\.claude`). Updated `channelsEnabled` description for API key auth (allowed by default unless managed settings exist). * **`skills.md`**: Added best practice tip: Keep skill body concise for token cost (since it stays in context). * **`slash-commands.md`**: Duplicate of `skills.md` change. * **`statusline.md`**: Update trigger for statusline script (now after `/compact`). Clarified `context_window.current_usage` is `null` after `/compact` until next API call. 3. **Synthesize Key Themes:** * **Plugin Loading & Packaging:** Support for `.zip` plugins, better error reporting for plugin loads, clarification on update lifecycles. * **Observability & Telemetry:** Shift from Statsig to Anthropic for metrics, improved mTLS config for OpenTelemetry, better subprocess behavior regarding env vars. * **UX & Behavior Clarifications:** Better explanations of hooks behavior, `/compact` effects on statusline/context, stdin limits, reserved names. * **Cross-Platform Consistency:** Clarifying Windows paths in settings/IAM. 4. **Determine Impact Level:** * **Level:** Medium. * **Reasoning:** * Plugin zip support is a feature addition (positive). * Statsig to Anthropic is an infra change, invisible to most but affects privacy/monitoring. * `alwaysLoad` blocking startup is a behavior change (could break non-blocking setups if they relied on specific timing, but likely improves reliability). * OTEL mTLS config changes (env vars moved) might break existing configs if users hardcoded specific metrics vars that now need protocol-specific handling. * `stdin` cap is a breaking change for heavy piped users (though 10MB is generous). 5. **Formulate Action Items:** * Check plugin installs if using local paths. * Update OTEL mTLS config if using gRPC. * Watch for `/compact` behavior in custom scripts (statusline). * Be aware of the stdin limit if using heavy pipes. 6. **Drafting the Content (in Chinese):** * *Summary:* 本次更新主要集中在插件系统增强（支持 ZIP 打包、更明确的生命周期管理）、遥测迁移至 Anthropic 基础设施、以及多项配置和行为的澄清（如 OpenTelemetry 的 mTLS 配置、状态栏刷新逻辑）。 * *Themes:* * **插件能力提升**：`--plugin-dir` 现支持 `.zip` 归档文件；增强了插件加载错误的反馈（如路径缺失或归档无效）；明确了插件更新时的路径生命周期处理。 * **遥测与监控变更**：指标服务从 Statsig 迁移至 Anthropic；重构了 OpenTelemetry 的 mTLS 认证配置，区分了 HTTP 和 gRPC 协议的变量。 * **配置与行为澄清**：明确了 `PostToolUse` hook 的行为；补充了 Windows 平台路径说明；解释了 `/compact` 命令对状态栏和上下文窗口的影响；新增 stdin 10MB 限制。 * *Impact:* Medium. 引入了新的功能（ZIP 插件）和破坏性较小的行为变更（stdin 限制、OTEL mTLS 配置变更），主要是文档层面的澄清和基础设施更新。 * *Action Items:* * 如果使用了 OpenTelemetry 的 mTLS 功能，需检查并更新环境变量配置，特别是针对 gRPC 协议。 * 若脚本通过管道传输大量数据至 Claude Code，请注意新增的 10MB 限制，建议改用文件引用。 * 开发插件时，注意 `${CLAUDE_PLUGIN_ROOT}` 的临时性，且根目录下的 `CLAUDE.md` 不会被自动加载。 * 更新依赖 MCP `alwaysLoad` 标志的逻辑，因为它现在会阻塞启动（即使设置了非阻塞模式）。 7. **Review and Refine:** * Ensure tone is professional. * Check specific details (e.g., OTEL vars moved/renamed logic). * *Self-Correction on OTEL:* The diff shows specific metrics mTLS vars were removed from the general table and moved to a protocol-specific section. It says "existing configurations that set the per-signal metrics variables continue to work" for gRPC, but users should verify based on the new docs. It's worth mentioning as a check. * *Self-Correction on stdin:* It's a new cap, so it's a potential breaking edge case. 8. **Final Polish (Markdown Output):** Proceed to generate output.