No way back to the default watch state once a repository has been watched or muted #180

repo watch sets a repo_watches row to watching; repo unwatch sets it to muted (internal/control/notifications.go, setWatch). Nothing deletes the row. A user who has never touched a repository is in a third state — notified only about work they are part of — and once they run either command they can never return to it from the CLI, the web, or the API.

Either repo unwatch should mean "back to default" with a separate repo mute, or a third command should clear the row. The iOS app mirrors the two commands today and cannot offer a way back until the server has one.

Decision: repo unwatch clears the row (back to default); new repo mute sets muted.