Where the workflow shifted
Copilot session docs show agents can work in the background and prepare or create pull requests from several entry points.
Split service delivery into scope confirmation, task launch, session evidence, draft PR, review edits, final merge, and rollback readiness.
Tool names are not outcomes
The signal matters when it clarifies a real service task, deliverable, and acceptance rule, not when it only shows a demo.
Check permissions and failure
- Set review checkpoints for every client task: scope before launch, diff after PR, rollback before release
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
Without human review points, scope, delays, and defects become service-delivery disputes. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.