I'm also experiencing the same issue — restoring pagination state with `v-model:first` in lazy mode causes an unwanted automatic reset to `first = 0` due to an internal page event emitted right after mount. Even if `first` is correctly set programmatically, PrimeVue still emits a `@page` with `page = 0`, which overrides everything.

This breaks expected behavior in lazy mode. Pagination should behave like a dumb view that reflects whatever data the app gives it, and emit `@page` events **only when the user interacts**.

More details (including a full StackBlitz reproducer and a GitHub issue opened against PrimeVue) here:

👉 https://github.com/primefaces/primevue/issues/7618

If you're facing the same problem, upvote the GitHub issue so the team gives it proper attention. This is critical for apps that rely on persisted pagination state (e.g., from localStorage or Vuex).