A repository owner wants three agents to work in parallel on separate services without overwriting each other’s changes or producing mixed validation evidence. The agents will use separate issues and draft pull requests. Which four actions should you perform in order? 1. Configure validation artifacts with scoped names and paths 2. Merge the first draft PR before checks complete 3. Assign all service tasks to a single shared branch 4. Create one issue per isolated service task 5. Scope workflow concurrency by pull request or branch 6. Ensure each agent works on its own branch or draft PR

The correct order ensures isolated, parallel work without conflicts. First, "Create one issue per isolated service task" (4) establishes clear, separate work items for each agent. Next, "Ensure each agent works on its own branch or draft PR" (6) prevents direct overwrites by giving each agent a dedicated workspace. Then, "Scope workflow concurrency by pull request or branch" (5) prevents validation runs from interfering with each other, ensuring independent checks. Finally, "Configure validation artifacts with scoped names and paths" (1) guarantees that validation evidence from different agents or services is distinct and doesn't get mixed or overwritten. Option 3 → 4 → 1 → 5 is incorrect because assigning all tasks to a single shared branch (3) would lead to immediate conflicts. Option 6 → 2 → 5 → 1 is incorrect because merging a draft PR before checks complete (2) bypasses crucial validation and introduces instability. Option 4 → 1 → 3 → 6 is incorrect because assigning all service tasks to a single shared branch (3) is problematic for parallel development.