v0.6.1

Fixed

setup's discovery hooks now fire regardless of PATH. The generated SessionStart/SessionEnd hook scripts gated on a bare command -v rawclaw. On any machine whose hook PATH doesn't include the binary's directory (e.g. ~/.local/bin when it isn't on a non-login shell's PATH), that gate failed and the hook silently no-opped: setup reported success, but the discovery banner never printed and the agent never learned rawclaw was installed.

setup now bakes the binary's absolute path into each hook (via os.Executable), falls back to a command -v PATH lookup if that path later moves (a reinstall or package upgrade), and degrades to a silent no-op only when neither resolves. A hook that was wired but dead now fires.

Re-run rawclaw setup to refresh the installed hooks.