You are reviewing a release for a new operations team. Each task uses a fresh fixture and a separate preview, so a working answer from an earlier example cannot substitute for the current requirement. Read the initial state, the available controls, and the outcome the team needs before you edit a file.
Check the normal route first, then repeat the action or move to the boundary named in the task. A control that looks correct can still leave stale data, share state accidentally, or accept one request too many. Use the visible output and the preview console to trace the failure. Keep each answer independent of the sample labels so the same component works when the fixture changes.