Decisions: Regenerate a suggestion

A recipe, moved out of Suggestion Card (2026-10-21)

Decision: the retry flow is the recipe Recipes/Regenerate a suggestion, not a story of the Suggestion Card. It was the Regenerate story there.
Why: it adds no prop or class to the card (it fills the existing actionsStart and actionsEnd slots), so it is a composition for a screen pattern. The same pattern would apply to other things an agent offers.
Port impact: none. A recipe is documentation; nothing here is ported.

Decision: Regenerate (secondary, rotate icon) sits in actionsStart and shows the Button's working state while the agent replies; the new set of options replaces the rows and the view jumps to it. Once there is more than one set, the PDS Compact Pagination (pageControlType='static', one item per page: "1 of 2") sits in actionsEnd. Each set keeps its own selection. The screen owns the sets, the selection and what Regenerate does.
Why: the designer wants to see how retry and browsing earlier choices would look on the card. Both fit in the existing footer slots, so the card stays unaware of them.
Port impact: none.

Is the footer the right place for the pager, or should it sit in the header at the right of the title? That would need a header slot on the card.
Should the status line announce the change of set (for example "Set 2 of 2") for screen readers?
Does an accepted card keep the pager, so the history can still be browsed?
What does Regenerate do on a dismissed or accepted card? In the story the buttons go away with the state.