A team wants Copilot coding agent to work on small implementation issues without allowing it to independently merge changes. The team needs visible task progress, automated validation, and a clear human approval point before merge. Which four actions should you perform in order? 1. Configure required checks and CODEOWNERS review on main 2. Assign a scoped GitHub Issue to Copilot coding agent 3. Merge the pull request after Copilot opens it 4. Review the Copilot-created draft pull request and checks 5. Mark the PR ready only after human validation passes 6. Remove branch protection for bot-created pull requests

The correct sequence ensures controlled automation. First, configure required checks and CODEOWNERS review on the main branch (1) to establish the necessary human approval and automated validation gates. Next, assign a scoped GitHub Issue to the Copilot coding agent (2), providing it with a specific task. After the agent creates a draft pull request, the team reviews it and its associated checks (4) to ensure the proposed changes meet requirements and pass automated tests. Finally, the team marks the PR as ready for review only after human validation passes (5), triggering the CODEOWNERS review and allowing the PR to be merged. Option 3 is incorrect because merging should only happen after human validation. Option 6 is incorrect as removing branch protection would bypass the required controls.