6 Commits

Include renames

Author	SHA1	Message	Date
Miguel PalhasandClaude Sonnet 5	49ab7e9c81	fix(maestro): suffix branch name on new-branch worktree collision ... git worktree add -b fails outright when the branch already exists, even if the target directory is free. A random fast-forward handle commonly collides with a branch an earlier, already-removed worktree left behind. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-04 13:29:49 +01:00
Miguel Palhas	c67fa2bd4e	feat(maestro): force-kill prompt in the web client ... The kill button now sends the unforced DELETE immediately instead of asking first. Only the daemon's guard refusal raises a prompt, and it is a real dialog rather than confirm(), so it can offer the override the daemon already implements. The API error envelope is decoded into ApiRequestError, keeping the code and the unsaved-work breakdown so the dialog names what is in the way.	2026-09-01 11:51:45 +01:00
Miguel PalhasandClaude Opus 5	d39fbdbbfc	feat(maestro): drop retained worktrees and header debug toggle ... Removes the retained-worktree store end to end: the daemon's state-dir store, GET/DELETE /api/worktrees, `maestro worktrees list|reclaim`, the TUI overlay behind `w`, and the web `#/worktrees` view and header link. The kill guard stays. A forced kill and a dirty natural exit now leave the worktree on disk untouched instead of parking it in a store, so removing one is an ordinary `git worktree remove`. A pristine tree is still removed on exit. DELETE /api/sessions/:id always answers 204. The header's debug button also goes; Ctrl+Shift+D and `?hud` still toggle the HUD. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-31 09:00:52 +01:00
Miguel Palhas	2fc19a886e	feat(maestro): apply the kill's worktree rule when a session exits on its own ... When the liveness watcher finds the tmux session gone, it now settles the worktree through the same probe_worktree/record_retention helpers the kill uses: pristine trees are removed, anything else is retained as exited-with-unsaved-work before anything is torn down. The dead session drops its worktree reference once settled, so dismissing it neither refuses nor retains twice. If the probe or store write fails, nothing is destroyed and the tree stays attached to the record. WORKTREES.md: written down the settle-then-drop and nothing-destroyed- when-unrecordable rules alongside the existing exit rule.	2026-08-24 11:54:43 +01:00
Miguel Palhas	0c135aa065	feat(maestro): maestro kill --force ... The flag overrides the kill refusal (#81): the session ends, the guarded worktree is retained, and the CLI prints where the work went — path, branch, force-killed — instead of leaving the operator to wonder. WORKTREES.md: write down that a forced kill of a tree whose guard is clear removes it as usual — force changes what happens to blocked work, not ordinary cleanup.	2026-08-24 11:34:15 +01:00
Miguel Palhas	35c75f9238	docs(maestro): write the worktree lifecycle contract ... Closes #89	2026-08-24 10:29:42 +01:00