Your organization allows Copilot coding agent to work on assigned issues. You must configure the repository so agent work produces reviewable evidence through normal pull request tooling before maintainers merge the change. Which four actions should you perform in order? 1. Add a PR workflow that validates and uploads the evidence directory. 2. Define the required artifact contents in repository agent instructions. 3. Rely on the Copilot-generated PR summary as the artifact. 4. Require the observability workflow check for protected branches. 5. Require the agent to write plan and validation files under agent-output/. 6. Upload inspection artifacts only after merge to main.

To ensure agent work is reviewable, first, 2. Define the required artifact contents in repository agent instructions. This step sets expectations for the agent on what evidence to produce. Next, 5. Require the agent to write plan and validation files under agent-output/. This ensures the agent places its output in a standardized, accessible location within the repository. Then, 1. Add a PR workflow that validates and uploads the evidence directory. This workflow automatically checks the agent's output and makes it available for review. Finally, 4. Require the observability workflow check for protected branches. This enforces that the evidence validation must pass before any changes from the agent can be merged into critical branches, ensuring quality and reviewability. Option 3 is incorrect because relying solely on a Copilot-generated PR summary is insufficient as reviewable evidence; it's a summary, not the raw output. Option 6 is incorrect because uploading artifacts after merge defeats the purpose of pre-merge review. The other incorrect sequences fail to establish the necessary prerequisites for reviewable agent work.