Deleting a background job's worktree previously refused outright when it held commits not pushed to any remote. Now a caller can pass a discardUnpushed pin (headSha plus worktreeDigest), and if the worktree's HEAD still matches that pin the removal proceeds despite the unpushed commits. If the pin no longer matches, or the unpushed commits are also referenced by another job's state, the kept-worktree reasons unpushed or the new unpushed_shared are returned instead, along with keptUnpushed/discardUnpushed info so the caller can re-confirm; unpushed_shared specifically refuses to offer a discard when another finished job's state.json also references the same worktree, to avoid destroying another session's output.
In the Fleet UI, deleting a session whose worktree has unpushed commits no longer fails silently: it reports the unpushed count and prompts to delete again to discard, tracking a discardOffer so a second delete forces discardUnpushed.