SQL Server PAGE-level restore and DBCC CHECKDB interaction: do repaired pages stay suspect?

The goal is to understand whether a page-level restore using RESTORE WITH PAGE automatically marks the repaired pages as clean, or if the pages remain listed in msdb.dbo.suspect_pages until a manual DBCC CHECKDB is executed.

Constraints include version‑dependent behavior: in some releases the suspect_pages entry persists after RESTORE WITH PAGE, requiring an explicit consistency check to change the state, while other versions may clear the entry automatically. The uncertainty centers on the exact point at which SQL Server considers a restored page repaired and whether additional verification steps are necessary before the database can be trusted for production use.

Does RESTORE WITH PAGE automatically remove the corresponding row from suspect_pages? Must DBCC CHECKDB be run to consider the page repaired, and if so, does running CHECKDB immediately after the page restore guarantee a clean suspect_pages state? Is there any version‑specific threshold after which the page is auto‑cleared without further checks?