Report vulnerabilities through GitHub's private vulnerability reporting. Do not include secrets or exploit details in a public issue. If the private form is unavailable, open an issue containing no vulnerability details and ask the maintainers for a private contact channel.

Version 0.3.x receives security fixes while it is the current line. Self-update accepts only the latest immutable stable GitHub release whose title matches its vX.Y.Z tag. It verifies GitHub asset digests, the exact SHA256SUMS wheel entry, and wheel metadata before invoking an explicitly selected or ownership-proven uv/pipx manager. These checks protect release integrity but do not create an independent trust root from the GitHub repository or eliminate package-manager failure modes.

Destructive recovery is explicit: discard validates ownership and registration, snapshots the representable worktree and staged index to private recovery refs, and requires separate authorization to delete unknown ignored files. Missing quarantined paths may be forgotten only when no filesystem entry or Git worktree registration remains.

The supported coordination model is cooperative processes sharing one OS account. Worktree Grove is not a sandbox or security boundary against a malicious same-UID process. Repository Git configuration and hooks, executables on PATH, credential helpers, and configured prepare/fingerprint commands run with the user's authority and must be trusted. No-follow, ownership, and inode checks reduce substitution risk but do not claim complete race elimination.