Rewind UX: code+conversation rewind should not be default and needs confirmation

Problem

The rewind feature currently defaults to reverting both conversation history and file changes. This is a dangerous default — an accidental click silently reverts working code with no warning or confirmation dialog.

Steps to reproduce

1. Use Claude Code and make file changes during a session
2. Click the rewind button
3. The first/primary option reverts both code and conversation — easy to trigger unintentionally

Expected behavior

1. Rewind conversation — first/default option (low risk, only affects chat history)
2. Rewind code + conversation — secondary option, behind a confirmation such as: "This will also revert changes to N files. Are you sure?"

Impact

Users can lose working code they intended to keep, thinking they were only rolling back the chat. The destructive option being the easiest to trigger is a real footgun — especially for users newer to the rewind feature who may not realize the distinction.

Having "rewind everything" as the default is roughly equivalent to putting rm -rf as the first option in a context menu. The safe action should be the default; the destructive action should require explicit confirmation.

Thank you kindly.