Feature Request: Refresh statusline on Stop hook or make refresh interval configurable

Problem

The statusline currently refreshes at an internal interval that's too infrequent, causing it to display stale usage data. Users can't control when the statusline refreshes, and Stop hooks don't trigger statusline updates.

Proposed Solutions

Recommended: #1 - Auto-refresh on Stop hook

Automatically refresh the statusline after every Stop hook completes. This is the best solution because:

• Zero configuration required
• Intuitive behavior (statusline updates when Claude finishes responding)
• No performance impact (only refreshes after responses, not continuously)
• Matches user expectations

Alternative solutions:

1. Configurable refresh interval - Add a statusLine.refreshInterval setting (in milliseconds) for users who want fine-grained control
2. Manual trigger API - Provide a command/signal that hooks can use to force a refresh (e.g., claude-code refresh-statusline)

Current Workaround Limitations

• Touching history.jsonl in Stop hooks doesn't reliably trigger refreshes
• The statusline only updates when Claude Code's internal timer decides, regardless of hook execution

Use Case

Power users with custom statusline scripts (showing token usage, costs, etc.) need real-time updates after each interaction to make informed decisions about context usage and costs.