[Feature Request] --yolo should not auto-approve plans in Plan Mode; separate tool approval from plan review

What feature would you like to see?

Currently, when --yolo (or --yes / --auto-approve) is enabled, entering Plan Mode causes the generated plan to be auto-approved and executed immediately without user confirmation.

This behavior conflates two very different levels of risk:

Expected behavior:

• --yolo should auto-approve tool executions (e.g., WriteFile, Shell), but it should still pause for plan confirmation in Plan Mode.
• Alternatively, provide finer-grained flags such as --auto-approve-tools vs. --auto-approve-plans.

Why this matters:
Plan Mode's core value is "plan first, execute second." If the plan itself is automatically approved, Plan Mode loses its primary purpose for users who simply want to avoid clicking "yes" on every file change.

Additional information

Related documentation: https://moonshotai.github.io/kimi-cli/zh/reference/kimi-command.html#审批控制

Start by tracing how the --yolo, --yes, and --auto-approve flags are handled alongside the Plan Mode approval flow. Confirm where plan confirmation and tool execution approval are coupled, then verify that plans still pause for review while tools remain auto-approved; the issue does not name specific files or tests.