Copilot CLI Plan exit approval

[DonJayamanne]

No description provided.

[Copilot]

Pull request overview

This PR updates the Copilot CLI chat session flow to handle plan-exit approval and permission prompts via core confirmation tools (through IToolsService) rather than via per-session permission handlers.

Changes:

• Add handling for exit_plan_mode.requested in CopilotCLISession, showing a confirmation prompt and responding to the SDK with approval/denial.
• Remove the old attachPermissionHandler wiring from the VS Code participant contribution and shift permission prompting to requestPermission(...) using IToolsService.
• Update unit/e2e tests to validate confirmation-tool invocation and new session/command behaviors (e.g., /compact, yielding/steering).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
test/e2e/cli.stest.ts	Introduces a test IToolsService to auto-approve confirmations and asserts confirmation invocations instead of session permission handlers.
src/extension/chatSessions/vscode-node/test/copilotCLIChatSessionParticipant.spec.ts	Adds coverage for slash-command mapping and yielding behavior; adjusts mock clearing.
src/extension/chatSessions/vscode-node/copilotCLIChatSessionsContribution.ts	Removes participant-level permission handler attachment (permission prompting now handled in-session).
src/extension/chatSessions/copilotcli/node/test/copilotcliSession.spec.ts	Updates permission-related tests to use FakeToolsService confirmation results; adds /compact and steering-after-failure tests.
src/extension/chatSessions/copilotcli/node/copilotcliSession.ts	Implements exit-plan-mode approval via core confirmation tool; routes permission requests through requestPermission(...).

Comments suppressed due to low confidence (1)

src/extension/chatSessions/copilotcli/node/copilotcliSession.ts:343

• invokeTool is called with CancellationToken.None in the exit_plan_mode.requested handler. Since this listener is registered inside handleRequestImpl, it has access to the request's token; using None prevents cancellation/timeout from propagating and can leave the confirmation UI hanging after the request is cancelled. Pass the active request token instead.

					const result = await this._toolsService.invokeTool(ToolName.CoreConfirmationTool, {
						input: params,
						toolInvocationToken: this._toolInvocationToken,
					}, CancellationToken.None);