[jcannon98188]

Summary

Adds C# bindings for the pending update and pending delete set that yffi exposes through ytransaction_pending_update and ytransaction_pending_ds.

When an update arrives before the updates it depends on, yrs holds it back instead of integrating it. These bindings let callers see what is waiting and what is missing, for example to request the missing data from a peer.

Changes

New public API on Transaction:

• PendingUpdate() returns a PendingUpdate?, or null if nothing is pending.
  • Missing is a StateVector with the minimum client clocks that must arrive before the update can be applied.
  • Update is the pending update as lib0 v1 encoded bytes.
• PendingDeleteSet() returns a DeleteSet?, or null if all deletions have been applied. It reuses the existing DeleteSet type.

Internals:

• TransactionChannel gains the P/Invoke entry points ytransaction_pending_update, ytransaction_pending_ds, ypending_update_destroy and ydelete_set_destroy.
• A new PendingUpdateNative struct mirrors yffi's YPendingUpdate.
• Native memory is copied into managed objects and then freed in a finally block, so the native structs are released even if reading fails.

The signatures and struct layouts come from libyrs.h at release-v0.19.1, the version pinned in build-binaries.yml.

Tests

New PendingTests:

• An empty doc returns null for both methods.
• Applying an update whose dependency is missing produces a pending update with a non-empty Update and Missing vector. Applying the dependency afterwards clears it.
• Applying a deletion whose target content hasn't arrived produces a pending delete set with ranges.

I ran the unit suite against a yrs.dll built locally from release-v0.19.1, and all of it passes.

Notes

• PendingUpdate.Missing depends on StateVector reading its clocks correctly. That bug is fixed separately on fix/state-vector-clocks and is not part of this PR. Until it merges, the clock values in Missing are wrong. The tests here only assert that they are non-zero, so they pass either way.
• The change is additive and does not alter any existing public API.

🤖 Generated with Claude Code

[SebastianStehle]

This is weirdly named. It should e ReadUpdate or so

[jcannon98188]

I'm happy to make this change, but Update() is more in line with the DeleteSetNative that this pairs with. Which exposes Clients() and Ranges(). Your call though. Let me know.

[SebastianStehle]

perhaps their are all named badly, but Update sounds like an action.

[jcannon98188]

Would you prefer PendingUpdate() instead? Seems closest to the intended field without being an action?