Add PR link to AVAD CHANGELOG entries

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: yumnahussain

sdk/cosmos/azure_data_cosmos/CHANGELOG.md

@@ -5,7 +5,7 @@
 ### Features Added
 
 - Added change feed pull support via `ContainerClient::query_change_feed()`, which takes a required `ChangeFeedStartFrom` start position (`Beginning`, `Now`, `PointInTime`) and returns a `ChangeFeedPageIterator<T>` that streams `FeedPage<T>` results. New `feed` types `ChangeFeedPageIterator`, `FeedScope`, and `ContinuationToken`, plus `options` types `ChangeFeedOptions` and `ChangeFeedMode` (`LatestVersion` default; `AllVersionsAndDeletes` is reserved for a future release and currently returns an error); supports single-partition, per-partition-key, and full-container (cross-partition fan-out) reads with continuation-token resumption that persists the original start position so never-polled partitions don't replay history on resume. ([#4621](https://github.com/Azure/azure-sdk-for-rust/pull/4621))
-- Added `ChangeFeedMode::AllVersionsAndDeletes` ("full fidelity") support to `ContainerClient::query_change_feed()`. In this mode each change is delivered as a `ChangeFeedItem<T>` envelope exposing the post-change document (`current`), the pre-change document (`previous`, when available), and a `ChangeFeedMetadata` describing the change (`ChangeFeedOperationType` — `Create`/`Replace`/`Delete` — plus `lsn`, commit timestamp, previous-image LSN, and a time-to-live-expiry flag). New public model types `ChangeFeedItem<T>`, `ChangeFeedMetadata`, and `ChangeFeedOperationType`. `ChangeFeedStartFrom::Beginning` is rejected for this mode because intermediate versions and deletes are only retained within the container's retention window; use `Now` or an in-retention `PointInTime`. The continuation token does not persist the feed mode, so callers must re-pass `AllVersionsAndDeletes` on resume.
+- Added `ChangeFeedMode::AllVersionsAndDeletes` ("full fidelity") support to `ContainerClient::query_change_feed()`. In this mode each change is delivered as a `ChangeFeedItem<T>` envelope exposing the post-change document (`current`), the pre-change document (`previous`, when available), and a `ChangeFeedMetadata` describing the change (`ChangeFeedOperationType` — `Create`/`Replace`/`Delete` — plus `lsn`, commit timestamp, previous-image LSN, and a time-to-live-expiry flag). New public model types `ChangeFeedItem<T>`, `ChangeFeedMetadata`, and `ChangeFeedOperationType`. `ChangeFeedStartFrom::Beginning` is rejected for this mode because intermediate versions and deletes are only retained within the container's retention window; use `Now` or an in-retention `PointInTime`. The continuation token does not persist the feed mode, so callers must re-pass `AllVersionsAndDeletes` on resume. ([#4706](https://github.com/Azure/azure-sdk-for-rust/pull/4706))
 - Added `TlsBackend` (re-exported) and a `tls_backend` option on `ConnectionPoolOptions` (`ConnectionPoolOptionsBuilder::with_tls_backend`), defaulting to `TlsBackend::Rustls`, available under the `rustls` feature, to pin the TLS backend used by the transport. This is additive and changes no behavior for the default (rustls) build; it only has an effect in builds that compile in multiple reqwest TLS backends, where reqwest would otherwise default to native-tls and the driver now pins rustls instead. ([#4649](https://github.com/Azure/azure-sdk-for-rust/pull/4649))
 
 ### Breaking Changes

sdk/cosmos/azure_data_cosmos_driver/CHANGELOG.md

@@ -5,7 +5,7 @@
 ### Features Added
 
 - Added change feed support in the dataflow pipeline: a new `UnorderedMerge` node fans a change feed read out across physical partitions and round-robins their pages, and `CosmosOperation::change_feed` builds incremental-feed operations with the appropriate wire headers. A new public `ChangeFeedStartFrom` enum (`Beginning`, `Now`, `PointInTime`) records the feed's original start position and is persisted in the continuation token so partitions never polled before a checkpoint re-apply it on resume instead of replaying history; set it via `CosmosOperation::with_change_feed_start`. ([#4621](https://github.com/Azure/azure-sdk-for-rust/pull/4621))
-- Added full-fidelity (AllVersionsAndDeletes) change feed support: a new `CosmosOperation::change_feed_all_versions_and_deletes` factory and a `CosmosRequestHeaders::full_fidelity_feed` flag emit `A-IM: Full-Fidelity Feed` (in place of `Incremental Feed`) so the service returns every intermediate version and delete as an envelope with `current`, `previous`, and `metadata`.
+- Added full-fidelity (AllVersionsAndDeletes) change feed support: a new `CosmosOperation::change_feed_all_versions_and_deletes` factory and a `CosmosRequestHeaders::full_fidelity_feed` flag emit `A-IM: Full-Fidelity Feed` (in place of `Incremental Feed`) so the service returns every intermediate version and delete as an envelope with `current`, `previous`, and `metadata`. ([#4706](https://github.com/Azure/azure-sdk-for-rust/pull/4706))
 - Added `TlsBackend` (currently `TlsBackend::Rustls`, the default) and a `tls_backend` option on `ConnectionPoolOptions` (`ConnectionPoolOptionsBuilder::with_tls_backend` / `ConnectionPoolOptions::tls_backend`), available under the `rustls` feature. The driver asserts the selected backend on the `reqwest` transport, giving a supported way to pin the TLS backend without direct transport access. This is additive and changes no behavior for the default (rustls-only) build, where reqwest already negotiates rustls; it only has an effect in builds that compile in multiple reqwest TLS backends (e.g. `rustls` plus `native_tls`, absent reqwest's `http3` feature), where reqwest would otherwise default to native-tls and the driver now pins rustls instead. ([#4649](https://github.com/Azure/azure-sdk-for-rust/pull/4649))
 
 ### Breaking Changes