3 Commits

Include renames

Author	SHA1	Message	Date
Rui Xue	c833f290a9	fix(worktrees): unlock before remove so WebUI-created worktrees can be reaped ... WebUI-created worktrees are locked at creation by the agent (cli._setup_worktree locks with --reason 'hermes pid=...'), but remove_worktree_for_session never unlocked, so git refused every removal with "use 'remove -f -f' to override or unlock first" — force=true included, since a single --force cannot override a lock. Mirror the agent's own _cleanup_worktree ordering: fail-soft 'git worktree unlock' right before the remove, after all dirty/untracked/unpushed/stream/terminal guards have passed. Those guards remain the real safety layer; force keeps meaning 'override dirty working state', never 'override a foreign lock'. Tests: locked worktree now removes cleanly without force; unlock is fail-soft when the worktree was never locked; existing mocked call-order assertions updated for the leading unlock call. Fixes #6023	2026-07-13 17:47:58 +00:00
Frank Song	46c62851ad	Harden worktree removal safeguards	2026-05-13 09:49:15 +08:00
Frank Song	93b7d35bfa	Issue #2057 Slice 2: Add worktree remove action ... Backend: - POST /api/session/worktree/remove — removes a session's git worktree - Guards: stream/terminal lock, dirty/untracked without force - remove_worktree_for_session() in api/worktrees.py Frontend: - 'Remove Worktree' context menu item + confirm modal - i18n keys for all 11 locales Tests: - 5 tests: clean remove, missing worktree, no-path, route success, 404	2026-05-13 09:11:55 +08:00