Problem
ponytail-activate.js's "STATUSLINE SETUP NEEDED" nudge hardcodes ~/.claude/settings.json as the file to edit. When CLAUDE_CONFIG_DIR is set, the flag file and settings live under that directory instead — so the nudge sends the user to the wrong file, and the statusline never gets configured.
This is the same CLAUDE_CONFIG_DIR override already honored for the .ponytail-active flag (issue #34); the nudge text just didn't follow suit.
Fix
Use the already-resolved settingsPath (computed from getClaudeDir(), which honors CLAUDE_CONFIG_DIR) in both nudge branches — the shell-safe snippet and the manual-config fallback — instead of the literal ~/.claude/settings.json.
Scope
hooks/ponytail-activate.js — two string substitutions
tests/hooks.test.js — assert the nudge references CLAUDE_CONFIG_DIR/settings.json and not ~/.claude/settings.json
Problem
ponytail-activate.js's "STATUSLINE SETUP NEEDED" nudge hardcodes~/.claude/settings.jsonas the file to edit. WhenCLAUDE_CONFIG_DIRis set, the flag file and settings live under that directory instead — so the nudge sends the user to the wrong file, and the statusline never gets configured.This is the same
CLAUDE_CONFIG_DIRoverride already honored for the.ponytail-activeflag (issue #34); the nudge text just didn't follow suit.Fix
Use the already-resolved
settingsPath(computed fromgetClaudeDir(), which honorsCLAUDE_CONFIG_DIR) in both nudge branches — the shell-safe snippet and the manual-config fallback — instead of the literal~/.claude/settings.json.Scope
hooks/ponytail-activate.js— two string substitutionstests/hooks.test.js— assert the nudge referencesCLAUDE_CONFIG_DIR/settings.jsonand not~/.claude/settings.json