New feature: Optionally disable mouse

[timotheosh]

Proposal: Make terminal mouse capture configurable

I'd like to propose making terminal mouse capture configurable while preserving the current behavior as the default.

Motivation

Crush currently enables terminal mouse reporting so it can receive mouse events within the TUI. This enables features such as clickable UI elements and mouse scrolling, but it also means the terminal no longer handles mouse events normally.

As a result, users lose native terminal behaviors such as:

• Text selection
• Copy/paste using the terminal
• Right-click context menus
• Native terminal scrolling behavior

For users who primarily interact with Crush from the keyboard, especially those working inside terminal multiplexers such as tmux, copying generated code, shell commands, compiler errors, and logs is a common workflow. In those cases, the terminal's native mouse behavior can be more valuable than mouse interaction within the TUI.

Proposal

Add a configuration option to enable or disable terminal mouse capture.

For example:

{
  "options": {
    "tui": {
      "mouse": false
    }
  }
}

The default would remain unchanged:

• true (default): current behavior
• false: do not enable Bubble Tea mouse reporting, allowing the terminal to handle selection, copy/paste, scrolling, and context menus.

Users who prefer the existing mouse-driven interface would not notice any change.

Implementation

I've already implemented this locally using the existing configuration patterns in the project.

The implementation:

• adds options.tui.mouse (default true)
• only enables Bubble Tea mouse reporting when the option is enabled
• preserves existing behavior when the option is omitted
• updates the configuration schema and documentation
• includes tests covering the new configuration and mouse mode selection

The implementation follows the project's existing configuration conventions rather than introducing a new configuration style.

If this proposal aligns with the project's direction, I'm ready to submit the PR.

[meowgorithm]

Hey! Thank you for opening a discussion about this. Totally down for this, but let's wait until we merge #3410 first, since this one touches settings.

I'd also add a command to the command palette to enable/disable the functionality in-app.

[timotheosh]

I see that #3410 has been merged.
I have a new branch based on the latest main branch that includes enable/disable functionality in the app. Shall I go ahead and submit my PR?

[meowgorithm]

Yep, please.

[timotheosh]

#3542

just synced with main and retested