Error message for version-pinned batch writes now says the whole batch is refused, not applied piecemeal
When Claude Code explains why an unsupported batch write can't proceed, it now takes into account whether the batch is version-pinned. For a version-pinned batch, the message says it will only be applied all-or-nothing if the server supports batch writes; otherwise it's refused entirely, since 'a version-pinned batch is never applied one at a time'. This replaces the previous message, which described a one-at-a-time fallback.
This corrects the explanation given to accurately reflect that a version-pinned batch can't be split apart and applied piece by piece, avoiding a misleading description of what happens when the write fails.