zap 0.2.2: check, schedule, map, and Homebrew

zap now tells you before your disk fills, shows what else coding agents keep on it, and installs with Homebrew. This release covers everything since 0.1.0 (0.2.0 and 0.2.1 shipped the same changes without a working Homebrew cask).

brew install thecloudranger/tap/zap

Added

• zap check: one line on merged or empty worktrees and free disk space. Exits 3 when they use at least --min-stale (default 1 GB) or free space is under --min-free (default 10 GB), for cron, CI or a shell prompt. --notify adds a desktop notification.
• zap schedule on|off|status: runs zap check --notify every day (--every to change) with a launchd agent on macOS or a systemd user timer on Linux, and prints a cron line on Termux. It never deletes anything.
• zap map: what coding agents keep on the disk, to scale: worktrees per agent, Claude Code temp sessions in /tmp/claude-<uid>, and Claude Code and Codex transcripts. Temp sessions and transcripts are reported only, never deleted. --tree (experimental) draws nested blocks sized by disk use.
• scan --all and clean show the disk's free space and total.
• Homebrew: brew install thecloudranger/tap/zap.
• The one-time disclaimer now says plainly that zap deletes only when you confirm a clean, and that scan, explain, map, check and schedule never delete.

Fixed

• A worktree created from someone else's unmerged commits (git worktree add -b x origin/feature) was reported empty and offered for removal. empty now also requires the tip to be in the target branch.
• After zap undo, a restored merged worktree was reported empty instead of merged.
• With a home folder reached through a symlink (macOS /tmp is /private/tmp), paths were shown in full instead of as ~/..., in scan, map and the picker.

Full history: CHANGELOG.md