createYamlTransform forwards yaml-patch operations to the renderer, but its internal currentSpec snapshot is only updated for add, replace, and remove. A valid RFC 6902 move or copy therefore leaves the base used by subsequent yaml-edit fences stale.
Reproduction:
```yaml-patch
{"op":"add","path":"/a","value":1}
```
```yaml-patch
{"op":"move","from":"/a","path":"/b"}
```
```yaml-edit
b: null
```
The final edit should remove /b, but createYamlTransform currently emits only the add and move patches. The renderer now has /b, while the transform's currentSpec still has /a, so the merge edit sees no b key to remove.
Please keep the transform snapshot synchronized with RFC 6902 operations before applying later edit fences, and add a regression test for a move followed by a yaml-edit of the destination.
createYamlTransformforwardsyaml-patchoperations to the renderer, but its internalcurrentSpecsnapshot is only updated foradd,replace, andremove. A valid RFC 6902moveorcopytherefore leaves the base used by subsequentyaml-editfences stale.Reproduction:
The final edit should remove
/b, butcreateYamlTransformcurrently emits only theaddandmovepatches. The renderer now has/b, while the transform'scurrentSpecstill has/a, so the merge edit sees nobkey to remove.Please keep the transform snapshot synchronized with RFC 6902 operations before applying later edit fences, and add a regression test for a
movefollowed by ayaml-editof the destination.