On the change’s Rollouts page, a user can select Run checks, choose an environment and services, and start checking. Deferred checks are labeled Deferred with the reason shown. The same release notes say that closing an issue now requires a reason, with examples including Fixed and Duplicate.
Cursor also lists Rollouts settings fixes: authenticating an MCP tool no longer removes an existing shared connection, and connected servers refresh rather than opening a sign-in window. The source does not specify pricing, plan availability, the checks that are run, or whether the feature applies to every Cursor deployment.