Group of 3 Under the hood
No documentation found
Artifact document writes can now ask the server to reject writes that conflict with a newer version, with automatic fallback
What
- Artifact database writes (both single writes and batch writes) can now pass a
requireVersionflag to the server, asking it to reject a write if the artifact has changed since the client last read it. - Writes made through the
str_replaceediting path also passrequireVersion; this only happens when the artifact-DB feature (CLAUDE_CODE_ARTIFACT_DB, on by default) is enabled and either theCLAUDE_CODE_ARTIFACT_DB_STR_REPLACEenvironment variable or a remote flag (tengu_umber_stile, off by default) is set. - If a server does not understand
requireVersion, the client remembers that server as unsupported and automatically retries the write withoutrequireVersioninstead of failing.
Why This adds an opt-in safeguard against silently overwriting someone else's concurrent changes to an artifact, while staying compatible with older servers that don't support the check yet.
Names in the bundlerequireVersion
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't say what the new result fields contain or what happens when the version check fails.