A team wants a repeatable pattern for agent tasks that prevents context drift between the issue, the agent session, the pull request, and the validation workflow. The pattern must preserve progress and decisions as artifacts that reviewers can inspect later. Which four actions should you perform in order? 1. Ask Copilot to continue from the last unsaved chat context 2. Create or update the issue with scope and acceptance criteria 3. Capture implementation decisions in the draft PR description or comments 4. Upload validation evidence as a workflow artifact 5. Merge after the agent says the task is complete 6. Review the durable artifacts before marking the PR ready

The correct order ensures traceability and prevents context drift. First, 2. Create or update the issue with scope and acceptance criteria establishes a clear objective for the agent. Then, 3. Capture implementation decisions in the draft PR description or comments documents the agent's thought process and choices, making them reviewable. Next, 4. Upload validation evidence as a workflow artifact provides concrete proof of the agent's work and its adherence to criteria. Finally, 6. Review the durable artifacts before marking the PR ready ensures that all necessary information is present and correct before human review, preventing premature merging. Option 1 is incorrect because starting with an unsaved chat context doesn't establish a clear, reviewable objective. Option 5 is incorrect because merging solely based on the agent's completion claim bypasses crucial human review and validation.