v0.3.2 - absolute hook paths (fixes silent windows)

Fixes the hook silently doing nothing in Cursor windows whose working directory is not ~/.cursor/ (e.g. any freshly opened repo).

Root cause: hooks.json shipped relative commands (./hooks/attention-beep.sh stop). hooks.json has no ~/env-var expansion and Cursor does not guarantee the cwd it spawns hooks from, so the relative path resolved against whatever repo was open and silently no-op'd.

Fix: install.sh now renders each command with the absolute path to the installed script ($HOME/.cursor/hooks/attention-beep.sh) for both fresh-install and merge paths. Absolute paths work regardless of cwd.

If you installed an earlier version, just re-run ./install.sh -- it backs up your ~/.cursor/hooks.json, strips the old relative entries, and re-adds absolute ones. Then reload your Cursor window.

No change to the beep logic or the v0.3.1 shell regex.

v0.3.1 - tuned shell regex from real session data

Narrows the shell-event beep to only truly elevated tokens (sudo, ssh family, chmod, chown) and anchors matching to the start of a (sub-)command so paths in arguments (e.g. ~/.ssh/config) stop triggering the ssh token.

Tuned from a real ~3-hour multi-agent session diagnostic log:

• 28 noise items previously beeping (all git, uv, curl, ~/.ssh/ path reads) now silent.
• All 10 legit SSH-key/host setup operations still beep.
• Zero spurious MCP beeps observed; MCP coverage unchanged.
• stop event remains the primary 'agent needs you' signal, as before.

To override the tokens for your own workflow:

export ATTENTION_BEEP_PATTERN='your-extended-regex'

Or restore the v0.3.0 token set by exporting the previous default.

v0.3.0 - high-signal defaults

Full Changelog: https://github.com/aRealGem/cursor-attention-beep/commits/v0.3.0