A developer is responding to a degraded multi-agent release. Copilot cloud agent created a draft PR, the validation agent flagged a failing canary check, and the developer wants Copilot CLI to inspect the local rollback plan before asking a human reviewer to approve recovery. Which action should the developer take first? Select one answer.

The developer needs to inspect the local rollback plan before involving a human reviewer. The copilot CLI, when invoked in the agent-diagnostics directory, will open a trusted repository view. This allows the developer to examine the generated diffs, understand the proposed changes for the rollback, and ensure they align with the recovery strategy. This step is crucial for validating the agent's proposed solution before proceeding. Rerunning failed checks is premature; the issue is already identified. Resuming the cloud agent and approving every tool without inspection could lead to unintended consequences or further issues. Marking the draft PR ready for review is the final step, not the first, as the developer needs to validate the changes locally first.