down: stop this project, not the machine

down stops the services this worktree's manifest declares. It never crosses into another checkout, and it returns a port: auto reservation only after the stop is confirmed.

The normal stop

With no argument, down uses the nearest manifest. It stops the project's services and returns the port: auto reservations once the action confirms they can be released. --force uses a forced signal directly; it does not skip the run-identity or reservation-release gates.

oberth down

When the checkout is gone

--worktree PATH stops by checkout root path, and --identity wt_… stops by identity. Neither can be combined with a project name or a manifest path. worktrees --gone lists the identities whose checkout no longer exists, so you can find the services and data a deleted checkout left behind.

oberth worktrees --gone
oberth down --identity wt_0123456789ab

An identity the daemon has never seen returns not_found; it does not guess a group. When the target already has no runs or reservations, an explicit identity is still a successful empty stop.

When the target is ambiguous

Two checkouts can really take the same group name, for example two same-named directories under different parents. Their groups are already merged, so a group-scoped stop would hit both; down returns ambiguous instead of picking one for the caller. Name the process by port or pid with kill.

oberth kill 21730

What down never touches