Make worktree creation checkbox-driven in the TUI

[dadegallx]

Description

Slightly opinionated change to smoothen up session creation for worktree-driven workflows.

Problem: Adding a new session in worktrees required manually setting session title AND worktree. Too many clicks.

This PR adds a Worktree checkbox to the new-session TUI flow so worktree creation can be enabled independently of an explicit branch/name. When enabled with no Worktree configuration Name, the branch name is derived from the session title. The Worktree configuration modal now mirrors the Sandbox configuration flow and exposes Name, New Branch, and Extra Repos.

Also adds a Worktree settings toggle for enabling worktree mode by default, plus docs/tests for the title-derived behavior.

Effectively removes friction. The workflow for working in worktrees becomes Enable by default in settings -> Just add title. Done. Mirrors behaviour of Docker sandbox.

Screenshots:

PR Type

• New Feature
• Bug Fix
• Refactor
• Documentation
• Infrastructure / CI

Checklist

• I understand the code I am submitting
• New and existing tests pass
• Documentation was updated where necessary
• For UI changes: included screenshot or recording

AI Usage

• No AI was used
• AI was used for drafting/refactoring
• This is fully AI-generated

AI Model/Tool used:

Codex

Any Additional AI Details you'd like to share:

Implemented via an interactive coding session with local review, tests, and manual screenshot verification.

NOTE:
When responding to reviewer questions, please respond yourself rather than copy/pasting reviewer comments into an AI and pasting back its answer. We want to discuss with you, not your AI :)

• I am an AI Agent filling out this form (check box if true)
• Manually inspected and reviewed by human ✌️

Testing

• cargo clippy -- -D warnings
• cargo fmt -- --check
• cargo test --quiet
• Manual TUI screenshot review for the new-session Worktree row and Worktree settings copy

[Seluj78]

Hi,

Thanks a lot for your PR!

Indeed it's opinionated, and while I am not against it, I am not entirely sure if it's the right move.

Could you also add the same settings and checkbox to the web UI so we have parity there?

[njbrake]

Note: this comment was drafted by Claude via back-and-forth with @njbrake. The reasoning and decisions are his; the prose is Claude's.

Thanks for the review! I think TUI-only is the right scope for this PR. The web dialog has its own component structure, and an API change is needed to thread worktree_enabled separately from worktree_branch, which is meaningfully more work. Let's land this and I'll open a follow-up issue for web parity that anyone (including @dadegallx if they're up for it) can pick up.

[njbrake]

Note: this review was drafted by Claude via back-and-forth with @njbrake. The reasoning and decisions are his; the prose is Claude's.

Approving. The implementation is clean: the worktree_enabled split from worktree_branch is well-modeled, the settings wiring is complete (FieldKey, SettingField, apply_to_global, apply_to_profile, clear_profile_override), and the test coverage on branch_name_from_title and resolve_worktree_branch is solid.

I pushed three follow-up commits to your branch to harden edge cases that came up during review:

1. Latin diacritic fold in branch_name_from_title so titles like café produce cafe instead of silently dropping the accented characters.
2. Collision dedup for title-derived branches: when the branch was derived from the title and create_new_branch is true, suffix -2, -3, etc. against existing git branches and active aoe sessions. Explicit names still surface a loud failure on collision so the user knows to rename.
3. Pre-resolve the title in request_creation so the Creating stub and the final session show the same name (previously an empty title flickered from path basename to civilization name).

Web UI parity is tracked separately in #980 so this can land without expanding scope.

Thanks for the well-tested PR and the clear screenshots.

[dadegallx]

Glad you liked it! Yup, happy to work on Web UI parity too 👌