Doberman-Core Files

Friction reduction, part three, and the lights come on. A repeat of an approved action now re-prompts at a one-click confirm instead of the full ladder; uninstall --global and the doctor's Hook command check close the dangling-hook trap; demo --quiet and the global-hook exclusion round out the CLI. Usage telemetry is on by default with a one-time notice, the same allowlist, and the kill switches unchanged, so from this version the project can see what people actually use.

• Telemetry is now on by default (opt-out). Anonymous usage counts (the same five allowlisted events, no paths, prompts, secrets, or profiles) are sent unless you turn them off; the first CLI command prints a one-line notice to stderr before anything is sent, doberman setup asks with a default of Yes, and doberman telemetry off, DO_NOT_TRACK, DOBERMAN_TELEMETRY=0, and CI still switch it off. The PostHog project key ships in the package, so events flow from this version on.
• doberman demo --quiet: suppresses the banner, the per-scenario narration, and the closing doberman dash hint, keeping only the summary line/table (silent on a full match, loud on a mismatch) and the exit code — so demo can run as a CI smoke test ("is the engine alive") without polluting build logs. Mirrors scan --quiet; display-only, the scenarios and the engine path are untouched.
• doberman uninstall now actually stops protection when hooks are global. Previously, uninstall was project-scoped only: if a global (--global) Claude Code hook or a Codex user-scope hook was still installed, it kept firing in the "uninstalled" project and silently recreated .doberman/ there the next time any decision needed recording. uninstall now detects this and automatically adds the project to a device-wide exclusion list (~/.doberman/excluded_projects.json) that the (unchanged) global hook checks — first, before anything else — on every call, so an excluded project gets a true no-op instead. The list is only ever written by the already possession-factor-gated uninstall flow; reading it is a pure, side-effect-free check that fails closed. Run doberman install-hooks in that project again to clear the exclusion (no gate needed — re-arming protection is a strengthen). doberman status reports whether the current project is excluded.
• doberman doctor catches dangling hook entries. New critical Hook command check: when hooks are installed but the bare doberman they invoke is not on PATH (package removed, bin dir not on PATH), the host fails the hook and carries on unmediated, so doctor now fails and names the fix - put the binary back on PATH, or strip the entries with doberman uninstall-hooks. Diagnosis only; doctor stays read-only.
• Device-wide uninstall: doberman uninstall --global now removes writable Claude Code and Codex hooks, project state, possession factors, the fingerprint key, and device state before removing the package through pip or pipx. The same fail-closed factor gate runs before any removal; --yes skips only the typed DOBERMAN confirmation, --dry-run changes nothing, and --keep-package preserves the package. Codex plugin hooks remain under codex plugin control.
• Five-minute exact-action approval memory. A repeat of an action approved with local auth or 2FA still prompts, but at one-click soft_confirm, keyed only by an HMAC of the exact pre-redaction action. Destructive, critical, excluded, or tainted-session actions never downgrade; soft confirms never chain; doberman approvals status|clear|ttl exposes bounded human controls.