One idea is shown in our components design ( https://www.figma.com/design/H8xtCDg3nc7rJ3XmgCKeNK/Edit-Check---features?node-id=1-2&p=f&t=oAVXcTQYmUbUq84r-0 ):

There are some problems with showing the success state in the card stack:

• May be technically difficult, checks are rendered when they are valid. Having a check still exist for some time after it has been resolved would add complexity.
• Assuming the message only persists for a few seconds, this could result in other checks jumping vertically after that time if checks are bunched up. Moving click targets at random times is a bad UX.
• In pre-save check mode we only show one check at a time. One would either need a different experience, or only show the check for a short period of time, but even then that could slow down a user trying to dismiss a lot of checks quickly.

@Esanders the idea behind using a completed state instead a Toast was:

1. Avoid using a success Toast with a green color which would include another color code apart from the yellow warning checks and the blue suggestions.
2. Keep the success feedback visually close to the card the user just interacted with, instead of a Toast that always appears in the same corner and feels disconnected from the card being completed.

I’m not attached to a specific solution here, just interested in whether there is a technically feasible way to keep the success feedback localized to the card's position without being disruptive.

Regarding the pre-save moment, we could also discuss whether a completed/success state is really needed there, since that flow already relies on pagination to navigate a list of cards. In contrast, during mid-edit, a localized completed/success feedback could make more sense, as checks are distributed across different places in the article.

Based on intern conversations, we decided to reuse existing components instead of creating custom states. So sharing the approach reusing existing components:

mobile	desktop

After completing a suggestion:

• Use a success Toast
• Highlighted the affected text in background-color-success-subtle while the success Toast is shown, making the connection between the action and the result explicit

After dismissing a suggestion:

• Use a notice Toast
• Optionally include a Undo button in the Toast to allow users to undo dismissing the suggestion