docs(CHANGES): retry_until args and monotonic clock

why: Both changes are visible to the downstream test suites that call
this helper -- one adds a parameter they can use, the other stops a
wall-clock step from ending a wait early.

what:
- Record the `args` parameter and the monotonic budget as one
  deliverable under `What's new`.

Author: tony

CHANGES

@@ -45,6 +45,16 @@ $ uvx --from 'libtmux' --prerelease allow python
 _Notes on the upcoming release will go here._
 <!-- END PLACEHOLDER - ADD NEW CHANGELOG ENTRIES BELOW THIS LINE -->
 
+### Fixes
+
+- {func}`~libtmux.test.retry.retry_until` measures its budget with
+  {func}`time.monotonic` instead of the wall clock, so an NTP correction, a
+  container clock sync, or a VM resume can no longer cut a wait short or
+  stretch it (#726)
+- {func}`~libtmux.test.retry.retry_until` accepts an `args` tuple forwarded to
+  the predicate, so waiting on a loop variable no longer needs a closure that
+  ruff's `B023` rejects and mypy cannot infer (#726)
+
 ### Documentation
 
 #### Cleaner `from_env` examples (#719)