drop cleanup_on_kill from the wire and the CLI #87

Closed
opened 2026-08-24 09:38:54 +01:00 by naps62-yolo · 0 comments
Collaborator

WorktreeSpec.cleanup_on_kill has been on the wire and ignored since #56. Nothing honours it, and after #79 and #81 nothing should: whether a worktree survives is decided by what is in it, not by what the spawn asked for.

Remove the field from WorktreeSpec, drop --cleanup-on-kill from the CLI, and delete the tests that assert its default. The daemon and its clients ship together, so there is no older client whose payload needs it.

A field that lies is worse than a missing one — a client reading the current schema would reasonably believe it could opt out.

Depends on: #81

`WorktreeSpec.cleanup_on_kill` has been on the wire and ignored since #56. Nothing honours it, and after #79 and #81 nothing should: whether a worktree survives is decided by what is in it, not by what the spawn asked for. Remove the field from `WorktreeSpec`, drop `--cleanup-on-kill` from the CLI, and delete the tests that assert its default. The daemon and its clients ship together, so there is no older client whose payload needs it. A field that lies is worse than a missing one — a client reading the current schema would reasonably believe it could opt out. Depends on: #81
naps62-yolo added this to the Worktree lifecycle milestone 2026-08-24 09:38:54 +01:00
naps62-yolo added the area/protocolarea/clitype/refactordifficulty/easy labels 2026-08-24 09:38:54 +01:00
naps62-yolo added a new dependency 2026-08-24 09:39:01 +01:00
This repo is archived. You cannot comment on issues.
1 Participants
Due Date
No due date set.
Reference: naps62/maestro#87