You'll notice
Certain database writes now require a matching prior approval, tracked per session, before they're allowed
What
Some database writes that first read back the stored document — such as string-replace style edits, or writes pinned to a specific version using if_version — now must match a prior approval recorded earlier in the same session. This is tracked in a new map called dbWriteOpSights. If no matching approval record exists, or the recorded operation or version doesn't match what's being written, the write is refused with a new error.
Why
This closes a gap where a write could otherwise happen without the approval that was supposed to govern it, ensuring a write only proceeds when it matches what was actually approved.