Clarify check renaming and streamline the publishing workflow

[prestoncabe]

Problem

Renaming a check currently requires a separate republish step. New users may reasonably expect the rename to take effect without realizing that they must also publish a new version.

This raises a broader usability question: is the requirement to publish checks clear, and can that workflow be streamlined?

Questions to resolve

• Should renaming a check automatically publish a new version?
• Should the user be prompted to choose what to do after renaming?
• If publishing remains a separate step, how should the UI make that requirement and the current publication state obvious?
• Can check publishing generally be streamlined or better explained for new users?

Desired outcome

Define and implement a clear rename/publishing experience so users understand whether their rename has taken effect and whether another action is needed. Automatic publishing and prompting are options to evaluate, rather than decisions already made.