The archived puzzles table currently shows two actions: Un-Archive and Clone. Un-Archive moves a puzzle back to pending, which means the same puzzle (same ID) can be approved and sent out again.
The side effect: users who answered it weeks or months ago get told they already answered when it shows up in their feed.
Clone already covers the legitimate use case (reuse a good puzzle without dragging its answer history along), so Un-Archive is mostly a footgun.
Proposed change: remove the Un-Archive button from the archived puzzles row. Keep Clone.
Open question: should we also drop the pending transition path from archived in the controller, or just hide the button for now?
One thing worth confirming before you file it: is there ever a case where you do want to un-archive in place (e.g., a puzzle was archived by mistake right after being sent)? If so, the framing shifts from "remove" to "gate behind a confirmation" or "only allow if never sent."
The archived puzzles table currently shows two actions: Un-Archive and Clone. Un-Archive moves a puzzle back to pending, which means the same puzzle (same ID) can be approved and sent out again.
The side effect: users who answered it weeks or months ago get told they already answered when it shows up in their feed.
Clone already covers the legitimate use case (reuse a good puzzle without dragging its answer history along), so Un-Archive is mostly a footgun.
Proposed change: remove the Un-Archive button from the archived puzzles row. Keep Clone.
Open question: should we also drop the pending transition path from archived in the controller, or just hide the button for now?
One thing worth confirming before you file it: is there ever a case where you do want to un-archive in place (e.g., a puzzle was archived by mistake right after being sent)? If so, the framing shifts from "remove" to "gate behind a confirmation" or "only allow if never sent."