fix: ctx_patch batch ops rejected with -32602 (schema over-constrains top-level path) (#1005)

[andig]

Problem

Fixes #1005. ctx_patch rejected valid batch calls with MCP error -32602: path is required. The tool documents Batch: ops:[{op, path, ...}], but:

1. the schema declared required: ["path"], and
2. the handler called require_resolved_path(…, "path") unconditionally,

so a correct batch was refused before it ever reached execution. On top of that, the implementation only applied ops to one shared params.path — the advertised cross-file batch never actually worked.

Fix

• Schema: drop path from required. Top-level path is optional when ops is present.
• Handler: plan_groups groups batch ops by each op's own path (falling back to the top-level path), resolves + write-gates each file, and applies them per file through the shared apply_one — extracted from the old inline handler body and reused by the single-op path too. A batch may now legitimately span files.
• Existing single-file batch atomicity (bottom-up, all-or-nothing per file) is unchanged; cross-file batches are atomic per file.

Also softens ctx_read's mode docs, which overclaimed "REQUIRED" though the param is optional and defaults to auto (issue item 2).

Scope

Issue item 3 — modeling action-conditional requirements across ctx_execute / ctx_search with JSONSchema oneOf/if-then — is intentionally left as a follow-up rather than speculatively rewriting every tool schema in this PR.

Tests

4 new pure grouping tests (cross-file order, top-level fallback, missing-path rejection, empty-ops). Full existing ctx_patch suite (86 tests incl. batch atomicity, syntax gate, BOM/CRLF, backups) passes.

🤖 Generated with Claude Code

[yvgude]

Superseded by and integrated into #1013, including per-op cross-file batch planning, schema correction, token-budget protection, and additional regression coverage. The original commit/authorship remains preserved in the integrated history. Thank you.