plan/results: record the two post-gate CRUD corrections

The gate results file said the replacement-style-update gap was found and not
fixed, and PLAN said it was left alone. Both were true when written and are not
now, so a reader would take the M0 scorecard for the current one. The M0 figures
stay as measured -- they are the gate result -- with a pointer to
tests/spec/scorecard.txt, which always holds the current number.

tests/e2e/results/m0-gates.txt

@@ -148,9 +148,12 @@
 # argument for keeping both the churn gate and the concurrent benchmark in the
 # gate list rather than treating them as optional.
 #
-# ONE COMPATIBILITY GAP FOUND, NOT FIXED (out of M0's scope, storage-only)
-# `update.apply` (src/update.zig:18) rejects any update document whose first
-# key is not `$`, so replacement-style writes -- replaceOne, findOneAndReplace,
-# bulkWrite's replaceOne -- fail with "bad update". Found while building the
-# churn workload. It is a CRUD feature, not storage, and it is already part of
-# what the 161 spec failures cover.
+# ONE COMPATIBILITY GAP FOUND HERE, FIXED AFTER THE GATE
+# `update.apply` rejected any update document whose first key was not `$`, so
+# replacement-style writes -- replaceOne, findOneAndReplace, bulkWrite's
+# replaceOne -- failed with "bad update". Found while building the churn
+# workload, out of scope for a storage milestone, and fixed immediately after in
+# `update: replacement-style writes` and `db: a write that changes nothing is
+# not a write`. The scorecard above is the M0 figure and is left as measured;
+# those two commits took it to 163 pass / 129 fail, and `tests/spec/scorecard.txt`
+# always holds the current one.