For teams that just shipped a hotfix and want proof it works, with no test data in production.

Your setup

Production ran 2.5.0. You deployed hotfix 2.5.1 for issue #31.
Production is a Certyn environment with a test account, best one that can only view.
The wiki's testing rules say what runs must not do on production.
You want a fast answer: is production fine, and is #31 gone?

Say this to Certyn

We just put hotfix 2.5.1 on production for issue #31. Do a read-only smoke check and retest #31 there.

Reads the version on production (app.environment.get). If it does not show 2.5.1, it offers to set it with a short changelog (app.environment.update). You approve. A new version starts production's after-deploy processes, such as a read-only smoke check.
Runs the smoke check, if no after-deploy process already does: a short quick run on production with a look-only goal. Sign in, open the main pages, search, change nothing.
Retests #31 (app.run.create type retest) when it was found on production and is confirmed and linked. Otherwise it runs the bug's steps as a quick run on production, look-only where the steps allow.
Reports both results. If #31 passed, it asks, then closes it as fixed in 2.5.1.

Read-only is an instruction in the goal and the wiki, not a lock. For a hard guarantee, use a production account that can only view.
A retest runs on the environment where the bug was found. A bug found on staging is retested on staging; for production, Certyn uses a quick run.
If the bug only shows when data changes (for example placing an order), a look-only check cannot prove the fix. Retest it on staging with 2.5.1, or allow one named action on production.
Setting the version from the chat needs your approval. The same version twice starts nothing.