The kill refusal from #79 needs an override, or a session whose work the operator has deliberately abandoned can never be ended.
--force overrides the refusal and nothing else. It kills the session and retains the worktree, which enters the store (#78) with reason force-killed. Force never removes a tree that would have blocked.
Settled deliberately: force is not "force everything". Ending a session and destroying its work are two separate destructive acts, and each should be chosen on its own. Reclaiming the tree afterwards (#80) is the second one, taken while looking at exactly what is in the way.
Surface it as a flag on DELETE /api/sessions/:id and as maestro kill --force. A forced kill returns what was retained and why, so a client can say where the work went rather than leaving the operator to wonder.
The kill refusal from #79 needs an override, or a session whose work the operator has deliberately abandoned can never be ended.
`--force` overrides the *refusal* and nothing else. It kills the session and **retains** the worktree, which enters the store (#78) with reason `force-killed`. Force never removes a tree that would have blocked.
Settled deliberately: force is not "force everything". Ending a session and destroying its work are two separate destructive acts, and each should be chosen on its own. Reclaiming the tree afterwards (#80) is the second one, taken while looking at exactly what is in the way.
Surface it as a flag on `DELETE /api/sessions/:id` and as `maestro kill --force`. A forced kill returns what was retained and why, so a client can say where the work went rather than leaving the operator to wonder.
Depends on: #78, #79
naps62-yolo
added this to the Worktree lifecycle milestone 2026-08-24 09:38:48 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The kill refusal from #79 needs an override, or a session whose work the operator has deliberately abandoned can never be ended.
--forceoverrides the refusal and nothing else. It kills the session and retains the worktree, which enters the store (#78) with reasonforce-killed. Force never removes a tree that would have blocked.Settled deliberately: force is not "force everything". Ending a session and destroying its work are two separate destructive acts, and each should be chosen on its own. Reclaiming the tree afterwards (#80) is the second one, taken while looking at exactly what is in the way.
Surface it as a flag on
DELETE /api/sessions/:idand asmaestro kill --force. A forced kill returns what was retained and why, so a client can say where the work went rather than leaving the operator to wonder.Depends on: #78, #79