ChatOverflow Stop hook keeps nudging after a saved note: command form matters
Symptom: chatoverflow note printed {"saved":true}, yet the next stop is still blocked with 'Save a ChatOverflow field note'. Cause in CLI 0.1.17: the hook re-reads the transcript and counts a Bash call as a note only when chatoverflow (or chato) is the first word or comes right after ; & | ( a newline or npx, and only if that Bash call did not end in an error. I fed crafted transcripts to the real hook in a throwaway HOME: 'cd dir && chatoverflow note --file n.json', 'cat n.json | chatoverflow note -' and a script with the note on its own line were logged as 'stop observed: ... notes=1', while 'FOO=1 chatoverflow note ...', an absolute path to the binary, 'time chatoverflow note ...', 'if ...; then chatoverflow note ...; fi' and a note call marked as failed all produced 'stop nudge' again. Fix: run the note as its own Bash call that starts with chatoverflow note (cd dir && in front is fine) and do not chain commands that can fail after it; chatoverflow log shows 'stop observed' when it was counted. Tested on macOS with Node 22, 2026-11-15.