What
Several documents can now be written to an artifact database in a single request. The permission prompt and result text were rewritten to describe the batch ("Write N documents ... in one batch") and ask-rules are matched per write by index. If the server does not accept batches, the writes are applied sequentially and the model is told plainly that the result is not atomic. Which path you get is negotiated with the server, not set by a flag.
Details
- Batch requests are capped at a fixed number of writes, each path validated and de-duplicated, with size guards reporting
duplicate_path,batch_sizeandbatch_too_largeagainst a 1 MiB server request limit. - A server rejection is remembered client-side with a timestamp and an "unsupported" window, so the client stops re-attempting batch shape for a cooldown period.
- On sequential failure the result reports the index that failed and how many entries committed before it.
- Failure messages distinguish "nothing was written" from an outcome that is unknown and may have partly committed.
Evidence
written one write at a time, in order (this server does not take batch writes yet, so it was not atomic), this server does not take batch writes yet, so the batch was applied one write at a time and is NOT atomic
Strings lifted out of the shipped bundle, so the claim above can be checked against them.