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.
This commit is contained in:
@@ -61,8 +61,15 @@ pub async fn dispatch(
|
||||
run_attach_url(&daemon.attach_url(args.session_id)?, detach).await?;
|
||||
}
|
||||
Command::Kill(args) => {
|
||||
run_kill(&daemon, &args).await?;
|
||||
let outcome = run_kill(&daemon, &args).await?;
|
||||
println!("killed {}", args.session_id);
|
||||
if let Some(w) = outcome.retained {
|
||||
println!(
|
||||
"worktree retained at {} (branch {}, force-killed)",
|
||||
w.path.display(),
|
||||
w.branch
|
||||
);
|
||||
}
|
||||
}
|
||||
}
|
||||
Ok(())
|
||||
|
||||
Reference in New Issue
Block a user