- Ya
- 22 Agosti 2026, 07:00 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 4548fcc
A WOPI save on a CLASSIC version now publishes docs.classic-saved.{memberId} so the Kamo PDF editor, if it is open on the form-fillable version, can redraw the pages the fields sit on instead of showing the ones they were placed over. Core NATS and unstreamed, matching the training badge: this is a live nudge, not a durable log. A member whose socket is down misses it and sees correct bytes the next time they open the document, which is the behaviour without any of this. Ids go on the wire as strings. They are int64s past 2^53, and a bare number is rounded by JSON.parse — the editor would then compare against an id that does not exist and ignore every frame it was sent. Nothing in the announce path can fail the save: the bytes are already stored, and a 500 here would tell the member their edit was lost when it was not.