diff --git a/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.i18n.yaml b/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.i18n.yaml new file mode 100644 index 0000000000..3e63657ba7 --- /dev/null +++ b/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.i18n.yaml @@ -0,0 +1,31 @@ +# Bilingual-pair consistency record for 2026-09-28-apply-patch-file-editing.md (docs/i18n/README.md): per heading +# section, a hash of its English and Chinese blocks outside code blocks and generated regions. +# After editing either side, bring the other along and re-record with: +# pnpm run verify-translation-pairing --write .agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.md +/agent-note-apply-patch-file-editing: + en: 76281e6919445c05 + zh: 22c855a840d5e98c +/agent-note-apply-patch-file-editing/problem: + en: 631d9a311ab996a9 + zh: 5d248a4690caa635 +/agent-note-apply-patch-file-editing/proposal: + en: aa5d52ca643f37df + zh: 835b59c07bc8401d +/agent-note-apply-patch-file-editing/proposal/confirmed-design-choices: + en: 6ff974940136c83c + zh: 42628aed000ff31e +/agent-note-apply-patch-file-editing/proposal/development-plan: + en: 9a2dd65884617f75 + zh: 549156fc04488d72 +/agent-note-apply-patch-file-editing/proposal/review-acceptance-boundary: + en: 93272ed56f783085 + zh: 4179782cfff0d5e0 +/agent-note-apply-patch-file-editing/alternatives-considered: + en: 4afded3298d7eb9c + zh: f397a2338787ca81 +/agent-note-apply-patch-file-editing/acceptance-criteria: + en: 837dc9f292c43ced + zh: 4666e89322ce6baf +/agent-note-apply-patch-file-editing/risks: + en: 0fcf82e6f0c4cb3e + zh: 0acfa13bc6857a56 diff --git a/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.md b/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.md new file mode 100644 index 0000000000..6d4b2499c0 --- /dev/null +++ b/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.md @@ -0,0 +1,87 @@ +# Agent Note: Apply patch file editing + +Status: proposed + +English | [中文](2026-09-28-apply-patch-file-editing.zh.md) + +## Problem + +A model editing several files or separated regions needs multiple literal-edit calls or a shell script. Shell and Python edits do not expose their affected paths to the existing file-tool capture path, so a working directory without Git cannot reliably present those edits in the turn Review tab. A patch tool can express related edits in one call and identify every affected path before mutation. Implementation precedes the effectiveness evaluation in #5121; #4556 supplies the broader motivation for efficient use of file tools. + +## Proposal + +Add an `apply_patch` tool for text-file creation, updates, deletion, and moves, with multiple files and hunks per call. Use Codex patch syntax and the existing filesystem capability, observation policy, sandbox policy, and tool execution lifecycle. Keep parsing and path extraction in a shared pure module so execution and Review capture interpret the same patch. + +Review work is limited to collecting the tool's affected paths before mutation and adding necessary composition or configuration entries. Reuse the existing [workspace change recorder](../../../../packages/deliverables/workspace-changes/README.md) and [Review tab](../../../../packages/client/ui-deliverables/README.md), including their diff types and display logic. Moves may appear as deletion plus creation. Rename-specific presentation, durable Review storage, remote capture, and changes to capture limits or failure policy are outside this proposal. + +### Confirmed design choices + +The choices below are approved for this design. The feature remains unimplemented, so the note retains `Status: proposed`. Step 1 selects the upstream version and specifies examples and integration details within these choices before parser and mutation work starts. + +| Topic | Confirmed choice | Implementation specification in step 1 | +|---|---|---| +| Input | A JSON argument with a `patch` string; reuse filesystem permission fields when applicable. | Final argument schema, activation method, and bounded result fields. | +| Syntax | `*** Begin Patch`, `*** End Patch`, `*** Add File:`, `*** Update File:`, `*** Delete File:`, `*** Move to:`, hunk markers, and `*** End of File`. | Select an upstream Codex version and enumerate supported forms, malformed input, and any exclusions. | +| Matching | Follow the parser and matcher of a pinned Codex version. | Verify the reference behavior for exact matching, whitespace tolerance, Unicode normalization, repeated contexts, search order, empty hunks, and EOF handling; record an expected output or error for each. | +| Filesystem policy | Preserve the mounted observation and sandbox policies; an internal preflight read does not count as a model observation. | Specify update/delete/move guards and destination collisions under these policies, plus path aliases, repeated paths, cross-provider moves, and line-ending preservation. | +| Failure | Preflight the whole patch, then commit in order; stop at the first failure and report actual completed, failed, and unexecuted operations; no whole-patch rollback. | Per-operation commit points, cancellation, and destination-written/source-not-deleted move outcomes. | +| Activation | Enable through composition for implementation and evaluation while retaining existing file tools. | Which profiles expose the tool initially; broader default adoption follows measured results. | + +The selected Codex version defines patch syntax and text matching. Read-before-edit, freshness checks, and sandbox restrictions remain Harness deployment policies. The compatibility matrix records these policy differences and the verified reference behavior; it is an implementation specification, not a pending choice between matching strategies. + +### Development plan + +Each step produces reviewable evidence. The implementation owner delivers the code and checks; the maintainer reviewing the change accepts the step. There is no calendar estimate or named staffing commitment. The critical path is steps 1–6 followed by integrated acceptance in step 7; evaluation in step 8 starts after acceptance. Parser fixtures and filesystem-operation design can proceed independently once step 1 fixes their shared types and semantics. + +1. **Specify the confirmed behavior and ownership.** Select and record the upstream version; read its parser, matcher, tests, and license, and expand the confirmed choices into a compatibility matrix. Decide where the pure parser and tool plugin live in the filesystem group, using the [architecture](../../../../docs/architecture.md) and [tool integration guide](../../../../docs/cookbook/adding-a-tool.md). Deliver input/output examples for success, rejection, and partial completion, plus the operation and path rules above. Exit when every supported syntax and matching rule has an expected result, package dependencies are explicit, and mutation safety has testable requirements. + +2. **Build pure parsing and matching.** Convert patch text into ordered operations, affected paths, and hunks; apply hunks to supplied text without filesystem I/O. Cover multiple files and hunks, malformed markers, repeated context, LF/CRLF, missing final newline, Unicode, and empty files against the compatibility matrix. Exit when selected upstream fixtures and Harness-specific differences have deterministic tests, including rejected cases, and the same parsed operations serve execution and capture. + +3. **Provide guarded filesystem operations.** The current [filesystem service](../../../../packages/fs/fs/README.md) has text writes and literal edits, but no delete or move operation. Add only the primitives needed by the chosen patch design, preserving provider-owned freshness checks and atomic publication of a single file. Update local, sandboxed, and [SSH filesystem](../../../../packages/ssh/fs-ssh/README.md) implementations and any affected RPC helper/schema consumers together. A move spans two paths: define locking, source and destination guards, and failure outcomes explicitly. Exit when stale versions, denied paths, collisions, and interrupted operations leave the documented disk state; do not claim a multi-file transaction. + +4. **Implement patch execution.** Resolve and deduplicate canonical targets, obtain policy intents, and preflight syntax, permissions, matching, and destination rules before mutation. Recheck freshness at each provider commit; preflight does not prevent a later race or I/O failure. Execute in order, update observations after actual mutations, and retain completed-operation facts through cancellation or later failure. Exit when result metadata and concise model output agree with disk state, including partial moves, and the executor never bypasses the filesystem provider with shell or direct host writes. + +5. **Expose and present the tool.** Register `apply_patch` through normal plugin effects and the existing tool/PTC paths; keep the agent loop unchanged. Put parameter rules in the schema, teach when to choose the tool, and provide short corrective errors. Design the Host presenter and Web tool-call presentation using existing result metadata and presentation mechanisms. Add the selected activation/configuration entries and fail clearly on missing dependencies. Exit when the intended profiles advertise and execute the tool, disabled profiles remain coherent, and model-visible output is reconstructable from the Session log. + +6. **Connect existing Review capture.** The recorder's [mutation-path extraction](../../../../packages/deliverables/workspace-changes/src/capture.ts) currently recognizes a fixed set of tools and returns one path. Add the smallest producer-side adaptation for `apply_patch` to enumerate every affected path, including both move endpoints, from the shared parser. Await baseline capture before any write and retain the first capture of each path in the turn. Reuse turn-end capture and comparison of actual bytes. Exit when a non-Git directory shows every supported file with a net change, repeated edits produce a first-to-last diff, failed/unexecuted operations add no fictitious change, and Review display code is unchanged. This requires a small path-extraction change; configuration alone cannot provide it today. + +7. **Verify the composed capability and document it.** Combine focused parser/provider/tool tests with a recorded Session snapshot through a shipped profile and an existing Review flow in a non-Git directory. Cover successful edits, preflight rejection, partial execution, cancellation, and existing-tool regression. If the snapshot harness cannot express a required path, add that support in the same implementation. Update affected bilingual READMEs, JSDoc, subsystem references, and generated catalogs; acknowledge any declared persistence-type changes. Follow [testing policy](../../../../docs/testing.md) and [scope-based checks](../../../skills/dsh-pre-push-checks/SKILL.md). Exit when the acceptance matrix below passes and any unavailable real-provider evidence is explicitly reported. + +8. **Evaluate after implementation.** Run the same representative editing tasks with existing file tools and with `apply_patch`, controlling model, repository state, and task instructions. Measure correct final files, task success, request/prompt/output tokens, model steps, tool calls, retries, latency, and existing Review coverage. Report failures as well as gains, including the first-request prompt cost. Exit with a reproducible comparison and a recommendation on default activation; do not assume improvement or build a general benchmarking platform as part of this feature. + +### Review acceptance boundary + +Review uses whole-file captures before the first mutation and at turn end; tool-call hunks and patch text are not substitutes for these bytes. Test without a Git repository and with Git unavailable so Git coverage cannot conceal missing tool-path capture. A create followed by deletion, or an edit fully reverted in the same turn, has no net change and need not produce a row. + +The [existing Review decision](../../implemented/feature/2026-09-15-changed-file-diff-preview.md) owns size/count/time limits, capture-error behavior, session lifetime, and supported locations. This feature inherits them. Acceptance covers supported Host files while their Session is available; it does not promise persistent or SSH Review. Adding operations to the SSH filesystem provider keeps the filesystem API complete and does not imply remote Review support. + +## Alternatives considered + +**Keep using shell or Python for patches.** This leaves non-Git file changes without a predictable pre-mutation path list and does not provide the requested model-facing editing tool. + +**Reuse Codex markers with an independently strict matcher.** This can reduce initial implementation work but makes familiar patches fail differently. The confirmed design follows a pinned Codex parser and matcher, with Harness filesystem-policy differences explicitly recorded. + +**Make the whole patch transactional.** Cross-file rollback adds recovery state and can overwrite concurrent external edits. Preflight plus ordered commits gives earlier rejection and explicit partial results without promising rollback. + +**Expand Review while adding the tool.** Rename UI, persistent storage, remote capture, and a new capture-failure policy are independent product decisions. Existing capture and diff rendering suffice for the scoped tool integration. + +## Acceptance criteria + +| Area | Required evidence | +|---|---| +| Text operations | Add, update, delete, move, multiple files, and multiple hunks produce the expected final bytes; syntax and matching differences are recorded. | +| Guarded mutation | Unobserved or stale sources, protected paths, and destination conflicts follow the chosen policies; rejected preflight performs no writes. | +| Failure and cancellation | A failure after an earlier commit reports every completed mutation and every pending operation; disk state and output agree. | +| Non-Git Review | Existing Review shows supported net changes at turn end, including both move endpoints as existing file entries; no display-logic change. | +| Tool experience | Normal calls and PTC use the registered tool; concise output, errors, tool-call presentation, and Session snapshots agree. | +| Adoption evidence | The post-implementation comparison reports correctness and total work before recommending broader activation. | + +## Risks + +Upstream matching may be permissive or change between versions. Pin the reference and verify its behavior with compatibility fixtures; fix unintended mismatches against that reference. Any proposed matching-policy change must be recorded as a change to the confirmed design. Copying upstream code also requires license and dependency review. + +Preflight can succeed before a later version conflict, cancellation, or storage failure. The implementation owner must preserve provider guards and accurate partial outcomes, especially for moves; a test failure here blocks tool acceptance. + +Path extraction can drift from execution or omit a move endpoint. Sharing the parsed operations and testing the complete non-Git path is required before enabling the tool in a profile with Review. + +This proposal preserves the rationale of the [filesystem split](../../implemented/simplification/2026-06-26-fsspec-style-fs-seam.md), [observation event policy](../../implemented/architecture/2026-06-26-file-context-as-event-gate.md), [filesystem sandbox](../../implemented/feature/2026-07-14-cross-family-fs-sandbox.md), and [turn changed-files card](../../implemented/feature/2026-09-11-turn-changed-files-card.md). It adds an editing capability without superseding those decisions. diff --git a/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.zh.md b/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.zh.md new file mode 100644 index 0000000000..79c0c92703 --- /dev/null +++ b/.agents/notes/proposed/feature/2026-09-28-apply-patch-file-editing.zh.md @@ -0,0 +1,87 @@ +# Agent Note: Apply patch 文件编辑 + +Status: proposed + +[English](2026-09-28-apply-patch-file-editing.md) | 中文 + +## 问题 + +模型编辑多个文件或相隔较远的区域时,需要多次字面量编辑调用或一段 shell 脚本。Shell 和 Python 编辑不会向现有文件工具采集路径暴露受影响文件,因此没有 Git 的工作目录无法可靠地在轮次 Review tab 中展示这些修改。补丁工具可以在一次调用中表达相关编辑,并在修改前识别所有受影响路径。#5121 先实现工具再评测效果;#4556 提供了高效使用文件工具的更广泛动机。 + +## 提案 + +新增 `apply_patch` 工具,支持文本文件的创建、更新、删除和移动,以及一次调用中的多文件、多 hunk 修改。采用 Codex 补丁语法,复用现有文件系统能力、观察策略、沙箱策略和工具执行生命周期。将解析与路径提取放在共享的纯模块中,使执行与 Review 采集对同一补丁保持一致理解。 + +Review 工作仅限于在修改前采集工具涉及的路径,以及添加必要的组合或配置项。复用现有[工作区变更记录器](../../../../packages/deliverables/workspace-changes/README.zh.md)和 [Review tab](../../../../packages/client/ui-deliverables/README.zh.md),包括其 diff 类型和展示逻辑。移动可以显示为删除加创建。重命名专用展示、Review 持久化存储、远程采集,以及采集限制或失败策略的调整均不在本提案范围内。 + +### 已确认的设计选择 + +以下设计选择已获确认。功能尚未实现,因此文档保留 `Status: proposed`。步骤 1 将在解析器和修改操作开发开始前,选定上游版本,并在这些选择之内细化示例与接入细节。 + +| 主题 | 已确认方案 | 步骤 1 需细化的实现规范 | +|---|---|---| +| 输入 | 使用包含 `patch` 字符串的 JSON 参数;适用时复用文件系统权限字段。 | 最终参数 schema、启用方式,以及有输出上限的结果字段。 | +| 语法 | `*** Begin Patch`、`*** End Patch`、`*** Add File:`、`*** Update File:`、`*** Delete File:`、`*** Move to:`、hunk 标记和 `*** End of File`。 | 选择上游 Codex 版本,列出支持形式、非法输入及排除项。 | +| 匹配 | 遵循固定版本 Codex 的解析器和匹配器。 | 核对参照实现的精确匹配、空白容错、Unicode 归一化、重复上下文、搜索顺序、空 hunk 和 EOF 行为;每项记录预期输出或错误。 | +| 文件系统策略 | 保留已挂载的观察与沙箱策略;内部预检读取不算模型观察。 | 在这些策略下细化更新、删除和移动的保护条件与目标冲突,以及路径别名、重复路径、跨提供方移动和换行符保留规则。 | +| 失败 | 先预检整个补丁,再按顺序提交;首次失败即停止,报告实际完成、失败和未执行的操作;不提供整个补丁回滚。 | 各操作的提交点、取消,以及目标已写入但源文件未删除时的移动结果。 | +| 启用 | 通过组合配置启用以进行实现和评测,同时保留现有文件工具。 | 首批暴露工具的 profile;扩大默认启用范围以评测结果为依据。 | + +补丁语法与文本匹配遵循选定的 Codex 版本。先读后改、版本新鲜度检查和沙箱限制仍属于 Harness 部署策略。兼容性矩阵记录这些策略差异和已核实的参照行为,是实现规范,不再将匹配策略列为待选择项。 + +### 开发计划 + +每一步都产出可评审的证据。实现负责人交付代码与检查结果,由评审该变更的维护者验收步骤。本计划不承诺日历工期或具名人员安排。关键路径是步骤 1–6,随后在步骤 7 集成验收;步骤 8 的评测在验收后开始。步骤 1 固定共享类型和语义后,解析器 fixture 与文件系统操作设计可以独立推进。 + +1. **细化已确认行为与归属。** 选定并记录上游版本,阅读其解析器、匹配器、测试和许可证,将已确认选择展开为兼容性矩阵。依照[架构](../../../../docs/architecture.zh.md)和[工具接入指南](../../../../docs/cookbook/adding-a-tool.zh.md),确定纯解析器与工具插件在文件系统组中的位置。交付成功、拒绝及部分完成的输入输出示例,以及上述操作和路径规则。退出条件:每种支持的语法和匹配规则都有预期结果,包依赖明确,修改安全性具有可测试的要求。 + +2. **实现纯解析与匹配。** 将补丁文本转换为有序操作、受影响路径和 hunk;只对传入文本应用 hunk,不进行文件系统 I/O。依据兼容性矩阵覆盖多文件、多 hunk、非法标记、重复上下文、LF/CRLF、缺少末尾换行、Unicode 和空文件。退出条件:选定的上游 fixture 与 Harness 特有差异都有确定性测试,包含拒绝用例;执行和采集使用同一组解析结果。 + +3. **补齐受保护的文件系统操作。** 当前[文件系统服务](../../../../packages/fs/fs/README.zh.md)提供文本写入和字面量编辑,没有删除或移动操作。只添加选定补丁设计需要的原语,保留提供方负责的版本新鲜度检查和单文件原子发布。同时更新本地、沙箱和 [SSH 文件系统](../../../../packages/ssh/fs-ssh/README.zh.md)实现,以及受影响的 RPC helper/schema 消费方。移动涉及两个路径,必须明确定义锁、源与目标保护条件及失败结果。退出条件:旧版本、受限路径、目标冲突和中断操作都留下约定的磁盘状态;不宣称多文件事务。 + +4. **实现补丁执行。** 解析并去重规范化目标,获取策略意图,在修改前预检语法、权限、匹配及目标规则。每次由提供方提交时重新检查版本新鲜度;预检不能消除后续竞态或 I/O 失败。按顺序执行,在实际修改后更新观察状态,并在取消或后续失败时保留已完成操作的事实。退出条件:结果元数据和精简模型输出与磁盘状态一致,包括部分完成的移动;执行器不通过 shell 或直接写 Host 文件绕过文件系统提供方。 + +5. **暴露并呈现工具。** 通过常规插件 effect 和现有工具/PTC 路径注册 `apply_patch`,保持 agent loop 不变。将参数规则放入 schema,说明何时选用工具,并提供简短的纠错信息。使用现有结果元数据和呈现机制设计 Host presenter 与 Web 工具调用展示。添加选定的启用/配置项,对缺失依赖给出明确错误。退出条件:目标 profile 能声明并执行工具,未启用的 profile 保持一致,所有模型可见输出均可由 Session 日志重建。 + +6. **接入现有 Review 采集。** 记录器的[修改路径提取](../../../../packages/deliverables/workspace-changes/src/capture.ts)目前只识别固定工具,并返回单一路径。为 `apply_patch` 增加最小的生产端适配,从共享解析器枚举全部受影响路径,包括移动的源与目标。在任何写入前等待基线采集完成,并保留每个路径在轮次中的首次采集。复用轮次结束时对实际字节的采集与比较。退出条件:无 Git 目录能展示所有支持范围内存在净变化的文件,重复编辑形成从首次修改前到最终状态的 diff,失败或未执行操作不产生虚假变更,Review 展示代码不变。这里需要小幅修改路径提取;当前仅靠配置不能实现。 + +7. **验证组合能力并补齐文档。** 将定向解析器、提供方和工具测试,与通过已发布 profile 的录制 Session 快照、无 Git 目录中的现有 Review 流程结合。覆盖成功修改、预检拒绝、部分执行、取消及现有工具回归。如果快照测试框架无法表达必要路径,在同一实现中补齐支持。更新受影响的双语 README、JSDoc、子系统参考和生成目录;确认声明的持久化类型变更。遵循[测试策略](../../../../docs/testing.zh.md)和[按范围选择检查的规则](../../../skills/dsh-pre-push-checks/SKILL.md)。退出条件:下方验收矩阵通过,无法获得的真实提供方验证证据明确列出。 + +8. **实现后评测。** 使用现有文件工具与 `apply_patch` 分别执行同一组典型编辑任务,控制模型、仓库状态和任务指令。测量最终文件正确性、任务成功率、请求/prompt/输出 token、模型步骤、工具调用、重试、延迟和现有 Review 覆盖情况。报告失败及收益,包含首个请求的 prompt 成本。退出条件:形成可复现的比较与默认启用建议;不预设改进,也不在本功能中建设通用评测平台。 + +### Review 验收范围 + +Review 使用首次修改前与轮次结束时的完整文件采集;工具调用的 hunk 和补丁文本不能代替这些字节。测试应同时覆盖无 Git 仓库及 Git 不可用的环境,避免 Git 覆盖掩盖工具路径漏采集。文件在同一轮次中先创建后删除,或修改后完全还原,没有净变化,可以不产生文件行。 + +[现有 Review 决策](../../implemented/feature/2026-09-15-changed-file-diff-preview.zh.md)负责大小、数量、时间限制、采集错误行为、会话生命周期及支持位置。本功能沿用这些规则。验收覆盖 Session 可用期间支持范围内的 Host 文件,不承诺持久化或 SSH Review。补齐 SSH 文件系统提供方的操作是为了保持文件系统 API 完整,不代表支持远程 Review。 + +## 考虑过的替代方案 + +**继续通过 shell 或 Python 应用补丁。** 无 Git 文件变更仍然缺少可预先确定的修改路径列表,也无法提供所需的模型文件编辑工具。 + +**复用 Codex 标记,自行实现严格匹配器。** 这可以减少初期实现工作,但会让熟悉的补丁以不同方式失败。已确认设计遵循固定版本 Codex 的解析器和匹配器,并明确记录 Harness 文件系统策略的差异。 + +**让整个补丁具备事务性。** 跨文件回滚需要恢复状态,并可能覆盖并发的外部编辑。预检加顺序提交可以提前拒绝错误,并提供明确的部分结果,无需承诺回滚。 + +**添加工具时同时扩展 Review。** 重命名 UI、持久化存储、远程采集和新采集失败策略是独立的产品决策。现有采集与 diff 渲染足以支持本次范围内的工具接入。 + +## 验收标准 + +| 领域 | 必需证据 | +|---|---| +| 文本操作 | 新增、更新、删除、移动、多文件和多 hunk 产生预期最终字节;语法与匹配差异有记录。 | +| 受保护的修改 | 未观察或已过期的源文件、受限路径及目标冲突遵循选定策略;预检拒绝不发生写入。 | +| 失败与取消 | 前序提交后的失败报告全部已完成修改和待执行操作;磁盘状态与输出一致。 | +| 无 Git Review | 现有 Review 在轮次结束时展示支持范围内的净变化,包含移动两端对应的现有文件条目;不改变展示逻辑。 | +| 工具体验 | 普通调用和 PTC 使用注册工具;精简输出、错误、工具调用展示与 Session 快照一致。 | +| 启用依据 | 实现后的比较先报告正确性和总工作量,再建议扩大启用范围。 | + +## 风险 + +上游匹配可能较宽松,也可能随版本变化。固定参照版本,并用兼容性 fixture 核对其行为;修复与参照实现不一致的意外差异。任何匹配策略调整都必须记录为已确认设计的变更。复制上游代码还需要审查许可证和依赖。 + +预检成功后仍可能发生版本冲突、取消或存储失败。实现负责人必须保留提供方保护条件和准确的部分结果,尤其是移动;此处测试失败会阻止工具验收。 + +路径提取可能偏离执行行为或遗漏移动的一端。在支持 Review 的 profile 中启用工具前,必须共享解析结果并验证完整的无 Git 路径。 + +本提案保留[文件系统拆分](../../implemented/simplification/2026-06-26-fsspec-style-fs-seam.zh.md)、[观察事件策略](../../implemented/architecture/2026-06-26-file-context-as-event-gate.zh.md)、[文件系统沙箱](../../implemented/feature/2026-07-14-cross-family-fs-sandbox.zh.md)和[轮次变更文件卡片](../../implemented/feature/2026-09-11-turn-changed-files-card.zh.md)的决策依据。它新增编辑能力,不替代上述决策。