…ts (#280)"

This reverts commit 237b789.

…ts (#280)" (#283)

This reverts commit 237b789.

Re-adds the session reset functionality from PR 2mawi2#280 without the
terminal mouse tracking changes that caused wheel scroll issues.

Endpoints:
- POST /api/reset - Reset orchestrator or session with selection
- POST /api/sessions/{name}/reset - Reset specific session

Supports:
- Agent type switching
- Prompt override for fresh starts
- Skip prompt/permissions flags

Re-adds the session reset functionality from PR 2mawi2#280 without the
terminal mouse tracking changes that caused wheel scroll issues.

Endpoints:
- POST /api/reset - Reset orchestrator or session with selection
- POST /api/sessions/{name}/reset - Reset specific session

Supports:
- Agent type switching
- Prompt override for fresh starts
- Skip prompt/permissions flags

* feat: add MCP session reset endpoint (isolated from terminal changes)

Re-adds the session reset functionality from PR #280 without the
terminal mouse tracking changes that caused wheel scroll issues.

Endpoints:
- POST /api/reset - Reset orchestrator or session with selection
- POST /api/sessions/{name}/reset - Reset specific session

Supports:
- Agent type switching
- Prompt override for fresh starts
- Skip prompt/permissions flags

* fix(ci): remove target-cpu=native from Linux targets

The native flag causes SIGILL on CI runners with different CPU features.
Replace with strip=debuginfo which is CI-safe.

* fix: downgrade tauri to 2.9.5 to match NPM packages (2.9.1)

* ci: add Tauri version sync checks to prevent NPM/Rust mismatch

Dependabot bumped Rust tauri to 2.10.1, but NPM packages are still at 2.9.x,
causing build failures. This adds two safeguards:

1. CI check that fails if Rust tauri and NPM @tauri-apps/api major.minor
   versions don't match
2. Dependabot ignore rules to prevent bumping tauri beyond 2.9.x until
   NPM packages catch up

This prevents the version mismatch from happening again.

* fix: filter -i flag for agent terminals to prevent job control conflicts

Agent terminals (top terminals running Claude, Codex, OpenCode, etc.) call
setRawMode() on the TTY, which conflicts with bash's job control enabled by
the -i (interactive) flag. This resulted in errno 5 (EIO) errors.

Changes:
- Pass terminal_id to resolve_app_program_and_args()
- Add filter_interactive_flag() to remove -i from shell args
- Agent terminals: Remove -i flag even if user has it in settings
- Non-agent terminals: Keep -i flag for interactive behavior

This allows agents to work without requiring users to manually remove -i
from their shell settings.

Also improved CI version check to use cargo tree instead of grep/awk.

* fix: source .zshrc/.bashrc for agents with 'set +m' to disable job control

Previous approach removed -i flag to prevent job control conflicts, but this
prevented .zshrc/.bashrc from being sourced, losing env vars like NVM, PYENV.

New approach:
- Keep -i flag so .zshrc/.bashrc are sourced (provides full environment)
- Add 'set +m;' before agent command to explicitly disable job control
- This prevents conflicts with setRawMode() while keeping full env

Command now looks like:
  /bin/zsh -i -l -c 'set +m; exec claude <args>'

This gives agents:
- .zprofile env (from -l login flag)
- .zshrc env (from -i interactive flag)
- No job control conflicts (from 'set +m')

* fix: bump @tauri-apps/api to 2.10.x to match Rust tauri crate

---------

Co-authored-by: Shawn <[email protected]>
Co-authored-by: 2mawi2 <[email protected]>